Izzy

@basile-laderchi if you can give me a link to your fork, and have the APK available there (ideally attached to a release), I can give it a try.

> Do I have to sign the apk for releasing it? Yes please. Else fdroidserver won't accept it. Let me know when the APK is available and I give it...

No, if you want me to pick pre-releases, that can easily be done. But the tag name potentially poses a problem: it should either reflect the `versionName` or the `versionCode`...

@basile-laderchi thanks! I just updated its metadata to have the updater check for tags going by `versionName`, and then it was able to see and fetch the update (should show...

Not really a problem with the `.free` suffix (I hope – we'll see when you published the next release and my updater picked it up). Those reports came by mail....

A few items coming to my mind: * whenever doing a release (e.g. for Playstore), create a new tag * name the tag `v` (e.g. `v1.2.3` for version 1.2.3) and...

And do not forget to increase the `versionCode` with each new release (not Github related, but still important – otherwise Android will not recognize it as new version).

Thanks for the kind feedback, @housseindjirdeh ! To further encourage you, I've made your app [available in my F-Droid repo](https://apt.izzysoft.de/fdroid/index/apk/com.gitpoint) (while dependencies on proprietary components, here GMS and Firebase, wouldn't...

@housseindjirdeh > And I made the mistake of not increasing versionCode when launching a quick Android update so I've experienced that already Yeah – right now. Please check `versionCode` and...

As pointed out: the `.apk` attached to v1.1.0 shows up with versionCode=1 and versionName=1.0, so it cannot be placed next to the real v1.0 in the repo. Also, if I'd...