Skip to main content

Common Issues

This guide covers the top 10 most common issues users encounter with OneTap Login and how to resolve them.

1. One Tap Popup Not Appearing​

Symptoms​

  • No Google popup when visiting the page
  • Button works but One Tap doesn't show
  • Works on some browsers but not others

Causes​

CauseLikelihood
User not logged into GoogleHigh
User dismissed One Tap previouslyHigh
FedCM not supported (older browser)Medium
Cookie consent not givenMedium
Site not using HTTPSMedium
Third-party cookies blockedMedium

Solutions​

  1. Check Google login status

    • User must be logged into Google in their browser
    • Try visiting gmail.com to verify

  2. Cooldown period

    • Google enforces cooldown after dismissal
    • Wait 2 hours or clear Google cookies

  3. Browser compatibility

    • Chrome 117+ uses FedCM (more reliable)
    • Safari has stricter privacy controls
    • Try Chrome for testing

  4. Cookie consent

    • If using cookie consent plugin, ensure consent given
    • Check settings: Auto-detect vs Never wait

  5. HTTPS requirement

    • Must use HTTPS (except localhost)
    • Check SSL certificate is valid

  6. Third-party cookies

    • Check browser settings allow third-party cookies for google.com
    • Or use browsers with FedCM support

Quick Test​

1. Open Chrome Incognito
2. Log into Google
3. Visit your My Account page
4. One Tap should appear

2. "Invalid Origin" Error​

Symptoms​

  • Error in browser console
  • Error: Invalid origin for client
  • Button doesn't load or shows error

Cause​

Your site's domain is not in the Authorized JavaScript Origins in Google Cloud Console.

Solution​

  1. Go to Google Cloud Console
  2. Select your project
  3. Go to APIs & Services > Credentials
  4. Click your OAuth 2.0 Client ID
  5. Add your domain to Authorized JavaScript Origins: 
    https://yourdomain.com
    https://www.yourdomain.com
  6. Save changes
  7. Wait 5 minutes for propagation
  8. Hard refresh your site (Ctrl+Shift+R)

Common Mistakes​

WrongCorrect
http://yourdomain.comhttps://yourdomain.com
https://yourdomain.com/https://yourdomain.com
Missing www variantAdd both with and without www

3. "redirect_uri_mismatch" Error​

Symptoms​

  • Error page from Google
  • Error 400: redirect_uri_mismatch
  • Shows during OAuth flow

Cause​

The redirect URI doesn't match what's configured in Google Cloud Console.

Solution​

  1. Go to Google Cloud Console > Credentials
  2. Edit your OAuth Client ID
  3. Add to Authorized redirect URIs: 
    https://yourdomain.com/wp-json/onetap/v1/callback
  4. Also add www variant if used: 
    https://www.yourdomain.com/wp-json/onetap/v1/callback
  5. Save and wait 5 minutes

Verify Your URI​

In WordPress, go to Settings > OneTap Login and look for the callback URL shown in the settings.

4. Connection Test Fails​

Symptoms​

  • Test Connection shows red X
  • "Invalid Client ID" or "Invalid Client Secret"
  • Can't save settings

Solutions by Error​

Invalid Client ID:

  1. Copy Client ID from Google Cloud Console
  2. Paste exactly, no spaces
  3. Check for correct project
  4. Verify client type is "Web application"

Invalid Client Secret:

  1. Copy Client Secret (or create new one)
  2. Paste exactly, no spaces
  3. Secrets can only be viewed once when created

REST API Error:

  1. Check if REST API is accessible
  2. Test: https://yourdomain.com/wp-json/
  3. Security plugins may block REST API

HTTPS Error:

  1. Site must use HTTPS
  2. Check SSL certificate is valid
  3. Force HTTPS via WordPress settings

Google API Error:

  1. Enable "Google Identity Services" API
  2. Configure OAuth consent screen
  3. Check project quota

5. User Created But Can't Log In​

Symptoms​

  • Account created successfully
  • But login fails next time
  • Or wrong account accessed

Causes​

  1. Account not linked: Google ID not saved to user
  2. Email conflict: Different user has same email
  3. Role issue: User role was changed

