ferdium-app Google Mail not loading (Company login)

Avoid duplicates

[X] I agree to follow the Code of Conduct that this project adheres to.
[X] I have searched the issues tracker for a bug report similar to mine, in vain (older issues were there, but nothing current)

Ferdium Version

7.0.0

What Operating System are you using?

Windows

Operating System Version

Edition Windows 10 Pro Version 22H2 Installed on ‎06/‎08/‎2022 OS build 19045.5131 Experience Windows Feature Experience Pack 1000.19060.1000.0

What arch are you using?

x64

Last Known Working Ferdium version

7.0.0 (it just stopped working suddenly, without updating to a newer Ferdium version, so thats why this is same as above)

Expected Behavior

Service loads and i can read my emails

Actual Behavior

After logging in to my account, there is a short loading animation (something rotating, and google being written). But afterwards, everything is grey. There are no errors in the dev console during this process.

before logging in (aka after doing ctrl R to refresh the service):

after logging in:

after finish rotating:

I have already tried setting user agent to Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36 but it doesn't work.

Gmail still works fine for my personal gmail account, but not for the one at work.

Steps to reproduce

I don't know if this can be reproduced easily with just any login, as for myself it still works fine with my personal account.

But the steps are:

add Gmail service
login with company account
nothing is displayed after logging in

Additional note: after doing ctrl R to reload the service, i have to relogin.

Debug link

No response

Screenshots

No response

Additional information

No response

Nov 19 '24 09:11 Zutatensuppe

Gmail stopped working for me too today. I've done the usual, "Reload", "Clear Cache", "Disable service" + "Enable Service".

Additionally Google Calendar stopped working exactly the same way.

Nov 19 '24 10:11 juha-aiven

We can confirm, that it is also in older versions of ferdium tried Ferdium-win-AutoSetup-6.7.6-x64.exe and cleared also C:\Users\%user%\AppData\Roaming\Ferdium. But no effect, so seems a google issue... It is also happening on our Macs

Nov 21 '24 09:11 bepipelino

I can confirm that this also happens when I tried to login with my university email (Google Workspace). Google Calendar, GMail only show blank page, but still works fine with personal account.

Nov 21 '24 14:11 hyuuki

Similarly also impacted by this issue. I'm seeing the redirect flow from corporate SSO and then it just stops at https://accounts.google.com/a/company.com/acs. I'm seeing a few possibly related errors in the console logs

/Applications/Ferdiu…obalErrorStore.js:1 Warning: findDOMNode is deprecated and will be removed in the next major release. Instead, add a ref directly to the element you want to reference. Learn more about using refs safely here: https://reactjs.org/link/strict-mode-find-node
    at WithSortableContainer (/Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/react-sortable-hoc/dist/react-sortable-hoc.js:614:7)
    at div
    at TabBar (/Applications/Ferdium.app/Contents/Resources/app.asar/components/services/tabs/Tabbar.js:1:1123)
    at div
    at Sidebar (/Applications/Ferdium.app/Contents/Resources/app.asar/components/layout/Sidebar.js:1:2222)
    at /Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/mobx-react/dist/mobxreact.cjs.development.js:524:34
    at injectIntl(inject-with-stores-actions(Sidebar))
    at div
    at div
    at ErrorBoundary (/Applications/Ferdium.app/Contents/Resources/app.asar/components/util/ErrorBoundary/index.js:1:1286)
    at injectIntl(ErrorBoundary)
    at /Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/react-jss/dist/react-jss.cjs.js:420:25
    at AppLayout (/Applications/Ferdium.app/Contents/Resources/app.asar/components/layout/AppLayout.js:1:2936)
    at /Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/react-jss/dist/react-jss.cjs.js:420:25
    at injectIntl(WithStyles(AppLayout))
    at ThemeProvider (/Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/theming/dist/theming.cjs.js:78:37)
    at DefaultPropsProvider (/Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/@mui/system/DefaultPropsProvider/DefaultPropsProvider.js:18:3)
    at RtlProvider (/Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/@mui/system/RtlProvider/index.js:19:7)
    at ThemeProvider (/Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/@mui/private-theming/node/ThemeProvider/ThemeProvider.js:39:5)
    at ThemeProvider (/Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/@mui/system/ThemeProvider/ThemeProvider.js:52:5)
    at ThemeProvider (/Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/@mui/material/node/styles/ThemeProvider.js:21:14)
    at AppLayoutContainer (/Applications/Ferdium.app/Contents/Resources/app.asar/containers/layout/AppLayoutContainer.js:1:1532)
    at /Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/mobx-react/dist/mobxreact.cjs.development.js:524:34
    at RenderedRoute (/Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/react-router/dist/umd/react-router.development.js:539:7)
    at Routes (/Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/react-router/dist/umd/react-router.development.js:1229:7)
    at Router (/Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/react-router/dist/umd/react-router.development.js:1163:17)
    at HistoryRouter (/Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/react-router-dom/dist/umd/react-router-dom.development.js:770:7)
    at FerdiumRoutes (/Applications/Ferdium.app/Contents/Resources/app.asar/routes.js:1:2693)
    at /Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/mobx-react/dist/mobxreact.cjs.development.js:524:34
    at IntlProvider (/Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/react-intl/src/components/provider.js:33:47)
    at I18N (/Applications/Ferdium.app/Contents/Resources/app.asar/I18n.js:1:1030)
    at /Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/mobx-react/dist/mobxreact.cjs.development.js:524:34
    at Provider (/Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/mobx-react/dist/mobxreact.cjs.development.js:493:24)
