FedCM get() rejects with NetworkError: Error retrieving a token

Question

We tested our application for FedCM changes as mentioned in the Beta Test Program https://developers.google.com/identity/gsi/web/guides/fedcm-migration.

Steps we followed:

1. Enabled the experimental FedCmWithoutThirdPartyCookies feature under chrome://flags.
2. Blocked the third party cookies in browser settings.
3. Have set use_fedcm_for_prompt to true in the IdConfiguration object.
4. We haven't used opt_out_or_no_session in our application.
5. We haven't used position style attributes from data-prompt_parent_id and intermediate_iframes in our application.
6. We have not defined CSP for our website.
7. We haven't used AMP support for our sign for our application.

After making these changes, we see the following:

1. The one tap prompt dialogue doesn't get displayed initially and throws a message 'Third-party sign in was disabled in browser Site Settings'
2. After a minute we also see this error in the console - '[GSI_LOGGER]: FedCM get() rejects with NetworkError: Error retrieving a token.' So basically we do not see the prompt dialogue.

Is this issue related to auto_select : true in the IdConfigurationObject?? The one tap prompt dialogue did not seem to appear even when tried with commenting the 'auto_select : true' parameter.

After making these changes, we see the following:

1. The one tap prompt dialogue doesn't get displayed initially and throws a message 'Third-party sign in was disabled in browser Site Settings'
2. After a minute we also see this error in the console - '[GSI_LOGGER]: FedCM get() rejects with NetworkError: Error retrieving a token.' So basically we do not see the prompt dialogue.

Is this issue related to auto_select : true in the IdConfigurationObject?? The one tap prompt dialogue did not seem to appear even when tried with commenting the 'auto_select : true' parameter.

Answer 1

The One Tap does not display because your browser had the "Third-party sign-in" setting disabled. You can enable it by going to chrome://settings/content/federatedIdentityApi on your Chrome Browser.

Answer 2

I resolved the issue by Removing localhost entry from

chrome://settings/content/federatedIdentityApi