I am working on a Chrome extension that uses the chrome.identity.launchWebAuthFlow API in interactive mode for the authentication process. The chrome.identity API opens a popup with the OAuth2 URL for the user to enter their login credentials. Afterward, I use the authentication response to log the user into the system.
This process works fine on the Windows operating system. However, on macOS, I am encountering an issue. When the user completes the login process in the authentication popup, the extension also closes automatically. This seems to be a issue in Chrome on macOS.
When I perform the same steps with the developer console open, the login process works as expected, and the extension does not close automatically.
I could resolve this issue by using an alternative solution (such as a background.js file), but I need to know if there are any additional configurations required specifically for macOS.
--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/493ff581-b82e-4311-a6e4-98324cf25b74n%40chromium.org.
Configuring chrome.identity.launchWebAuthFlow for Google Sign In in the extension
Handling Google OAuth Authorization Code and Access Token Exchange in a Chrome Extension
Sharing just in case it helps in one area or another.
- Stephen