# Troubleshooting

> [!WARNING]
> **Warning:** The Google Sign-In library optionally uses FedCM APIs, and their use will become a requirement. [Conduct an impact assessment](https://developers.google.com/identity/sign-in/web/gsi-with-fedcm) to confirm that user sign-in continues to function as expected.   
>
> Support for the Google Sign-In library is deprecated, see the [Deprecation and Sunset](https://developers.google.com/identity/sign-in/web/deprecation-and-sunset) guide for more.

## 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](https://developers.google.com/identity/protocols/oauth2/web-server).

### 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](https://github.com/google/google-api-javascript-client/issues)
for any other issue with the Google Sign-In library.