mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-26 06:35:59 +03:00
[GH-ISSUE #1308] The Android app crashes #869
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#869
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 @kalekad on GitHub (Dec 31, 2022).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1308
Which version of floccus are you using?
v4.18.0
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.
Samsung, LineageOS 19.1(Android 12L)
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
application crashes when selecting a bookmark
Expected Behavior
To Reproduce
Debug log provided
@kalekad commented on GitHub (Dec 31, 2022):
The application crashes when I select a bookmark, but the menu appears in which browser I want to open the bookmark, I select the browser and the bookmark is loaded.
@kalekad commented on GitHub (Dec 31, 2022):
-ad: When I reopen an already opened application in the background, I don't go back to the folder where I was, but the application loads the base folder.
@kalekad commented on GitHub (Dec 31, 2022):
-ad: In the browser, I share a bookmark to the app, the bookmark save menu appears, I don't save the bookmark, but I click the arrow in the top left corner, go back to the browser and back to Floccus, and the previously rejected bookmark shows up for saving.
@marcelklehr commented on GitHub (Dec 31, 2022):
I cannot reproduce this.
@marcelklehr commented on GitHub (Dec 31, 2022):
I cannot reproduce this. For me it works.
@marcelklehr commented on GitHub (Dec 31, 2022):
I can only reproduce this when not tapping the back button in the save menu but switching to the browser directly and then resharing to floccus. I don't believe this can be fixed, though.
@technopagan commented on GitHub (Jan 5, 2023):
+1'ing the crashing on Lineageos 19.1 + WebDav:
During account setup, the app constantly resets itself when losing focus (e.g. when I look up my WebDav password) so that I had to write everything down beforehand and do the account setup without changing app focus.
After the WebDav account was finally set up, I tried importing an HTML bookmarks file. This also makes the app crash immediately.
@heapifyman commented on GitHub (Jan 8, 2023):
I experience the same behaviour as @kalekad. The app seems to be crashing or re-initializing after selecting a bookmark. Examples:
Select bookmark directly
Select bookmark from search results
In step 2, when the bookmark is already opened in the browser I often get a popup from Android saying: "floccus bookmark sync keeps stopping", with options to stop the app or view app information. (I assume that is an indicator that the app crashed?)
This started happening only after updating to version 4.18.0.
Downgrading to 4.17.1 resolves the issue.
I am using a Google Pixel 6 with Android 13 (patch level January 2023). Floccus was installed from f-droid store.
I am synching bookmarks to a nextcloud instance. After updating to v4.18.0 I changed the sync interval to 10 minutes (from the default 15 minutes).
Do I need to disable battery optimisation for floccus so that it can run in the background?
@KevinCFechtel commented on GitHub (Jan 8, 2023):
I experienced also the same behavior with resetting the app when loosing focus.
Also i can repeatly crash the app by adding a Bookmark with empty Link (only with a title) to the root folder.
The only way to get the app back working is to delete all data (which means i need to readd the account which is a paine with the resetting when losing focus bug).
I am using a Samsung Galaxy S20 FE with Android 13 patchlevel December 2022
App Version is 4.18.0 from googleplay
@marcelklehr commented on GitHub (Jan 8, 2023):
The only thing I can reproduce is the broken state after adding a bookmark without a link. I can fix that.
The crashing / resetting may be due to capacitor v4. Hopefully they have a fix for that
@marcelklehr commented on GitHub (Jan 8, 2023):
Could you may try to get the log after a crash, if you have a bit of android experience?
@KevinCFechtel commented on GitHub (Jan 8, 2023):
I will try to get the logs with logcat tomorrow.
@KevinCFechtel commented on GitHub (Jan 9, 2023):
So, here are two log files.
One with the crash after inserting an empty link (with starting the app in the broken state).
One with resetting the application when loosing focus.
Hope this helps.
floccus_empty_link.log
floccus_loosing_focus.log
@heapifyman commented on GitHub (Jan 10, 2023):
Probably this issue: https://github.com/katzer/cordova-plugin-background-mode/issues/574 ?
There's an open PR with a fix: https://github.com/katzer/cordova-plugin-background-mode/pull/571
But the project seems to be unmaintained - no commit for over 3 years.
@heapifyman commented on GitHub (Jan 14, 2023):
@marcelklehr do you have an ETA for a new release that contains the fix?
@marcelklehr commented on GitHub (Jan 17, 2023):
@heapifyman Should be out now on Google Play
@heapifyman commented on GitHub (Jan 17, 2023):
And on f-droid, too :) thanks
@github-actions[bot] commented on GitHub (Jan 18, 2024):
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.