View Issue Details

IDProjectCategoryView StatusLast Update
0008860Talerwallet (Android App)public2024-06-17 15:52
ReporterFlorian Dold Assigned Toavalos  
PrioritynormalSeverityminorReproducibilityhave not tried
Status confirmedResolutionopen 
Target Version0.13 
Summary0008860: APKs on are outdated
DescriptionWe 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
TagsNo tags attached.


parent of 0008901 confirmedavalos Create Buildbot test/deployment pipeline for the Android wallet (and other apps) [estimate: 8h] 
Not all the children of this issue are yet resolved or closed.



2024-05-22 19:32

developer   ~0022454

@grote: how were builds in being published?

Florian Dold

2024-05-22 23:39

manager   ~0022458

AFAIK those were done completely manually.


2024-05-23 23:22

developer   ~0022463

I never published there, must have been Florian.


2024-05-24 20:55

developer   ~0022468

Last edited: 2024-05-24 20:56

I can work on a CI with some guidance on Buildbot, but I will probably need write access to

@grote: for signing, should we use the same key that we use for Google Play?


2024-06-03 19:55

developer   ~0022500

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?

Florian Dold

2024-06-03 22:56

manager   ~0022502

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?


2024-06-04 13:29

developer   ~0022504

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.


2024-06-04 19:00

developer   ~0022506

Last edited: 2024-06-04 19:01

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).


2024-06-17 15:52

developer   ~0022647

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 (

Issue History

Date Modified Username Field Change
2024-05-22 10:02 Florian Dold New Issue
2024-05-22 10:02 Florian Dold Status new => assigned
2024-05-22 10:02 Florian Dold Assigned To => avalos
2024-05-22 19:32 avalos Note Added: 0022454
2024-05-22 23:39 Florian Dold Note Added: 0022458
2024-05-23 23:22 grote Note Added: 0022463
2024-05-24 20:55 avalos Note Added: 0022468
2024-05-24 20:56 avalos Note Edited: 0022468
2024-06-03 19:55 grote Note Added: 0022500
2024-06-03 22:56 Florian Dold Note Added: 0022502
2024-06-04 13:29 grote Note Added: 0022504
2024-06-04 16:42 avalos Target Version 0.11 => 0.12
2024-06-04 19:00 avalos Status assigned => confirmed
2024-06-04 19:00 avalos Note Added: 0022506
2024-06-04 19:01 avalos Note Edited: 0022506
2024-06-04 19:01 avalos Note Edited: 0022506
2024-06-05 17:20 avalos Relationship added parent of 0008901
2024-06-17 15:48 avalos Target Version 0.12 => 0.13
2024-06-17 15:52 avalos Note Added: 0022647