mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-26 06:35:59 +03:00
[GH-ISSUE #1586] F-droid build of floccus is broke #1049
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#1049
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 @jrfVP42bLiUWAYOShp5r on GitHub (May 4, 2024).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1586
Using LineageOS 21, most recent version.
I today upgrade to 5.0.12. It doesn't start, only shows a blank screen. I cleared the cache, deleted storage, reinstalled app, nothing helped.
Had to reinstall 5.0.11. works flawless.
@github-actions[bot] commented on GitHub (May 4, 2024):
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 commented on GitHub (May 4, 2024):
Ah, the bug is already resolved. Thank you for reporting, still.
@eikedw commented on GitHub (May 4, 2024):
Hi @marcelklehr ,
quite possible I miss something, but the f-droid version 5.0.12 mentioned by the OP is based on revision
c8cf591, i.e. --- as of now --- still being the latest version of the code in https://github.com/floccusaddon/floccus/tree/develop/android. How did You come to the conclusion the bug may already be fixed :) ? Which commit should have helped?That said, I am having the same problems as the OP (although I did not clear the cache or downgraded to the working 5.0.11 I had before).
For the record: Pixel phone running Android 13.
Many thanks, for providing floccus.
@marcelklehr commented on GitHub (May 4, 2024):
This is the commit that fixed it:
github.com/floccusaddon/floccus@250257c619@marcelklehr commented on GitHub (May 4, 2024):
Clarification: The bug is fixed in the source code ;)
@eikedw commented on GitHub (May 4, 2024):
Ah, sorry, I did not notice the Android build in "android" directory is dragging in things from "../src".
Thanks for the clarification!
@jrfVP42bLiUWAYOShp5r commented on GitHub (May 5, 2024):
Thanks for the info.
@github-actions[bot] commented on GitHub (May 6, 2025):
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.