E018 on GrapheneOS/Android during sync

[alexkg413]

Which version of floccus are you using?

5.4.5

How many bookmarks do you have, roughly?

50

Are you using other means to sync bookmarks in parallel to floccus?

No

Sync method

Google Drive

Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.

GrapheneOS/Android 15

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

The extension seems to be working in Brave, but the mobile app is giving "E018: Couldn't authenticate with server" every time it tries to sync. I have not gotten it to successfully connect to my synced bookmarks from the mobile app yet.

Expected Behavior

I would expect the mobile app to show something like the green checkmark and "All good" like in the Brave extension, but since I haven't gotten it to work on mobile yet I don't know

To Reproduce

I successfully logged in with Google and the correct Profile name and Bookmarks file name show up in the mobile app. Then from the first sync attempt on mobile the E018 began appearing with "No bookmarks here":

2025-05-29T17:34:44.440Z Starting sync process for account <>
2025-05-29T17:34:44.448Z onSyncStart: begin
2025-05-29T17:34:44.569Z Failed to authenticate to Google API: [<>]
2025-05-29T17:34:44.572Z Syncing failed with E018: Couldn't authenticate with the server.
2025-05-29T17:34:44.588Z onSyncFail

Debug log provided

• I have provided a debug log file

[github-actions]

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. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings.
I'm Marcel. I created floccus a few years ago, and have been maintaining it 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. It helps when you stick around to answer follow up questions I may have,
as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report
and the issue cannot be solved without it, I will have to close the issue after a while.
Note also that GitHub in general 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!
If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way,
I ask that you donate to the project when opening an issue (or at least once your issue is solved), if you're not a donor already.
You can find donation options at https://floccus.org/donate/. Thank you!

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 Nextcloud 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.

Thank you for reading through this primer. I look forward to working with you on this issue!
Cheers 💙