mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-26 06:35:59 +03:00
[GH-ISSUE #1447] E017: Network Error on Android App #954
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#954
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 @TheDaftGazebo on GitHub (Dec 8, 2023).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1447
Which version of floccus are you using?
v4.19.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.
Android 14 (Dec 5, 2023 security update), Google Pixel 6a
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)
Synology NAS (DSM 7), LAN only
Describe the Bug
The Android App is unable to sync from the bookmarks.html file hosted in the shared folder I created for floccus, I imported the account from my desktop browser extension, where floccus is working as expected. I also attempted to setup the account manually on my Android device, but I get the exact same result, which is the E017: Network Error message.
Expected Behavior
I expect the Android app to sync with my Synology NAS WebDAV server just like my desktop browser extension is able to.
To Reproduce
Debug log provided
@github-actions[bot] commented on GitHub (Dec 8, 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 💙
@marcelklehr commented on GitHub (Dec 8, 2023):
I cannot reproduce this. Are you using self-signed TLS certificates?
@TheDaftGazebo commented on GitHub (Dec 8, 2023):
I am not. I've decided to try out self-hosting Nextcloud instead. My apologies for raising this without further deliberation on my part. Thank you for your time.
@github-actions[bot] commented on GitHub (Dec 8, 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.