View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011727 | Taler | wallet (Android App) | public | 2026-08-17 08:43 | 2026-08-17 15:13 |
| Reporter | avalos | Assigned To | 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 | low | Severity | feature | Reproducibility | have not tried |
| Status | implementing | Resolution | open | ||
| Target Version | post-1.0 | ||||
| Summary | 0011727: built-in update push notification | ||||
| Description | We've seen plenty of cases where the Taler Wallet does not get auto-updated by Google Play, leaving users in some cases with completely non-functional versions of the wallet. We should implement a built-in notification mechanism that alerts users of new versions of the wallet and prompts them to update before continuing. This is a very standard pattern, and even though it could be annoying to some users, Google Play leaves us no choice! | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-08-17 08:43 | avalos | New Issue | |
| 2026-08-17 15:13 | Christian Grothoff | Priority | high => low |
| 2026-08-17 15:13 | Christian Grothoff | Severity | major => feature |
| 2026-08-17 15:13 | Christian Grothoff | Status | new => implementing |
| 2026-08-17 15:13 | Christian Grothoff | Target Version | 1.7 => post-1.0 |