View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010041 | Taler | wallet (Android App) | public | 2025-05-28 12:22 | 2025-05-28 20:27 |
| Reporter | sebasjm | Assigned To | avalos | ||
| Priority | high | Severity | crash | Reproducibility | always |
| Status | assigned | Resolution | open | ||
| Product Version | 1.0 | ||||
| Target Version | 1.0 stretch goals | ||||
| Summary | 0010041: reading QR code leaves the app without response | ||||
| Description | Create a qr code like this echo taler://withdraw-exchange/exchange.demo.taler.net/ | qrencode -t utf8 -o - Read it, you will see a black screen and no clue. The underlying problem is a \n in the QR code but the android app doesn't tell. Looking at the logs i found this 05-27 15:54:34.331 8551 8551 D taler-wallet: could not refresh ToS status, exchange null was not found 05-27 15:54:34.335 8551 8580 D BackendManager: sending message: 05-27 15:54:34.335 8551 8580 D BackendManager: { 05-27 15:54:34.335 8551 8580 D BackendManager: "id": 31, 05-27 15:54:34.335 8551 8580 D BackendManager: "operation": "prepareWithdrawExchange", 05-27 15:54:34.335 8551 8580 D BackendManager: "args": { 05-27 15:54:34.335 8551 8580 D BackendManager: "talerUri": "taler:\/\/withdraw-exchange\/exchange.demo.taler.net\/\n" 05-27 15:54:34.335 8551 8580 D BackendManager: } 05-27 15:54:34.335 8551 8580 D BackendManager: } 05-27 15:54:34.339 8551 8570 D BackendManager: message received: {"type":"error","operation":"prepareWithdrawExchange","id":31,"error":{"code":7001,"when":{"t_ms":1748372074338},"hint":"unexpected exception (message: expected a taler://withdraw-exchange URI)","stack":" at handlePrepareWithdrawExchange (<compiled_js>:52768)\n at dispatchRequestInternal (<compiled_js>:54010)\n at dispatchWalletCoreApiRequest (<compiled_js>:54080)\n"}} The error should be on screen to be actionable. | ||||
| Tags | No tags attached. | ||||
|
|
Errors should be on the screen, but also newlines/whitespace should simply be ignored by the parser. If the screen goes black, this will just feel like a crash, thus some urgency to fix (both the ignore whitespace and the show errors when the parser fails *nicely*). |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-05-28 12:22 | sebasjm | New Issue | |
| 2025-05-28 20:26 | Christian Grothoff | Assigned To | => avalos |
| 2025-05-28 20:26 | Christian Grothoff | Priority | normal => high |
| 2025-05-28 20:26 | Christian Grothoff | Severity | minor => crash |
| 2025-05-28 20:26 | Christian Grothoff | Status | new => assigned |
| 2025-05-28 20:26 | Christian Grothoff | Product Version | => 1.0 |
| 2025-05-28 20:26 | Christian Grothoff | Target Version | => 1.0 stretch goals |
| 2025-05-28 20:27 | Christian Grothoff | Note Added: 0025044 |
