View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008860 | Taler | wallet (Android App) | public | 2024-05-22 08:02 | 2024-08-28 21:30 |
| Reporter | Florian Dold | Assigned To | avalos | 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 | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Target Version | 0.13 | Fixed in Version | 0.13 | ||
| Summary | 0008860: APKs on wallet.taler.net are outdated | ||||
| Description | We should either consider: (a) making it part of our process to keep them up to date manually (b) having some CI to automatically build them | ||||
| Tags | No tags attached. | ||||
| child of | 0008901 | implementing | Create Buildbot test/deployment pipeline for the Android wallet (and other apps) [estimate: 8h] |
| @grote: how were builds in wallet.taler.net being published? | |
| AFAIK those were done completely manually. | |
| I never published there, must have been Florian. | |
| I can work on a CI with some guidance on Buildbot, but I will probably need write access to taler.net/files. @grote: for signing, should we use the same key that we use for Google Play? | |
| fun fact: we don't *have* the key from google play and I think google won't give it to us. So maybe to not have a third incompatibly signed version around use the fdroid releases? | |
| Do they have to be signed with the same key as Google Play uses? Or can we treat it as a separate distribution channel, like we do with F-Droid vs Google Play? | |
| They don't have to, but it sucks when people can't mix and match releases from different distribution channels. The OS blocks installs from another channel due to the different signer. Btw. if we wanted the google signature, we can't sign with their key, but we can download their APKs. | |
| I figured maybe we could sign them using the same key as the F-Droid nightlies, the key is already available in the GitLab pipeline, but we also need it in the Buildbot pipeline that I will set up for this (whenever @dvn is available to guide me). | |
| Moved this to 0.13, but since the CI is not part of the release itself, I'm hoping this will be ready much earlier. At this point, most of the pieces are together, and I'm only waiting for Torsten to give me access to the F-Droid nightly repository for the deployments, and Javier to give me access to the server where APKs will also be deployed (wallet.taler.net) | |
| Finally: https://buildbot.taler.net/#/builders/28/builds/27 The pipeline now builds and deploys all three apps (wallet, PoS, cashier). - https://taler.net/files/wallet/ - https://taler.net/files/merchant-terminal/ - https://taler.net/files/cashier/ I disabled F-Droid nightly deployment for now since they were failing, and https://taler.net/en/wallet.html still needs to point to the latest version. | |
| Fixed, https://taler.net/en/wallet.html now points to the latest APK via a symlink created by the CI. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-05-22 08:02 | Florian Dold | New Issue | |
| 2024-05-22 08:02 | Florian Dold | Status | new => assigned |
| 2024-05-22 08:02 | Florian Dold | Assigned To | => avalos |
| 2024-05-22 17:32 | avalos | Note Added: 0022454 | |
| 2024-05-22 21:39 | Florian Dold | Note Added: 0022458 | |
| 2024-05-23 21:22 | grote | Note Added: 0022463 | |
| 2024-05-24 18:55 | avalos | Note Added: 0022468 | |
| 2024-05-24 18:56 | avalos | Note Edited: 0022468 | |
| 2024-06-03 17:55 | grote | Note Added: 0022500 | |
| 2024-06-03 20:56 | Florian Dold | Note Added: 0022502 | |
| 2024-06-04 11:29 | grote | Note Added: 0022504 | |
| 2024-06-04 14:42 | avalos | Target Version | 0.11 => 0.12 |
| 2024-06-04 17:00 | avalos | Status | assigned => implementing |
| 2024-06-04 17:00 | avalos | Note Added: 0022506 | |
| 2024-06-04 17:01 | avalos | Note Edited: 0022506 | |
| 2024-06-04 17:01 | avalos | Note Edited: 0022506 | |
| 2024-06-05 15:20 | avalos | Relationship added | parent of 0008901 |
| 2024-06-17 13:48 | avalos | Target Version | 0.12 => 0.13 |
| 2024-06-17 13:52 | avalos | Note Added: 0022647 | |
| 2024-06-28 02:37 | avalos | Note Added: 0022752 | |
| 2024-06-28 16:50 | avalos | Relationship deleted | parent of 0008901 |
| 2024-06-28 16:51 | avalos | Relationship added | child of 0008901 |
| 2024-06-28 16:52 | avalos | Status | implementing => informing |
| 2024-06-28 16:52 | avalos | Resolution | open => fixed |
| 2024-06-28 16:52 | avalos | Note Added: 0022764 | |
| 2024-08-26 20:30 | Christian Grothoff | Fixed in Version | => 0.13 |
| 2024-08-28 21:30 | Christian Grothoff | Status | informing => closed |