Stay organized with collections
Save and categorize content based on your preferences.
Supported environments
Google Sign-In officially supports the following browsers and platforms:
Google Chrome on macOS, Windows, Linux, Android, iOS
Mozilla Firefox on macOS, Windows, Linux
Safari on macOS and iOS
Internet Explorer versions from 8 to 11 on Windows
Microsoft Edge on Windows
Known issues
The following are known issues that you might encounter when using Google
Sign-In.
Third-party cookies and data blocked
When enabled, this privacy feature deactivates all cookies and storage within
the iframe. Google requires this for secure user authentication.
One solution is to ask users who have disabled third-party data to create an
exception for https://accounts.google.com by adding accounts.google.com to
the allowed domains. In Chrome, do this in chrome://settings/cookies.
If many of your users enable this feature (some companies enforce this
setting for all their employees), another workaround is to implement a
server-side OAuth 2.0 flow.
Chrome on iOS in Incognito Mode
Google Sign-in does not support incognito mode on Chrome on iOS.
Safari with Intelligent Tracking Prevention
This new feature of macOS High Sierra and iOS 11 deactivates third-party cookies
every 24 hours, unless the user interacts with one of the page of the
third-party domain. The Google Sign-in library relies on cookies to securely
authenticate the user. It potentially detects that the user is logged out every
24 hours. The user must go through the sign in flow again to reactivate the
cookies.
Any other issue?
Go to our
GitHub issue tracker
for any other issue with the Google Sign-In library.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-05 UTC."],[[["\u003cp\u003eGoogle Sign-In is being deprecated; consult the Deprecation and Sunset guide for more information and migration planning.\u003c/p\u003e\n"],["\u003cp\u003eFedCM APIs will become mandatory for the Google Sign-In library, requiring an impact assessment to ensure continued functionality.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Sign-In supports a range of browsers and platforms, including Chrome, Firefox, Safari, Internet Explorer, and Edge.\u003c/p\u003e\n"],["\u003cp\u003ePotential issues include third-party cookie blocking and Intelligent Tracking Prevention, with solutions and workarounds detailed within the content.\u003c/p\u003e\n"]]],[],null,["# Troubleshooting\n\n| **Warning:** The Google Sign-In library optionally uses FedCM APIs, and their use will become a requirement. [Conduct an impact assessment](/identity/sign-in/web/gsi-with-fedcm) to confirm that user sign-in continues to function as expected. \n|\n| Support for the Google Sign-In library is deprecated, see the [Deprecation and Sunset](/identity/sign-in/web/deprecation-and-sunset) guide for more.\n\nSupported environments\n----------------------\n\nGoogle Sign-In officially supports the following browsers and platforms:\n\n- Google Chrome on macOS, Windows, Linux, Android, iOS\n- Mozilla Firefox on macOS, Windows, Linux\n- Safari on macOS and iOS\n- Internet Explorer versions from 8 to 11 on Windows\n- Microsoft Edge on Windows\n\nKnown issues\n------------\n\nThe following are known issues that you might encounter when using Google\nSign-In.\n\n### Third-party cookies and data blocked\n\nWhen enabled, this privacy feature deactivates all cookies and storage within\nthe iframe. Google requires this for secure user authentication.\n\nOne solution is to ask users who have disabled third-party data to create an\nexception for `https://accounts.google.com` by adding `accounts.google.com` to\nthe allowed domains. In Chrome, do this in `chrome://settings/cookies`.\n\nIf many of your users enable this feature (some companies enforce this\nsetting for all their employees), another workaround is to implement a\n[server-side OAuth 2.0 flow](https://developers.google.com/identity/protocols/oauth2/web-server).\n\n### Chrome on iOS in Incognito Mode\n\nGoogle Sign-in does not support incognito mode on Chrome on iOS.\n\n### Safari with Intelligent Tracking Prevention\n\nThis new feature of macOS High Sierra and iOS 11 deactivates third-party cookies\nevery 24 hours, unless the user interacts with one of the page of the\nthird-party domain. The Google Sign-in library relies on cookies to securely\nauthenticate the user. It potentially detects that the user is logged out every\n24 hours. The user must go through the sign in flow again to reactivate the\ncookies.\n\nAny other issue?\n----------------\n\nGo to our\n[GitHub issue tracker](https://github.com/google/google-api-javascript-client/issues)\nfor any other issue with the Google Sign-In library."]]