You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Your APKs all seem to still use the initial default version: versionCode 1 and versionName 1.0 – while the releases page already lists 5 releases (i.e. versionCode should be ≥ 5) with the latest one tagged "0.2.0" (suggesting a similar versionName). As this is not only a cosmetical thing (Android decides based on versionCode whether there's an update or not), could you please bring that "into sync"? For the easiest approach, you could use versionCode as a "release counter" (i.e. always increase it by 1), and use the tag name as versionName.
Thanks!
The text was updated successfully, but these errors were encountered:
Thanks – confirmed! Just added it to my repo then, should show up here with the next sync tomorrow (if you wish to link there, find some badges here). Due to the size I can only keep one package; I hope it doesn't grow much further 🙈 Updates will be pulled automatically within 24h of your making them available – so it should be pretty easy for users to keep it updated (the F-Droid client on their devices takes care for that).
Your APKs all seem to still use the initial default version: versionCode 1 and versionName 1.0 – while the releases page already lists 5 releases (i.e.
versionCode
should be ≥ 5) with the latest one tagged "0.2.0" (suggesting a similarversionName
). As this is not only a cosmetical thing (Android decides based onversionCode
whether there's an update or not), could you please bring that "into sync"? For the easiest approach, you could useversionCode
as a "release counter" (i.e. always increase it by 1), and use the tag name asversionName
.Thanks!
The text was updated successfully, but these errors were encountered: