codinux
/
BankingClient
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fixed that initDialogWithStrongCustomerAuthentication() JobContext.startNewDialog() hasn't been called causing message number to be 2 instead of 1 (and institution therefore to abort this dialog)

This commit is contained in:
dankito 2021-11-14 21:51:41 +01:00
parent 796218c2d6
commit c9884a380e
1 changed files with 2 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
fints4k/src/commonMain/kotlin/net/dankito/banking/fints/FinTsJobExecutor.kt
View File

@ -147,8 +147,6 @@ open class FinTsJobExecutor(
getUsersTanMethod(context) { didSelectTanMethod ->
if (didSelectTanMethod) {
context.startNewDialog()
initDialogWithStrongCustomerAuthenticationAfterSuccessfulPreconditionChecks(context) { initDialogResponse ->
closeDialog(context)
@ -164,9 +162,6 @@ open class FinTsJobExecutor(
open fun getAccounts(context: JobContext, callback: (BankResponse) -> Unit) {
context.startNewDialog(false)
initDialogWithStrongCustomerAuthenticationAfterSuccessfulPreconditionChecks(context) { response ->
closeDialog(context)
@ -579,6 +574,8 @@ open class FinTsJobExecutor(
protected open fun initDialogWithStrongCustomerAuthenticationAfterSuccessfulPreconditionChecks(context: JobContext, callback: (BankResponse) -> Unit) {
context.startNewDialog(false) // don't know if it's ok for all invocations of this method to set closeDialog to false (was actually only set in getAccounts())
val message = messageBuilder.createInitDialogMessage(context)
getAndHandleResponseForMessage(context, message, callback)