mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-26 14:45:59 +03:00
[GH-ISSUE #2115] Android app not loading #1422
Labels
No labels
browser-specific
bug
correctness issues
enhancement
feature: Google Drive
feature: Linkwarden
feature: git
feature: nextcloud-bookmarks
feature: tabs
feature: webdav
help wanted
native-app
priority: high
priority: low
priority: medium
pull-request
question
question
stale
upstream
waiting for more information
wontfix
🙁 Not following issue template
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/floccus#1422
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Z-Peppe on GitHub (Dec 8, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2115
Which version of floccus are you using?
5.8.2
How many bookmarks do you have, roughly?
30
Are you using other means to sync bookmarks in parallel to floccus?
Yes, I also sync via Mozilla account
Sync method
WebDAV
Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.
Android 15 (OneUI 7) and Android 16 (OneUI 8)
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)
WebDAV on koofr.eu
Describe the Bug
Since the last update, the app has been stuck in an infinite loading screen on both of my devices (running Android 15 and Android 16). Downgrading to 5.8.1 solves the issue
Expected Behavior
When opened, the app should open normally
To Reproduce
Updating to version 5.8.2 with a WebDAV on Koofr causes the app not to launch to the main screen but to remain stuck in an infinite loading loop.
Debug log provided
@github-actions[bot] commented on GitHub (Dec 8, 2025):
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. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings. I'm Marcel. I created floccus a few years ago, and have been maintaining it 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. It helps when you stick around to answer follow up questions I may have, as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report and the issue cannot be solved without it, I will have to close the issue after a while. Note also that GitHub in general 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! If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way, I ask that you donate to the project when opening an issue (or at least once your issue is solved), if you're not a donor already. You can find donation options at https://floccus.org/donate/. Thank you!
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 Nextcloud 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.
Thank you for reading through this primer. I look forward to working with you on this issue! Cheers! 💙
@mofongox commented on GitHub (Dec 9, 2025):
I am having the exact same issue on GrapheneOS both in my Pixel 8 Pro and my Pixel 10 Pro XL.
I cannot even get past the spinning wheel, left it to open overnight while charging, to no avail.
I install from github via Obtainium. Tried clearing data, cache and even uninstalling and reinstalling. Does not work.
@jeffiths commented on GitHub (Dec 9, 2025):
I've got the same issue on my Pixel 9.
@marcelklehr commented on GitHub (Dec 9, 2025):
Hi there, thank you for reporting this! I will push out a patch as soon as possible.
@mofongox commented on GitHub (Dec 9, 2025):
Meanwhile, I went back to 5.7, and everything works as expected. Just thought I'd share so that whomever is looking for a workaround knows this is a feasible one until @marcelklehr is able to push a patch.
Just so you know, updating after syncing will also make floccus 5.8.x break. I tried it.
@marcelklehr commented on GitHub (Dec 9, 2025):
Are you all using the F-Droid build or are you using the build from github?
@fimholz commented on GitHub (Dec 9, 2025):
GitHub here, installed with Obtainium
@marcelklehr commented on GitHub (Dec 9, 2025):
Nevermind I can reproduce with the build from GitHub.
@mofongox commented on GitHub (Dec 9, 2025):
The Fdroid build will not even download for me, for some reason.
@Z-Peppe commented on GitHub (Dec 9, 2025):
Tried them both, same problem
@marcelklehr commented on GitHub (Dec 9, 2025):
I've just built the app again from scratch and the new build works for me. I've uploaded it here to github. Let me know if that works for you! 💙
@Z-Peppe commented on GitHub (Dec 9, 2025):
It looks ok for me, thanks!
@mofongox commented on GitHub (Dec 9, 2025):
Yes, it is fixed now. I downloaded from github via browser and updated for one phone, and updated from Obtainium in the other. Both are working.
@jeffiths commented on GitHub (Dec 9, 2025):
Worked for me also