View Issue Details

IDProjectCategoryView StatusLast Update
0008083Talerwallet (WebExtension)public2024-03-07 20:49
ReporterChristian Grothoff Assigned Tosebasjm  
Status closedResolutionfixed 
Platformi7OSDebian GNU/LinuxOS Versionsqueeze
Product Versiongit (master) 
Target Version0.9.4Fixed in Version0.9.4 
Summary0008083: bad UX after scanning QR code with mobile app on withdraw
DescriptionWhen I scan the QR code shown by the Webextension wallet for withdraw with my Android wallet (bank-integrated withdrawal), I can confirm on Android but the QR code keeps being shown by the Webextension and the transaction "hangs" for a normal user as they would not know that they need to (manually!) go to the bank for the PIN/TAN authorization. Going manually to the bank allows me to complete the transaction.

The WebExtension wallet -- when showing the QR code -- should use wallet-core to *monitor* if some other wallet has taken up the withdrawal operation, and once the other wallet has confirmed it, the WebExtension wallet should automatically redirect the browser back to the bank.
Steps To ReproduceReproduced in CHF deployment using latest WebEx wallet.
TagsNo tags attached.


Christian Grothoff

2024-01-13 21:31

manager   ~0020872

This issue surfaces particularly hard now because the bank-shown QR code is gone and *if* a WebEx wallet is there, it is now the _only_ way to withdraw to mobile. Which is good, but that flow now needs to be made to work nicely...


2024-01-15 18:56

developer   ~0020878

Last edited: 2024-01-15 21:08

in wallet core
> WalletApiOperation.GetWithdrawalDetailsForUri
will be receive a new param
> notifyChangeFromPendingTimeoutMs
if the param is present wallet core will be making an addional request with long polling, the operation will not block but rather it will trigger notification
> NotificationType.WithdrawalOperationTransition
with operationId and new status.


2024-01-15 21:15

developer   ~0020881

I have also added `WalletApiOperation.GetWithdrawalTransactionByUri` which will return the transaction associated to that URI

this is useful in this context because if the operation is found to be selected or confirmed, it may or may not be for this wallet.


2024-01-15 21:37

developer   ~0020882

fixed in ef0bb60f2..2e2cf4049

Issue History

Date Modified Username Field Change
2024-01-13 21:30 Christian Grothoff New Issue
2024-01-13 21:30 Christian Grothoff Status new => assigned
2024-01-13 21:30 Christian Grothoff Assigned To => sebasjm
2024-01-13 21:31 Christian Grothoff Note Added: 0020872
2024-01-15 18:56 sebasjm Status assigned => confirmed
2024-01-15 18:56 sebasjm Note Added: 0020878
2024-01-15 20:46 Christian Grothoff Target Version 0.9.4 => 0.10
2024-01-15 21:08 sebasjm Note Edited: 0020878
2024-01-15 21:15 sebasjm Note Added: 0020881
2024-01-15 21:37 sebasjm Status confirmed => resolved
2024-01-15 21:37 sebasjm Resolution open => fixed
2024-01-15 21:37 sebasjm Note Added: 0020882
2024-01-15 22:00 Christian Grothoff Fixed in Version => 0.9.4
2024-01-15 22:00 Christian Grothoff Target Version 0.10 => 0.9.4
2024-03-07 20:49 Christian Grothoff Status resolved => closed