I've decided to yank #Catima 2.34.3 due to issues with Android 15 edge-to-edge support.
Specifically, when using button navigation on Android 15 landscape parts of the app are inaccessible.
The GitHub release has been reverted to a "pre-release", IzzyOnDroid has removed the release on my request, F-Droid has been notified (but they will likely still publish the new update for 3-5 days anyway due to their inability to remove apps out-of-build-cycle) and the Google Play rollout has been stopped.
=> More informations about this toot | More toots from SylvieLorxu@chaos.social
This is on me, I didn't test thoroughly enough with 3 button navigation in landscape mode, the majority of my testing was in portrait mode and with the default gesture navigation. I'm sorry.
I'm planning to soon release a new quick release that opts out on edge-to-edge completely, to properly fix it later (help is very welcome, edge-to-edge is quite a complex undertaking).
This is being tracking in https://github.com/CatimaLoyalty/Android/issues/2301.
=> More informations about this toot | More toots from SylvieLorxu@chaos.social
That being said, it would be great if Catima had a group of dedicated testers so there would be more safeguards against bad updates than just me forgetting to properly test one single case 🥲
=> More informations about this toot | More toots from SylvieLorxu@chaos.social
@SylvieLorxu great idea. I suggest you to create a way to notify interested users of a possibile beta release. I know that F-Droid allows this on a per repository basis. But don't know how you can signal it that there is a new beta release.
=> More informations about this toot | More toots from esplovago@mastodon.uno
@esplovago Realistically, I probably need automatic nightly builds for those who are interested enough to test changes but not interested enough to build themselves and look at WIP branches/main branch to test. The bad code was merged 2 week ago but it only got caught after the release. A nightly would've given 2 weeks for someone to hopefully notice.
Sadly setting up automatic building and publishing is some work and, well, I already have too much on the backlog 😅
=> More informations about this toot | More toots from SylvieLorxu@chaos.social
@SylvieLorxu I'd be open to testing things if you want, for new updates or anything really.
=> More informations about this toot | More toots from Skivling@mastodon.nz
@Skivling Thanks! I'll try to keep that in mind if I ever get a nightly build set up :) If you ever have spare time and you see there are any new open MRs from me or others or interesting changes in main, a look is always appreciated to! :)
=> More informations about this toot | More toots from SylvieLorxu@chaos.social
@SylvieLorxu
I could offer to test your app on my Samsung Galaxy A52 if that helps!? 😉
@IzzyOnDroid
=> More informations about this toot | More toots from kranzkrone@quasselkopf.de
@kranzkrone @IzzyOnDroid Thanks! I had some Android 13 users to double-check my fix this time (which was just a revert basically) so all should be good for now. But I'll definitely keep it in mind, maybe the next retry for edge-to-edge, can probably use testers there :)
=> More informations about this toot | More toots from SylvieLorxu@chaos.social
@SylvieLorxu
No problem, things happen. Thanks for developing it, it's really cool!
(about betatest: Google play has a feature for that AFAIK, maybe you can use that?)
=> More informations about this toot | More toots from rugk@chaos.social
@rugk Yeah, I do use Google Play Open Testing. I was still the first who caught it anyway ^^"
Honestly, the best thing would probably be some kind of automatic nightly builds, so this could've been detected in the 2 weeks of it being in the codebase before the release :)
=> More informations about this toot | More toots from SylvieLorxu@chaos.social This content has been proxied by September (ba2dc).Proxy Information
text/gemini