/Applications/Ferdiu…obalErrorStore.js:1 Warning: Function components cannot be given refs. Attempts to access this ref will fail. Did you mean to use React.forwardRef()?

Check the render method of `EditSettingsForm`.
    at injectIntl(WithStyles(Input))
    at div
    at div
    at form
    at div
    at div
    at EditSettingsForm (/Applications/Ferdium.app/Contents/Resources/app.asar/components/settings/settings/EditSettingsForm.js:1:10294)
    at injectIntl(EditSettingsForm)
    at ErrorBoundary (/Applications/Ferdium.app/Contents/Resources/app.asar/components/util/ErrorBoundary/index.js:1:1286)
    at injectIntl(ErrorBoundary)
    at /Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/react-jss/dist/react-jss.cjs.js:420:25
    at EditSettingsScreen (/Applications/Ferdium.app/Contents/Resources/app.asar/containers/settings/EditSettingsScreen.js:1:10559)
    at /Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/mobx-react/dist/mobxreact.cjs.development.js:524:34
    at injectIntl(inject-with-stores-actions(EditSettingsScreen))
    at RenderedRoute (/Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/react-router/dist/umd/react-router.development.js:539:7)
    at Outlet (/Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/react-router/dist/umd/react-router.development.js:1142:28)
    at div
    at ErrorBoundary (/Applications/Ferdium.app/Contents/Resources/app.asar/components/util/ErrorBoundary/index.js:1:1286)
    at injectIntl(ErrorBoundary)
    at /Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/react-jss/dist/react-jss.cjs.js:420:25
    at div
    at Transition (/Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/react-transition-group/cjs/Transition.js:135:30)
    at CSSTransition (/Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/react-transition-group/cjs/CSSTransition.js:120:35)
    at TransitionGroup (/Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/react-transition-group/cjs/TransitionGroup.js:57:30)
    at Appear (/Applications/Ferdium.app/Contents/Resources/app.asar/components/ui/effects/Appear.js:1:816)
    at SettingsLayout (/Applications/Ferdium.app/Contents/Resources/app.asar/components/settings/SettingsLayout.js:1:1467)
    at injectIntl(SettingsLayout)
    at ErrorBoundary (/Applications/Ferdium.app/Contents/Resources/app.asar/components/util/ErrorBoundary/index.js:1:1286)
    at injectIntl(ErrorBoundary)
    at /Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/react-jss/dist/react-jss.cjs.js:420:25
    at SettingsContainer (/Applications/Ferdium.app/Contents/Resources/app.asar/containers/settings/SettingsWindow.js:1:1437)
    at /Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/mobx-react/dist/mobxreact.cjs.development.js:524:34
    at RenderedRoute (/Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/react-router/dist/umd/react-router.development.js:539:7)
    at Outlet (/Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/react-router/dist/umd/react-router.development.js:1142:28)
    at div
    at div
    at div
    at ErrorBoundary (/Applications/Ferdium.app/Contents/Resources/app.asar/components/util/ErrorBoundary/index.js:1:1286)
    at injectIntl(ErrorBoundary)
    at /Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/react-jss/dist/react-jss.cjs.js:420:25
    at AppLayout (/Applications/Ferdium.app/Contents/Resources/app.asar/components/layout/AppLayout.js:1:2936)
    at /Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/react-jss/dist/react-jss.cjs.js:420:25
    at injectIntl(WithStyles(AppLayout))
    at ThemeProvider (/Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/theming/dist/theming.cjs.js:78:37)
    at DefaultPropsProvider (/Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/@mui/system/DefaultPropsProvider/DefaultPropsProvider.js:18:3)
    at RtlProvider (/Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/@mui/system/RtlProvider/index.js:19:7)
    at ThemeProvider (/Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/@mui/private-theming/node/ThemeProvider/ThemeProvider.js:39:5)
    at ThemeProvider (/Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/@mui/system/ThemeProvider/ThemeProvider.js:52:5)
    at ThemeProvider (/Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/@mui/material/node/styles/ThemeProvider.js:21:14)
    at AppLayoutContainer (/Applications/Ferdium.app/Contents/Resources/app.asar/containers/layout/AppLayoutContainer.js:1:1532)
    at /Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/mobx-react/dist/mobxreact.cjs.development.js:524:34
    at RenderedRoute (/Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/react-router/dist/umd/react-router.development.js:539:7)
    at Routes (/Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/react-router/dist/umd/react-router.development.js:1229:7)
    at Router (/Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/react-router/dist/umd/react-router.development.js:1163:17)
    at HistoryRouter (/Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/react-router-dom/dist/umd/react-router-dom.development.js:770:7)
    at FerdiumRoutes (/Applications/Ferdium.app/Contents/Resources/app.asar/routes.js:1:2693)
    at /Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/mobx-react/dist/mobxreact.cjs.development.js:524:34
    at IntlProvider (/Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/react-intl/src/components/provider.js:33:47)
    at I18N (/Applications/Ferdium.app/Contents/Resources/app.asar/I18n.js:1:1030)
    at /Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/mobx-react/dist/mobxreact.cjs.development.js:524:34
    at Provider (/Applications/Ferdium.app/Contents/Resources/app.asar/node_modules/mobx-react/dist/mobxreact.cjs.development.js:493:24)
