Syncing failed with E029 multiple Chrome profiles
Closed this issue · 1 comments
Which version of floccus are you using?
5.0.10
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.
Chrome Version 123.0.6312.107 (Official Build) (arm64)
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
Active tab sync failed when Chrome has multiple profiles (e.g. Profile A and Profile B) and the synced one (Profile A) is not active (closed) but Chrome is running on another profile (Profile B). If both profiles (Profile A and Profile B) are active on both systems everything is fine.
Expected Behavior
If Chrome with Profile A is closed and only Profile B is active, floccus should not attempt to sync tabs in the background, thereby avoiding the deletion of all tabs on the other system with the active Profile A.
To Reproduce
Sync between two systems with Google Chrome, both having Profiles A (synced via floccus) and Profile B (not synced via floccus).
The floccus sync for tabs is enabled and configured on Chrome with Profile A on System 1 and System 2.
Chrome is running on both systems but on System 1 Profile A is closed and only Profile B (not synced) is active.
On System 2 both profiles (Profile A and Profile B) are active.
Chrome continues to run the floccus sync for Profile A on System 1 in the background and now gives the E029 error on System 2 with an active Profile A.
Debug log provided
- I have provided a debug log file
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 💙