Ok, thank you very much!
i’ve updated android build CI pipelines so that
- gitlab releases contain apk version info in readable form - https://gitlab.tt-rss.org/tt-rss/tt-rss-android/-/releases/
- json files necessary for in-app update notifications to work are also generated and published during build - https://gitlab.tt-rss.org/tt-rss/tt-rss-android/-/jobs/611
1 Like
I might have a very old version, is it expected that I can not easily update to the latest gitlab release?
if you installed from play store originally, you’ll have to reinstall because the signing key is different. it’s the same key from then on though.
1 Like
Yeah, now the build number hast a -fdroid suffix, I guess I was still on a Play Store version. Feels a little bit snappier, should not have waited so long for the update 
Did I understand correctly that it now reaches out to your server to check if there is an update when the app starts? Would it be possible to make this optional and only trigger this manually?
nope, can’t disable it at the moment. i could make an opt-out checkbox i guess. 
its a simple json file https://srv.tt-rss.org/fdroid/updates/org.fox.ttrss.json
Sure, it’s not a big problem and I hope the updater library has something implemented to not block the app if some reason the server goes offline or at some point a wild CI config created a very big file, which is downloaded automatically by all users of the app at start.
Sure, the playstore and f-droid are doing the same, but it just does not feel right for a self-hosting crowd of people (which are too lazy to self-built an android app).
Looking through the code it seems like it already loads the settings, but from my glances over the code I was not able to understand how the settings UI is build (and I guess it does not fit to any of the current category)? So if I’m bored I would try to have the Android Developer Experience and create a try creating a PR.
Could the “Debugging” category maybe be the “Application settings”? But this would need new translations, maybe I will not bother implementing it
now i remember. i haven’t bothered to add an update opt-out checkbox because, well, to get to auto updates you need to download and install the APK off my server which implies rather impressive amount of trust, because android is a sieve of vulnerabilities.
trying to sever all further connections to the exact same infrastructure which somehow becomes a privacy-invading nightmare or w/e directly afterwards doesn’t make a lot of sense to me - at this point, if i was a bad actor, the damage has already been done.
lazy, technically inept, paranoid people are not the userbase i’m interested in. if using my software doesn’t feel right for them, they can collectively fuck off and use something else instead.
that said, i’ll make a note to add an opt-out knob for updates.
all network i/o on android is inherently asynchronous. you can’t do network on main application thread, it’s forbidden by runtime.
1 Like
new version with update opt-out is up.
https://gitlab.tt-rss.org/tt-rss/tt-rss-android/-/releases/9faf01bb
2 Likes