/Applications/Ferdiu…tores/AppStore.js:1 [MobX] Since strict-mode is enabled, changing (observed) observable values without using an action is not allowed. Tried to modify: [email protected]
2
node:electron/js2c/renderer_init:2 Uncaught (in promise) Error: Error invoking remote method 'GUEST_VIEW_MANAGER_CALL': Error: Script failed to execute, this normally means an error was thrown. Check the renderer console for the error.
    at IpcRendererInternal.invoke (node:electron/js2c/renderer_init:2:11410)
    at async Promise.all (index 0)
    at async WebViewElement.<anonymous> (/Applications/Ferdiu…s/Service.js:1:8742)
2
/Applications/Ferdiu…i/button/index.js:1 Ferdium Button prop `loaded` will be deprecated in the future. Please use `busy` instead

Nov 21 '24 14:11 wgordon17

I've tried reverting to both 6.7.7 and 6.7.6, however neither have made any improvement for resolving this 😞

Nov 21 '24 15:11 wgordon17

Same problem is in hangouts chat, try to access to company login. Debian Linux, tried 7.0 and 7.0.1 nightly build.

Nov 22 '24 09:11 wardragon

same problem on Fedora 40, ferdium 7.0.0 with company gmail as well as company calendar

Nov 22 '24 10:11 mjankula

Same, corporate GCal and Gmail doesn't work since yesterday, tested on various Ferdium versions

Nov 22 '24 12:11 jaklan

I have the strange feeling, that it has to do with the way google is promoting the use of passkeys during login. I was presented with such dialogs a lot, also in the corporate accounts. Some of my team mates are presented with those "advertisements" during login to use their passkey instead, but they have never set up this feature. Some others are using it, otherwise I would just disable it for testing in the google admin console.

Nov 22 '24 12:11 bepipelino

