Skip to content
This repository has been archived by the owner on Sep 1, 2021. It is now read-only.

Automatic F-Droid updates #132

Closed
AndreMiras opened this issue Apr 22, 2019 · 2 comments
Closed

Automatic F-Droid updates #132

AndreMiras opened this issue Apr 22, 2019 · 2 comments
Labels
enhancement New feature or request

Comments

@AndreMiras
Copy link
Owner

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 the build.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.
@AndreMiras AndreMiras added the enhancement New feature or request label Apr 22, 2019
@AndreMiras AndreMiras mentioned this issue Apr 22, 2019
Closed
AndreMiras added a commit that referenced this issue Apr 22, 2019
@AndreMiras
Supports F-Droid auto updates, refs #132
f811648 
Uses the HTTP update method, refs:
https://f-droid.org/en/docs/Build_Metadata_Reference/#UpdateCheckMode
@AndreMiras
Copy link
Owner Author

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 f811648#diff-9dfae494ff61038f3ace8e6d6467dc41
Upstream pull request:
https://gitlab.com/fdroid/fdroiddata/merge_requests/4768

AndreMiras added a commit that referenced this issue Apr 25, 2019
@AndreMiras
Updates release process and download links, refs #132
d594613 
- tag changed to match with F-Droid and `__version__`
- adds F-Droid download button
- changes APK download image to match size
refs #132
@AndreMiras
Copy link
Owner Author

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@AndreMiras