Solutions​

  1. Check user meta:

    • Go to Users > Edit User
    • Look for Google ID in user meta
    • If missing, user must re-link

  2. Email conflict:

    • Search users by email
    • Ensure no duplicates
    • Merge accounts if needed

  3. Test with new Google account:

    • Use different Google account
    • Verify new account links properly

6. Button Looks Wrong or Distorted​

Symptoms​

  • Button appears stretched or squished
  • Missing styling
  • Wrong size

Causes​

  1. Theme CSS conflicts
  2. Container too narrow
  3. JavaScript not loading

Solutions​

  1. Check container width:

    .onetap-button-container {
        min-width: 250px;
    }

  2. Reset conflicting CSS:

    .g_id_signin iframe {
        border: none !important;
        max-width: none !important;
    }

  3. Verify scripts loading:

    • Check browser console for errors
    • Google's GSI script should load

  4. Test with default theme:

    • Switch to Twenty Twenty-Four
    • If fixed, issue is theme-specific

7. Infinite Redirect Loop​

Symptoms​

  • Page keeps reloading
  • "Too many redirects" error
  • Never finishes logging in

Causes​

  1. Caching plugin caching logged-in state
  2. Redirect URL misconfigured
  3. Security plugin blocking

Solutions​

  1. Clear all caches:

    • WordPress cache
    • Browser cache
    • CDN cache (Cloudflare, etc.)

  2. Check redirect settings:

    • Disable custom redirects temporarily
    • Use default WordPress redirect

  3. Exclude from caching:

    Exclude URLs:
    /wp-json/onetap/*
    /my-account/*

  4. Check security plugins:

8. "Email Already Exists" Error​

Symptoms​

  • Error when trying to register
  • "An account with this email already exists"
  • Can't complete sign-in

What's Happening​

The Google email matches an existing WordPress user, but account linking is disabled or failed.

Solutions​

  1. Enable Account Linking:

    • Settings > OneTap Login > Users
    • Enable "Link existing accounts by email"

  2. Use Account Merge (PRO):

    • Requires password verification
    • More secure for existing accounts

  3. Manual linking:

    • User logs in with password first
    • Then links Google account in profile

  4. Different email:

    • User has different email in Google vs WordPress
    • Update WordPress email to match

9. Login Works on Desktop, Not Mobile​

Symptoms​

  • Google sign-in works on computer
  • Fails or looks wrong on phone
  • One Tap doesn't appear on mobile

Causes​

  1. Mobile browser restrictions
  2. Responsive CSS issues
  3. Touch target too small

Solutions​

  1. One Tap on mobile:

    • Works differently on mobile
    • May show as bottom sheet instead of popup
    • Requires user action on iOS

  2. Button responsiveness:

    @media (max-width: 768px) {
        .onetap-button-container {
            width: 100%;
        }
    }

  3. Test specific devices:

    • iOS Safari
    • Android Chrome
    • Samsung Internet

  4. In-app browsers:

    • Facebook/Instagram in-app browsers may not work
    • Redirect to system browser if possible

10. PRO Features Not Working​

Symptoms​

  • PRO features show as disabled
  • License active but features unavailable
  • Analytics not recording

Causes​

  1. License not activated
  2. License on different site
  3. Plugin needs update
  4. Cache issue

Solutions​

  1. Check license status:

    • Settings > OneTap Login > License
    • Verify "Active" status

  2. Deactivate/Reactivate:

    • Deactivate license
    • Clear cache
    • Reactivate license

  3. Check site URL:

    • License tied to specific domain
    • www vs non-www matters

  4. Update plugin:

    • PRO features may need latest version
    • Check for updates

  5. Contact support:

    • If still not working, contact PRO support

Quick Diagnostic Checklist​

Before contacting support, check:

  • HTTPS is working
  • Client ID correct (no extra spaces)
  • Client Secret correct
  • Origins/URIs configured in Google Cloud
  • Test Connection passes (5 green checks)
  • Tested in incognito/private mode
  • Tested with different browser
  • Checked browser console for errors
  • Disabled caching temporarily
  • Tested with default theme

Still Having Issues?​

See these specific guides:

Next Steps​