I can confirm, that only corporate accounts are affected, that use external identity providers (IdP's). Corporate user accounts (like super admins) with a plain google login are not affected.

Nov 22 '24 13:11 bepipelino

Tested with Ferdium Version: 6.7.7 and Version: 7.0.0. Same results. Using corporate accounts with Okta as external identity provider (IdP).

Nov 25 '24 08:11 cr3ation

Same here, fedora 40, ferdium 6.7.7, corporate google services (gmail, gcalendar, ...) are not loaded after login.

Nov 26 '24 08:11 martin-kanis

Same here for corporate gmail services ...

Nov 26 '24 09:11 vdhmax

Maybe it has something to do with certificates? If you search for "GUEST_VIEW_MANAGER_CALL", which is part of my error message, you get a lot of results regarding server certs.

invoking remote method 'GUEST_VIEW_MANAGER_CALL': Error: Script failed to execute, this normally means an error was thrown. Check the renderer console for the error.

In my case, my custom server running https://caddyserver.com/ doesn't load either. The Caddy obtains TLS server certificates at Let's Encrypt. There has been issues about self-signed certs #1850 and #1227, but no issues with Let's Encrypt certs.

Now, there are issues emerging with company services (which probably have some non-standard certificates maybe?).

Nov 26 '24 11:11 Muzosh

Same problem here. Ferdium version 6.7.7

Nov 26 '24 13:11 jmfinelli

I think we're all in the same boat, it's unnecessary at this point to spam "Same here" for all users following this issue with notifications :)

Nov 26 '24 13:11 RomLecat

@vraravam I'm wondering what might be the next steps here? Are there more logs or debug information that we can help provide? Is this something unique to Google/Ferdium/Chromium/Electron? Just wondering what might be possible for tracking this down further

Dec 02 '24 18:12 wgordon17

Same issue. MacOS 14.6.1, Arm64, Ferdium version 7.0.0. Started today, unable to log back into University Gmail. It starts log in, but once I finish entering credentials, the page is blank. Tried reinstalling the current build and then the beta build. I removed Gmail service and added it back.

Dec 02 '24 21:12 spirit1jkm

I can confirm that it is related to Google corporate accounts, no matter what service are you trying to login in. For example, in my case I also have ChatGPT and Trello with same Google corp account and I'm unnable to login.

Dec 03 '24 10:12 mfloresVicomtech

I am curious - is everyone who is having issues using Okta or some other identity provider? Instead of spamming the thread with a reply, a 👍 or 👎 to this message would be a quick way to see.

And by the way, I am not a developer and I almost certainly can not fix the issue but I want to try to narrow down what the problem is if at all possible to make it easier for someone who is able to to fix it.

Dec 03 '24 11:12 mbentley

I am curious - is everyone who is having issues using Okta or some other identity provider? Instead of spamming the thread with a reply, a 👍 or 👎 to this message would be a quick way to see.

And by the way, I am not a developer and I almost certainly can not fix the issue but I want to try to narrow down what the problem is if at all possible to make it easier for someone who is able to to fix it.

It's related to ACS (sample URL: https://accounts.google.com/a/foobar.com/acs), specific IdP shouldn't matter.

https://support.google.com/a/answer/6330801

Dec 03 '24 12:12 jaklan

Issue occurs with Authentik using SAML also. For some reason logins through the browser (I tried Librewolf, and Chrome) works just fine... Just not in Ferdium.

Dec 03 '24 23:12 3gmgithub

We are using out personal identity provider, that use shibbolet. Just worked fine until 2 weeks ago. I want to help to debug, but how to enable debug in ferdium? There is an option unto configuration or a command line or the only way is to use the web debugger application? Thanks

Dec 04 '24 07:12 wardragon

Same issue here (when I login to gmail/calendar with Okta)

I think it's the same than here : https://github.com/ferdium/ferdium-app/issues/1845

Dec 04 '24 14:12 julienchamp

Hello,

Some more details on this. My company account is authenticated with Okta, authentication which is successful.

Okta redirects to https://www.google.com/a/8x8.com/acs and it loads an HTML document which contains a form with some SAML details. The form is auto-submitted using JavaScript. The response is a similar HTML document which contains a similar form that is expected to also be auto-submitted. The problem is that the second request seems to get canceled for some reasons, see below screenshot:

This means the second request never reaches the Google server and the authentication process stops.

What I did to get into the account was to resubmit the second request by typing: document.forms["hiddenpost"].submit(); in the console. This will resubmit the second form and you get authenticated.

Unfortunately, I'm not able to replicate the same flow twice. It worked once, but can't make it work the second time.

Later edit: I managed to make it work the second time, but it's a bit complicated and I'll have to repeat it multiple times and note down the steps. Will update in this thread once I get to a consistent flow if anyone wants to try it out.

Dec 04 '24 21:12 raulmatei

I tried to use @raulmatei's method but it didn't work, here's a screenshot of an error from my console:

Dec 05 '24 00:12 k-y

