Close Menu
  • Home
  • AI
  • Big Data
  • Cloud Computing
  • iOS Development
  • IoT
  • IT/ Cybersecurity
  • Tech
    • Nanotechnology
    • Green Technology
    • Apple
    • Software Development
    • Software Engineering

Subscribe to Updates

Get the latest technology news from Bigteetechhub about IT, Cybersecurity and Big Data.

    What's Hot

    Here Come the Women in Construction

    March 3, 2026

    Mobile Spyware: How Hackers Hijack Phones Through App Spyware

    March 3, 2026

    How reversibility becomes irreversible – Physics World

    March 3, 2026
    Facebook X (Twitter) Instagram
    Facebook X (Twitter) Instagram
    Big Tee Tech Hub
    • Home
    • AI
    • Big Data
    • Cloud Computing
    • iOS Development
    • IoT
    • IT/ Cybersecurity
    • Tech
      • Nanotechnology
      • Green Technology
      • Apple
      • Software Development
      • Software Engineering
    Big Tee Tech Hub
    Home»iOS Development»react native – Expo Google OAuth with expo-auth-session: redirect_uri_mismatch and flowName=GeneralOAuthFlow when using auth.expo.io
    iOS Development

    react native – Expo Google OAuth with expo-auth-session: redirect_uri_mismatch and flowName=GeneralOAuthFlow when using auth.expo.io

    big tee tech hubBy big tee tech hubNovember 29, 2025012 Mins Read
    Share Facebook Twitter Pinterest Copy Link LinkedIn Tumblr Email Telegram WhatsApp
    Follow Us
    Google News Flipboard
    react native – Expo Google OAuth with expo-auth-session: redirect_uri_mismatch and flowName=GeneralOAuthFlow when using auth.expo.io
    Share
    Facebook Twitter LinkedIn Pinterest Email Copy Link


    I’m building an Expo React Native app and trying to implement Google Sign-In using
    `expo-auth-session` and `expo-auth-session/providers/google`.

    Environment:
    – React Native (Expo Router)
    – Running in Expo Go on iOS
    – Google OAuth client IDs created in Google Cloud:
    – Web application
    – iOS
    – Android

    import { AntDesign } from '@expo/vector-icons';
    import AsyncStorage from '@react-native-async-storage/async-storage';
    import * as Google from 'expo-auth-session/providers/google';
    import { useRouter } from 'expo-router';
    import * as WebBrowser from 'expo-web-browser';
    import React, { useCallback, useEffect, useState } from 'react';
    import { Alert, Button, Pressable, Text, View } from 'react-native';

    import IconFacebook from '../../../icons/IconFacebook';
    import IconGoogle from '../../../icons/IconGoogle';

    WebBrowser.maybeCompleteAuthSession();

    export default function LoginScreen() {
    const router = useRouter();
    const [, setUserInfo] = useState(null);

    const redirectUri = '

    const [request, response, promptAsync] = Google.useAuthRequest({
    expoClientId:
    '8263....apps.googleusercontent.com',
    iosClientId:
    '8263...apps.googleusercontent.com',
    androidClientId:
    '8263332....apps.googleusercontent.com',
    webClientId:
    '8263332....apps.googleusercontent.com',
    scopes: ['profile', 'email'],
    redirectUri,
    });

    useEffect(() => {
    console.log('Google redirectUri =', request?.redirectUri);
    }, [request]);

    // ...fetchUserInfo + UI omitted for brevity
    }

    On the Google Cloud side, my Web application client with ID:
    '8263332....apps.googleusercontent.com'

    has this Authorized redirect URI configured:

    So I expect that, when running in Expo Go with expoClientId/webClientId, the OAuth request will use that web client and redirect URI.

    However, when I start the login flow and log the generated request, I see this:
    OAuth Request: {
    redirectUri: "",
    request: {
    clientId: "826333210617-dogrjmu5121isqo1gdnblogr23j6qh6b.apps.googleusercontent.com", // <-- iOS client ID
    redirectUri: "",
    responseType: "code",
    scopes: ["profile", "email", "openid", ...],
    url: "
    redirect_uri=https%3A%2F%2Fauth.expo.io%2F%40trieuman2705%2Fbkoo&
    client_id=826333210617-dogrjmu5121isqo1gdnblogr23j6qh6b.apps.googleusercontent.com
    &response_type=code&state=...&scope=..."
    }
    }

    And in the browser I get this error page from Google:
    Error 400: redirect_uri_mismatch
    (Details mention flowName=GeneralOAuthFlow, but the main message is redirect_uri_mismatch)

    So Google is seeing:
    client_id = iOS client ID
    redirect_uri =

    but that redirect is configured for the Web client, not for the iOS client. I’m confused about why expo-auth-session is picking the iOS client ID for this flow when I’m running in Expo Go and I’ve also provided expoClientId/webClientId.



    Source link

    auth.expo.io EXPO expoauthsession flowNameGeneralOAuthFlow Google native OAuth React redirect_uri_mismatch
    Follow on Google News Follow on Flipboard
    Share. Facebook Twitter Pinterest LinkedIn Tumblr Email Copy Link
    tonirufai
    big tee tech hub
    • Website

    Related Posts

    swift – SwiftUI IOS 26 – Menu button floats outside its container during selection animation

    March 3, 2026

    I wish I could be an OpenClaw Maintainer

    March 2, 2026

    performance – The optimal way for loading large video from iOS gallery + reopen it on next app launch

    March 1, 2026
    Add A Comment
    Leave A Reply Cancel Reply

    Editors Picks

    Here Come the Women in Construction

    March 3, 2026

    Mobile Spyware: How Hackers Hijack Phones Through App Spyware

    March 3, 2026

    How reversibility becomes irreversible – Physics World

    March 3, 2026

    Khamenei killing: Is it legal to target a head of state in war?

    March 3, 2026
    About Us
    About Us

    Welcome To big tee tech hub. Big tee tech hub is a Professional seo tools Platform. Here we will provide you only interesting content, which you will like very much. We’re dedicated to providing you the best of seo tools, with a focus on dependability and tools. We’re working to turn our passion for seo tools into a booming online website. We hope you enjoy our seo tools as much as we enjoy offering them to you.

    Don't Miss!

    Here Come the Women in Construction

    March 3, 2026

    Mobile Spyware: How Hackers Hijack Phones Through App Spyware

    March 3, 2026

    Subscribe to Updates

    Get the latest technology news from Bigteetechhub about IT, Cybersecurity and Big Data.

      • About Us
      • Contact Us
      • Disclaimer
      • Privacy Policy
      • Terms and Conditions
      © 2026 bigteetechhub.All Right Reserved

      Type above and press Enter to search. Press Esc to cancel.