javascript - Testing Google One Tap - closed and now getting "suppressed-by-user" message - Stack Overflow

admin管理员组

文章数量:1415644

I am adding the Google One Tap api to a React application. I am correctly getting the one tap login modal showing up. However, I clicked to close the modal, and now am getting the following response, which I see is based on the cool down period for this api:

{
  "g": "display",
  "h": false,
  "j": "suppressed_by_user"
}

Since I am testing the application, is there a way to override this cool down period?

Looks like the following:

  ponentDidMount() {
    const handleCredentialResponse = response => {
      console.log(response);
    };
    const client_id = "424242424-example26example44examplexyz.apps.googleusercontent";
    const callback = handleCredentialResponse;
    const auto_select = true;

    google.accounts.id.initialize({ client_id, callback, auto_select });

    google.accounts.id.prompt(notification => {
      console.log(notification);
    });
  }

I am adding the Google One Tap api to a React application. I am correctly getting the one tap login modal showing up. However, I clicked to close the modal, and now am getting the following response, which I see is based on the cool down period for this api:

{
  "g": "display",
  "h": false,
  "j": "suppressed_by_user"
}

Since I am testing the application, is there a way to override this cool down period?

Looks like the following:

  ponentDidMount() {
    const handleCredentialResponse = response => {
      console.log(response);
    };
    const client_id = "424242424-example26example44examplexyz.apps.googleusercontent.";
    const callback = handleCredentialResponse;
    const auto_select = true;

    google.accounts.id.initialize({ client_id, callback, auto_select });

    google.accounts.id.prompt(notification => {
      console.log(notification);
    });
  }

• javascript
• reactjs
• google-api
• google-signin
• google-one-tap

Share Improve this question Follow edited Jul 15, 2020 at 10:21 Vadim Kotov 8,28488 gold badges5050 silver badges6363 bronze badges asked Jul 14, 2020 at 20:35 maudulusmaudulus 11.1k1111 gold badges8585 silver badges121121 bronze badges

Add a ment  | 

3 Answers 3

Sorted by: Reset to default 4

When trying to migrate to the FedCM API for Google One tap the accepted answer did not work for me.

The docs mention that:

When FedCM is enabled, Chrome users can reset cooldown status by clicking on the lock icon in the address bar and clicking the Reset Permission button.

Just click on the icon next to URL in the address bar, and select Site Settings

And then select Reset Permissions and Reload.

I think I've solved the issue. I had to follow the following guide in order to fully clear out the cache for the localhost:3000: https://superuser./questions/278948/clear-cache-for-specific-domain-name-in-chrome

F12 > Chrome Developer Tools > Application tab > Clear storage in left tree > Select all data items > click Clear site data

Another way to avoid 'cool down' during developement is to use incognito browser mode.

You can restart the incognito browser to clear all cached content.

本文标签： javascriptTesting Google One Tapclosed and now getting quotsuppressedbyuserquot messageStack Overflow