Here are the steps to make it work on a Windows machine (I don't have access to other OSes but it probably works on these too). It's a very technical flow and it requires a lot of patience. The process is harmless and should not affect anything on your machine, OS or Ferdium app, but try it at your on risk.

open Ferdium and go to the top menu and click on View → Toggle Navigation Bar (Ctrl+B) if the navigation bar it's not visible and then View → Toggle Service Developer Tools (Ctrl+Shift+Alt+I)
the devtools will open as a detached window
on the devtools select the Network tab and enable Preserve log on the first line under the Network tab
move to main Ferdium app window
type your username into the Google signing form and hit Next - it will redirect you to your 3rd party authentication provider (Okta, MS Asure, or any custom ones) - make sure to follow the steps for the authentication process based on the specific provider's flow
once you're redirected to the https://accounts.google.com/a/8x8.com/acs page with a gray background move to the devtools window and try to identify the canceled request:
find the acs request on top of it and click on that row
a separate panel should open on the right presenting more information about the request, go to Response tab on that panel, at this point it should say Failed to load response data: No resource with given identifier found if that's the case, move to next step - if it has content move to step 11
while keeping the acs request selected in the devtools window with the Response tab opened, go back to the main Ferdium app window and type your service url in the address bar: https://calendar.google.com in my case, but it can be any of their services - after this action you should be back to the login form - follow the steps again and pay attention to the detached devtools window - you'll have to select the acs request once it's fired to be able to get the response content, otherwise it will continue to show Failed to load response data: No resource with given identifier found - this is the most tricky part and it requires a lot of patience to get it working - if the requests are fired too fast you have the option to set a throttling profile by selecting one from the top of the devtools window: For me selecting 3G option slows down the request enough to be able to select the first acs request row and get the response content I managed to make it work even without the throttling options selected, but it's too fast sometimes and I miss it. Pay attention that there are some other requests that are fired after this one, please select the first acs request and wait for all requests to finish and then reselect the acs one before the canceled one - even if the panel will be closed the response content will be there if you selected it before the one that's canceled is fired (it's tricky, I know)
once you have it selected and Response tab open, you should see something like this: if you don't see it, repeat step 13 until you get the response content
once you have the response content available click anywhere inside the response tab and then CTRL+A to select the entire content and then CTRL+C to copy it
once you have it copied move to the Elements tab and right click on the <html> tab and select Edit as HTML and then remove everything and paste (CTRL+V) the content copied on the previous step and click outside the box or hit CTRL+ENTER to save it
once you have the HTML content pasted and visible in the Elements tab open the Console panel (hit ESC again if you closed it, if not it should still be at the bottom of the detached devtools window) and type document.forms["hiddenpost"].submit(); (pasting is disabled by default but if you want to just copy/paste it from here, type allow pasting in the console and hit ENTER and it will allow you to paste content, otherwise it will show a warning)
once you have the above command pasted into the console, hit ENTER and wait - this will submit the form inside the HTML content and will finalize the authentication process redirecting you to the selected service (as a side note, if you enabled throttling, disable it before executing this step, to speed up the rest of the process)

Make sure to execute steps 11 to 14 as fast as possible, the credentials will expire in a few minutes and you'll have to repeat the process again from step 9. If the process is successful, close all devtools instances and just use Ferdium as you did before this issue appeared. You'll have to repeat the process once your session expires. You also need to repeat the process for all Google services that are using 3rd party authentication providers. I don't know if there are issues with other non-Google services while using a 3rd party authentication provider and I haven't tested this with anything else than Google services (Gmail and Calendar). Please report back if it works for other cases as it might help other users.

Dec 05 '24 06:12 raulmatei

@raulmatei - thanks for taking the time to outline the steps! This worked for me to allow me to sign in - very tedious but worth it to get it working again. Certainly helps using the newer sandbox feature so that I only had to do the steps once instead of three times for my work services. I hope that the steps might help someone also understand how to resolve the issue as well.

The only thing I also had to do was toggle on the navigation bar from the view menu as I did not have that enabled.

Dec 05 '24 07:12 mbentley

Just as an update, I can simplify steps 1-6 by directly opening View > Toggle Service Developer Tools which is the next item in your screen shot but is truncated. That opens the dev tools for the specific service without having to identify it in the HTML of Ferdium.

Dec 05 '24 11:12 mbentley

Just as an update, I can simplify steps 1-6 by directly opening View > Toggle Service Developer Tools which is the next item in your screen shot but is truncated. That opens the dev tools for the specific service without having to identify it in the HTML of Ferdium.

Great, I'll update the steps later today

Dec 05 '24 11:12 raulmatei