Make the download Obtainium friendly

[Webxorcist]

For those not installing via app stores.

Current release can't be obtained by Obtainium anymore

Did the versioning change from the APK to the path? Obtainium doesn't recognize the source path to the APK anymore. I tried to create a new configuration, but it doesn't work.

Please add a Third installation (Obtainium) option in the readme.

[andiwand]

Happy to review a proposed change for this. I don't use Obtainium and I was not aware this is linked to our releases. You can still find the newest release on GitHub. it is now disentangled from Google and the app id changed

[dnut]

Why did the ID change? That's the whole problem here. This is a problem with the releases in general and is not specific to Obtainium. Anyone trying to update the app from your GitHub releases will have issues due to this ID change.

[andiwand]

because there are different flavors of the app. lite, pro, and now foss

[dnut]

So you've shutdown the availability of the pro version through GitHub releases? I assume it now is only available by paying through Google play. Only the new foss version is available through GitHub going forward?

I get the reasoning behind it, it's just a bit confusing because the prior release was only for the pro id and the latest release is only for the foss id. This interrupts the update process for anyone downloading from GitHub releases, forcing installation of a new app and uninstallation of the existing app.

[andiwand]

The apk on the release is at.tomtasche.reader.foss since 4.14.0, before that it was at.tomtasche.reader.pro. A different application id is a different app, so the old one keeps working and silently stops updating rather than erroring - install the new one, uninstall the old one. Nothing carries over, but nothing is worth carrying either: it is a recent documents list, and its uri permissions belong to the old package anyway.

Obtainium needs no filter, a release carries one apk. If it still fails on a fresh config, the old .pro app being installed is the likely reason.

#586 puts this in the readme.