mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 14:16:12 +03:00
[GH-ISSUE #2112] Crash on Android 7(?) #1418
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#1418
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 @marcdw1289 on GitHub (Dec 2, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2112
Which version of floccus are you using?
5.8.1
How many bookmarks do you have, roughly?
200
Are you using other means to sync bookmarks in parallel to floccus?
No
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 7.1.2, XenonHD ROM, Asus Nexus 7 (2013)
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)
mydrive.ch
Describe the Bug
After launching and waiting for sync, app crashes/closes.
FATAL EXCEPTION: main Process: org.handmadeideas.floccus, PID: 18898 android.app.RemoteServiceException: Bad notification posted from package org.handmadeideas.floccus: Couldn't create icon: StatusBarIcon(icon=Icon(typ=RESOURCE pkg=org.handmadeideas.floccus id=0x7f070069) visible user=0 ) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1680) at android.os.Handler.dispatchMessage(Handler.java:102) at android.os.Looper.loop(Looper.java:153) at android.app.ActivityThread.main(ActivityThread.java:6236) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:891) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:781)Expected Behavior
Floccus syncs and not crash.
To Reproduce
Launch floccus and wait.
Debug log provided
@github-actions[bot] commented on GitHub (Dec 2, 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! 💙
@marcelklehr commented on GitHub (Dec 3, 2025):
Hi @marcdw1289
Thank you for taking the time to give feedback by opening this issue!
I guess we're using an Android feature there that is not supported yet on your phone :/ Can you try disabling notifications for the floccus app? That might fix it for the short term.
@marcdw1289 commented on GitHub (Dec 4, 2025):
Thanks.
I see that sync notifications was added in 5.7.0.
First I tested with the different Importance levels but disabling notifications altogether kept it from crashing.
Given the age of the OS (Android 7) & device (2013) and the newness of the notification feature I don't think there's anything that needs fixing.
Assuming there's any other Nougat (or earlier) users out there with the same issue then turning off notifications should suffice.
Closing this. Not sure if I should pick 'Completed' or 'Not Planned' in the options.
@marcelklehr commented on GitHub (Dec 4, 2025):
Let's wait if more people complain about this. Until then we can close this as won't fix which is 'not planned' :) I'm glad it works for you now!