Blank screen for Android app v5.0.12 (F-Droid)

[de-code]

Which version of floccus are you using?

5.0.12

How many bookmarks do you have, roughly?

0

Are you using other means to sync bookmarks in parallel to floccus?

No

Sync method

Nextcloud Bookmarks

Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.

Android 14

Which version of Nextcloud Bookmarks are you using? (if relevant)

No response

Which version of Nextcloud? (if relevant)

No response

What kind of WebDAV server are you using? (if relevant)

No response

Describe the Bug

After upgrading to the latest version 5.0.12 (via F-Droid) I am seeing a blank screen (or sometimes the Logo).
Clearing data didn't help.
Since this isn't even showing any first setup dialog after resetting the data, it should be unrelated to bookmark service.

Re-installing the previous version 5.0.11 works.

Observation: F-Droid shows 5.0.12 as 3.2 MB, whereas 5.0.11 is 6.7 MB

Expected Behavior

Bookmarks or first setup-dialog shown

To Reproduce

Install 5.0.12 via F-Droid.

Debug log provided

• I have provided a debug log file

[github-actions]

Hello 👋

Thank you for taking the time to open this issue with floccus. I know it's frustrating when software
causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at
and if possible solved.
I'm Marcel and I created floccus and have been maintaining it ever since.
I currently work for Nextcloud which leaves me with less time for side projects like this one
than I used to have.
I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it.
Until then, please be patient.
Note also that GitHub is a place where people meet to make software better together. Nobody here is under any obligation
to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can
collaborate to make this software better. For everyone.
Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge
and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and
try to fix the odd bug yourself. Everyone will be thankful for extra helping hands!
One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the forum,
to twitter or somewhere else. But this is a technical issue tracker, so please make sure to
focus on the tech and keep your opinions to yourself.

I look forward to working with you on this issue
Cheers 💙

[marcelklehr]

Hi @de-code

This is fixed in v5.1.0 which is pending release on F-Droid. Should be any day now. 🤞

[ojde]

Just updated from IzzyOnDroid F-Droid repo. Works again. Thanks!

[de-code]

Thank you for the quick fix. It is indeed working again. 🙇