[GH-ISSUE #1036] Sync error after updating to 4.10.0 (Android) #679

Closed
opened 2026-02-25 22:37:49 +03:00 by kerem · 6 comments
Owner

Originally created by @gitmaker032 on GitHub (Feb 8, 2022).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1036

Describe the bug

After upgrading app to version 4.10.0 an error to connect to the server (XBEL/WebDAV) began to appear. If you roll back to version 4.9.0, functionality is restored and the error disappears. The error affects only Android, in the browser extension everything works fine. The connection settings are the same in all cases. Tried both updating and completely reinstalling the app.

Expected behavior

There are no sync errors.

Screenshots

image

Android

  • Version: 11 (MIUI 12.5.7)
  • Floccus version: 4.10.0
  • Floccus sync method: XBEL/WebDAV

Server

  • OS: Ubuntu 20.04.3
  • Nginx version: 1.18.0
  • https (Let's Encrypt)

Debug log

2022-02-08T17:59:40.705Z Starting sync process for account user@mysite.com
2022-02-08T17:59:40.728Z onSyncStart: begin
2022-02-08T17:59:40.729Z https://mysite.com/dav/bookmarks.xbel.lock
2022-02-08T17:59:40.807Z Error Caught
2022-02-08T17:59:40.808Z [e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855]
2022-02-08T17:59:40.814Z Syncing failed with E017: Network error: Check your network connection and your account details
2022-02-08T17:59:40.829Z onSyncFail
2022-02-08T17:59:40.902Z Error Caught
2022-02-08T17:59:40.902Z [e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855]

Originally created by @gitmaker032 on GitHub (Feb 8, 2022). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1036 ### Describe the bug After upgrading app to version 4.10.0 an error to connect to the server (XBEL/WebDAV) began to appear. If you roll back to version 4.9.0, functionality is restored and the error disappears. The error affects only Android, in the browser extension everything works fine. The connection settings are the same in all cases. Tried both updating and completely reinstalling the app. ### Expected behavior There are no sync errors. ### Screenshots ![image](https://user-images.githubusercontent.com/67278783/153053259-1630db5c-c659-4af6-9089-6dee9bdbc614.png) ### Android - Version: 11 (MIUI 12.5.7) - Floccus version: 4.10.0 - Floccus sync method: XBEL/WebDAV ### Server - OS: Ubuntu 20.04.3 - Nginx version: 1.18.0 - https (Let's Encrypt) ### Debug log 2022-02-08T17:59:40.705Z Starting sync process for account user@mysite.com 2022-02-08T17:59:40.728Z onSyncStart: begin 2022-02-08T17:59:40.729Z https://mysite.com/dav/bookmarks.xbel.lock 2022-02-08T17:59:40.807Z Error Caught 2022-02-08T17:59:40.808Z [e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855] 2022-02-08T17:59:40.814Z Syncing failed with E017: Network error: Check your network connection and your account details 2022-02-08T17:59:40.829Z onSyncFail 2022-02-08T17:59:40.902Z Error Caught 2022-02-08T17:59:40.902Z [e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855]
kerem 2026-02-25 22:37:49 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@marcelklehr commented on GitHub (Feb 8, 2022):

[e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855]

@gitmaker032 Can you check if this line contains useful information when not anonymizing the debug log?

Update: nevermind, the screenshot shows the error message

<!-- gh-comment-id:1032934818 --> @marcelklehr commented on GitHub (Feb 8, 2022): > [e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855] @gitmaker032 Can you check if this line contains useful information when not anonymizing the debug log? Update: nevermind, the screenshot shows the error message
Author
Owner

@gitmaker032 commented on GitHub (Feb 8, 2022):

[e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855]

@gitmaker032 Can you check if this line contains useful information when not anonymizing the debug log?

This is another bug (I can create a new issue if necessary) in version 4.10.0. The checkbox "Anonymize private data" does not save the state. After clicking on the "Save" button (settings), the checkbox returns to the active position. Consequently, it is not possible to get the extended log.

<!-- gh-comment-id:1032940347 --> @gitmaker032 commented on GitHub (Feb 8, 2022): > > [e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855] > > @gitmaker032 Can you check if this line contains useful information when not anonymizing the debug log? This is another bug (I can create a new issue if necessary) in version 4.10.0. The checkbox "Anonymize private data" does not save the state. After clicking on the "Save" button (settings), the checkbox returns to the active position. Consequently, it is not possible to get the extended log.
Author
Owner

@marcelklehr commented on GitHub (Feb 8, 2022):

This is another bug (I can create a new issue if necessary) in version 4.10.0. The checkbox "Anonymize private data" does not save the state. After clicking on the "Save" button (settings), the checkbox returns to the active position. Consequently, it is not possible to get the extended log.

Yes, please. I cannot seem to reproduce this off-hand.

<!-- gh-comment-id:1032941509 --> @marcelklehr commented on GitHub (Feb 8, 2022): > This is another bug (I can create a new issue if necessary) in version 4.10.0. The checkbox "Anonymize private data" does not save the state. After clicking on the "Save" button (settings), the checkbox returns to the active position. Consequently, it is not possible to get the extended log. Yes, please. I cannot seem to reproduce this off-hand.
Author
Owner

@marcelklehr commented on GitHub (Feb 8, 2022):

Confirmed and fix is in the works.

<!-- gh-comment-id:1032992786 --> @marcelklehr commented on GitHub (Feb 8, 2022): Confirmed and fix is in the works.
Author
Owner

@gitmaker032 commented on GitHub (Feb 9, 2022):

Problem solved in version 4.10.1 . Thanks for the quick fix.

<!-- gh-comment-id:1033721561 --> @gitmaker032 commented on GitHub (Feb 9, 2022): Problem solved in version 4.10.1 . Thanks for the quick fix.
Author
Owner

@github-actions[bot] commented on GitHub (Mar 20, 2023):

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.

<!-- gh-comment-id:1476307531 --> @github-actions[bot] commented on GitHub (Mar 20, 2023): 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.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/floccus#679
No description provided.