Tab-Session-Manager
Tab-Session-Manager copied to clipboard
Can't login to google form Ungoogled Chromium
Short description
Unlike Chrome, Ungoogled Chromium cannot login to Google
Steps to reproduce
- Start browser with clean profile
- Install Tab Session Manager
- Enable cloud sync and login to Google.
- error code 400
Expected result
Actual result
cant login with my google account, error code 400
Platform information
- Platform (OS): Windows 10 Home
- Version of browser: Chromium Version 89.0.4389.90 (Official Build, ungoogled-chromium) (64 bit)
- Version of Tab Session Manager: 6.8.1
Additional context
Where did you download Chromium from? I downloaded Chromium from https://download-chromium.appspot.com, and it worked fine.
The redirect_uri
shown in the error screen should be https://iaiomicjabeggjcfkbimgmglanimpnae.chromiumapp.org/
.
from https://ungoogled-software.github.io/ungoogled-chromium-binaries/releases/windows/64bit/89.0.4389.90-1
from https://ungoogled-software.github.io/ungoogled-chromium-binaries
Does the extension just invoke some sort of api of Chromium from the Sign In button? That might be the reason why it is currently broken in Ungoogled Chromium because they removed a bunch of Google's stuff in Chromium.
It might work better if it uses a normal syncing method like Toby does, but with Google as the backend (or something more manual like how Violentmonkey did syncing with dropbox/onedrive/gdrive).
It might work better if it uses a normal syncing method like Toby does, but with Google as the backend (or something more manual like how Violentmonkey did syncing with dropbox/onedrive/gdrive).
how to do it?
This happens to me, too
It might work better if it uses a normal syncing method like Toby does, but with Google as the backend (or something more manual like how Violentmonkey did syncing with dropbox/onedrive/gdrive).
how to do it?
It might be possible, assuming license compatibility, to reuse part of ViolentMonkey's code (https://github.com/violentmonkey/violentmonkey), but first it must be clear what is causing the problem
Same issue, using UnGoogled Chromium latest build.