Bug: Ferdium Todos - Cannot sign in to Google

[yohoshua]

Avoid duplicates

• [X] I have searched the issues tracker for a bug report similar to mine, in vain

Ferdium Version

6.2.5-nightly.0

What Operating System are you using?

Windows

Operating System Version

Windows 11 Home 22H2

What arch are you using?

x64

Last Known Working Ferdium version

No response

Expected Behavior

When I pull up Google Tasks as a Ferdium Todos option, I expect to be able to log in correctly

Actual Behavior

A "Sign in with Google" prompt says:

Couldn't sign you in

This browser or app may not be secure.

Try using a different browser. If you're already using a supported browser, you can try again to sign in.

Steps to reproduce

1. Go to Settings, Enable Ferdium Todos, select Google Tasks
2. Open the Todos sidebar, try to log in

Debug link

No response

Screenshots

No response

Additional information

This seems to be related to some other issues (#410 in particular), but changing the User Agent in Settings does not seem to fix the issue. Is there somewhere else where the User Agent specifically for the Todos sidebar can be defined? If I load a custom service or any other Google service as a normal service (not a Todo), I am able to log in correctly - problem is limited to the Todos bar.

[yohoshua]

Update: I downgraded to 6.0.0-nightly.7. Trying to use Google Tasks as a Todo service still gets the same message, but I'm able to set the Todo service to tasksboard.com/app and have it log me in, then switch to Google Tasks and it has me still logged in. I then upgraded to version 6.2.4 and that kept me logged in.

[therevoman]

I am experiencing this issue as well. I did downgrade to 6.0.0 but still cannot log in.

[nickchomey]

Same problem for me. I tried to log into a few different Todo services via Google but none worked

[malec985]

same problem:(( still no solution

[enekux]

+1

[ryanphung]

+1

[BugologistX]

same problem, here the error

[aritztg]

Same here, exacly as the previous comment.

[mastercko]

same problem with version 6.2.6

[Nipaleme]

same problem with version 6.2.6 also

[Stafil0]

I just found workaround that works for me: signing in while using the GMail service works just fine, so I copied and replaced all files from AppData\Roaming\Ferdium\recipes\gmail to another "recipe" (in my case it is chatgpt) except for icon.svg and package.json. After that, I successfully singed in Google Account when I used ChatGPT service. Maybe it works for another services as well

[Matosh-fr]

I just found workaround that works for me: signing in while using the GMail service works just fine, so I copied and replaced all files from AppData\Roaming\Ferdium\recipes\gmail to another "recipe" (in my case it is chatgpt) except for icon.svg and package.json. After that, I successfully singed in Google Account when I used ChatGPT service. Maybe it works for another services as well

It works for me too, switching the files exept icon.svg and package.json between gmail and chatgpt in AppData\Roaming\Ferdium

[svatem1]

this is one year old and due to some recent update of the app, I'd have to go through the aforementioned chore again, because my service was overwritten.. you just lost a user, not because of the update, but because of this - logging via google account - still doesn't work and I'm not going through this ritual again, I'm instead exploring different way of achieving what I want / need actually if you think about it - what you're doing? a special kind of web browser (based on chrome's core) where the speciality is nothing but UI & cookies isolation much better way long term will be to find out how to make chrome behave in a way so that i have these 5 services I'm using in a separate window with better UI (some session manager & extension eg.) or use Safari's web app mode and handle the applications via standard way of handling applications on Macos

[nickchomey]

This is happening for me for gmail now...

[nickchomey]

I solved this via the suggestions in these issues - #1179 and #1414.

It seems like we can use anything as the user agent, except a legitimate user agent...