Closed AndreMiras closed 5 years ago
I actually decided to use the HTTP
update mode rather than the Tag
one, so I don't need to ship build.grade
(required for version code) and AndroidManifest.xml
required for package and app name.
Instead we just need to update the version.py
file providing the version code, see https://github.com/AndreMiras/EtherollApp/commit/f81164875c04893fda9ef4caa8a7c51a1e8bf756#diff-9dfae494ff61038f3ace8e6d6467dc41
Upstream pull request:
https://gitlab.com/fdroid/fdroiddata/merge_requests/4768
The upstream pull request was merged which resulted to the F-Droid bot making the automatic metadata update here https://gitlab.com/fdroid/fdroiddata/commit/42be7da8b70a8de4cffb95046011399da9c36751
Unfortunately it looks like the build server VM didn't boot up for some reason and the build log gave the following message: could not bring up vm 'builder_default'
https://f-droid.org/wiki/page/com.github.andremiras.etheroll/lastbuild_202326
I saw other app builds having the same issue, so it may just be an issue F-Droid side.
Since the metadata got apparently properly updated, we can consider this issue solved
Now that #36 is fixed, we want F-Droid to build the new APK whenever we release. Problem is, it currently doesn't have the
versionCode
information. When tagging a new release, should be providing thebuild.gradle
so fdroidserver can read it. It's currently available under.buildozer/android/platform/build/dists/etheroll/build.gradle
and should probably be tracked in the code.