View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007353 | Taler | cashier (Android App) | public | 2022-09-08 18:57 | 2022-11-04 19:52 |
| Reporter | Christian Grothoff | Assigned To | grote | Resolution deadline | |
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | normal | Severity | tweak | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Target Version | 0.9 | Fixed in Version | 0.9 | ||
| Summary | 0007353: cashier app timed out on withdraw attempt | ||||
| Description | The cashier app seems to implement a (also rather short!) timeout on the attempt to withdraw. We had a user that took some time to download the wallet (slow wifi), and then the QR code timed out on the cashier. This is bad, because IF the user had scanned it, and then the timeout hits, we'd be in a very inconsistent state. I think we should simply never timeout on the QR code and instead always require the user to manually abort. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-09-08 18:57 | Christian Grothoff | New Issue | |
| 2022-09-08 18:57 | Christian Grothoff | Status | new => assigned |
| 2022-09-08 18:57 | Christian Grothoff | Assigned To | => grote |
| 2022-09-13 17:32 | grote | Status | assigned => informing |
| 2022-09-13 17:32 | grote | Resolution | open => fixed |
| 2022-09-13 17:32 | grote | Note Added: 0019129 | |
| 2022-10-20 08:47 | Christian Grothoff | Fixed in Version | => 0.9 |
| 2022-10-20 08:48 | Christian Grothoff | Target Version | => 0.9 |
| 2022-11-04 19:52 | Christian Grothoff | Status | informing => closed |