[GH-ISSUE #1472] After updating to 5.0.2 : EB017 : Network error #970

Closed
opened 2026-02-25 22:38:36 +03:00 by kerem · 3 comments
Owner

Originally created by @2Belette on GitHub (Dec 13, 2023).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1472

Which version of floccus are you using?

5.0.2

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.

Fennec 120.1

Which version of Nextcloud Bookmarks are you using? (if relevant)

NA

Which version of Nextcloud? (if relevant)

NA

What kind of WebDAV server are you using? (if relevant)

My own

Describe the Bug

After updating from F-Droid, version 5.0.2, my mobile is not synchronized anymore.
My browser version on my PC was updated and still working fine (the bookmark is updated on my Webdav server).
I am using exactly the same settings, I have tried to put the password again, delete the cache, same issue.
Accessing manually to the Webdav address from my browser is working from the same device

Debug :
2023-12-13T10:05:43.571Z Starting sync process for account xxx@xxx
2023-12-13T10:05:43.585Z onSyncStart: begin
2023-12-13T10:05:43.586Z https://xxx/bookmarks.xbel.lock
2023-12-13T10:05:43.595Z Error Caught
2023-12-13T10:05:43.595Z { [Error: NullPointerException] code: undefined }
2023-12-13T10:05:43.596Z Syncing failed with E017: Network error: Check your network connection and your account details
2023-12-13T10:05:43.617Z onSyncFail

Expected Behavior

Like in previous version, to work

To Reproduce

Updating to 5.0.2 and refreshing

Debug log provided

  • I have provided a debug log file
Originally created by @2Belette on GitHub (Dec 13, 2023). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1472 ### Which version of floccus are you using? 5.0.2 ### 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. Fennec 120.1 ### Which version of Nextcloud Bookmarks are you using? (if relevant) NA ### Which version of Nextcloud? (if relevant) NA ### What kind of WebDAV server are you using? (if relevant) My own ### Describe the Bug After updating from F-Droid, version 5.0.2, my mobile is not synchronized anymore. My browser version on my PC was updated and still working fine (the bookmark is updated on my Webdav server). I am using exactly the same settings, I have tried to put the password again, delete the cache, same issue. Accessing manually to the Webdav address from my browser is working from the same device Debug : 2023-12-13T10:05:43.571Z Starting sync process for account xxx@xxx 2023-12-13T10:05:43.585Z onSyncStart: begin 2023-12-13T10:05:43.586Z https://xxx/bookmarks.xbel.lock 2023-12-13T10:05:43.595Z Error Caught 2023-12-13T10:05:43.595Z { [Error: NullPointerException] code: undefined } 2023-12-13T10:05:43.596Z Syncing failed with E017: Network error: Check your network connection and your account details 2023-12-13T10:05:43.617Z onSyncFail ### Expected Behavior Like in previous version, to work ### To Reproduce Updating to 5.0.2 and refreshing ### Debug log provided - [X] I have provided a debug log file
kerem 2026-02-25 22:38:36 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@github-actions[bot] commented on GitHub (Dec 13, 2023):

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 💙

<!-- gh-comment-id:1853629358 --> @github-actions[bot] commented on GitHub (Dec 13, 2023): Hello :wave: 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 :blue_heart:
Author
Owner

@marcelklehr commented on GitHub (Dec 13, 2023):

This will be fixed in v5.0.3 which will scheduled to be released already.

<!-- gh-comment-id:1853839786 --> @marcelklehr commented on GitHub (Dec 13, 2023): This will be fixed in v5.0.3 which will scheduled to be released already.
Author
Owner

@github-actions[bot] commented on GitHub (Dec 13, 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.

<!-- gh-comment-id:2540280408 --> @github-actions[bot] commented on GitHub (Dec 13, 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.
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#970
No description provided.