Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Brave sync failing with parse error (Empty document)

See original GitHub issue

Describe the bug

When trying to sync bookmarks from Brave to Google drive, it fails with a parse error (see debug log)

To Reproduce

Steps to reproduce the behavior:

Add Google drive configuration (all default)
Start sync
See error

Expected behavior

I expect my bookmarks to be synced to the bookmarks file on Google drive without an error

Screenshots

Account configuration:

Desktop

OS: Arch Linux
Browser: Brave
Browser Version: 1.26.77
Floccus version: 4.6.4
Floccus sync method: Google drive

Server

Not applicable

Debug log

2021-07-28T07:26:23.644Z Starting sync process for account Google Drive: bookmarks.xbel
2021-07-28T07:26:23.664Z onSyncStart: begin
2021-07-28T07:26:25.000Z Syncing failed with Parse Error: <html xmlns="http://www.w3.org/1999/xhtml"><body><parsererror style="display: block; white-space: pre; border: 2px solid #c77; padding: 0 1em 0 1em; margin: 1em; background-color: #fdd; color: black"><h3>This page contains the following errors:</h3><div style="font-family:monospace;font-size:12px">error on line 1 at column 1: Document is empty
</div><h3>Below is a rendering of the page up to the first error.</h3></parsererror></body></html>
2021-07-28T07:26:25.003Z onSyncFail

Debug log provided

Additional context

I previously set up Floccus (with Google drive) on Firefox on a different machine running Fedora without problems. I have tried removing the bookmarks.xbel file from the Fedora sync, but that did not change the error, and the file is not recreated when syncing from Brave.

Issue Analytics

State:
Created 2 years ago
Comments:7 (4 by maintainers)

Top GitHub Comments

2reactions

marcelklehrcommented, Jul 28, 2021

Maybe parsing errors should hint at this potentially being the problem?

Yeah, just thought the same thing. I’ll change the error message 😃

Cheers!

1reaction

Victor4Xcommented, Jul 28, 2021

Damn, I didn’t remember doing that at all. Thank you! Maybe parsing errors should hint at this potentially being the problem? I don’t think I would’ve thought about it myself :p