I already made the query on this topic (https://forum.f-droid.org/t/help-update-my-app/7935), but I don’t know if I have to do something else to publish the update of my app?
v1.1 still tags 1.0: https://github.com/Webierta/ToDoList/blob/v1.1/app/build.gradle#L12. F-Droid checks Git tags and adds a new version if it finds a greater versionCode under one of the tags. In this case it
- checks out tag v1.0,
- finds versionCode 1 under it,
- checks out tag v1.1,
- finds the same versionCode 1,
- bails out because we already have a build with versionCode 1.
Proper versioning is important, see https://developer.android.com/studio/publish/versioning.
What you should do: just like Licaon_Kter said, delete the existing v1.1 tag, push a new v1.1 tag pointing to a hash after the versionCode change.
Thanks for your answer. I try to follow your comment:
- I have removed the tag.
But now I’m a little lost because versionCode was already changed at https://github.com/Webierta/ToDoList/blob/master/app/build.gradle :
So how do I point a new label?
Just make a new release with commit https://github.com/Webierta/ToDoList/commit/423213bebc4e0c647528034268d827823d8641fe
Thank you, then it is enough with:
git tag -a v1.1 -m "Releasing version v1.1" git push origin v1.1
Now yes (I think), before doing so I wanted to make sure. Thanks for your help.