AuthSession is the easiest way to implement web browser based authentication (for example, browser-based OAuth flows) to your app, built on top of expo-web-browser.

Do you know why? I remember Expo Go asked me for permission to access external link before open Google's authentication screen on my old login method using AuthSession.startAsync({ authUrl }) (SDK 48) and now it doesn't ask me anymore.

GitHub Auth Example · Copy · import { useEffect } from 'react'; import * as WebBrowser from 'expo-web-browser'; import { makeRedirectUri, useAuthRequest } from 'expo-auth-session'; import { Button } from 'react-native'; WebBrowser.maybeCompleteAuthSession(); // Endpoint const discovery = { authorizationEndpoint: 'https://github.com/login/oauth/authorize', tokenEndpoint: 'https://github.com/login/oauth/access_token', revocationEndpoint: 'https://github.com/settings/connections/applications/<CLIENT_ID>', }; export default function App() { const [request, response, promptAsync] = useAuthRequest

This works because AuthSession adds +expo-auth-session to the default returnUrl; however, if you provide your own returnUrl, you may want to consider adding a similar identifier to enable you to filter out AuthSession events from other handlers.

npm i expo-auth-session · github.com/expo/expo · docs.expo.dev/versions/latest/sdk/auth-session · 420,513 · 7.0.10 · MIT · 395 kB · 104 · 3 days ago · ide · brentvatne · evanbacon · expoadmin · exponent · bycedric · kudochien · alanhughes · expo-bot · wschurman ·

https://github.com/expo/expo/tree/main/packages/expo-auth-session

A fork of the expo-auth-session module to support Auth Code with PKCE, and token refresh. - TransformCore/expo-auth-session

If using Auth0 you need to pass in a path for the return url as well as the scheme. // app.json scheme is robapp // expo 47 const redirectUri = AuthSession.makeRedirectUri({ useProxy }); // expo 48 const redirectUri = AuthSession.makeRedirectUri({ scheme: 'robapp', path: 'root' });

An open-source framework for making universal native apps with React. Expo runs on Android, iOS, and the web. - expo/packages/expo-auth-session/src/providers/Google.ts at main · expo/expo

Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. ... android ios react-native react-navigation styled-components google-oauth async-storage expo victory-native finance-app react-hook-form expo-auth-session

Parse the url and store the session token with SecureStore. // app/App.tsx import * as Browser from "expo-web-browser"; import * as Linking from "expo-linking"; import * as SecureStore from "expo-secure-store"; export default function App() { const signIn = async (): Promise<User | null> => { const result = await Browser.openAuthSessionAsync( "http://localhost:3000/login/github", "exp://192.168.2.100:8081/login" ); if (result.type !== "success") return; const url = Linking.parse(result.url); const sessionToken = url.queryParams?.session_token?.toString() ??

May 23, 2022 - import * as AuthSession from 'expo-auth-session'; import * as WebBrowser from 'expo-web-browser'; import React from 'react'; import {Button} from 'react-native'; WebBrowser.maybeCompleteAuthSession(); function Page() { const [, , promptAsync] = AuthSession.useAuthRequest( { redirectUri: 'https://www.fake_my_app.com/verify', // Fake http redirectUri clientId: '123ABCD456', // Fake client id responseType: 'token', scopes: ['openid'], }, { tokenEndpoint: 'https://fake_open_id.com/token/', authorizationEndpoint: 'https://fake_open_id.com/authorization/', }, ); return <Button title="Handle auth" onPress={() => promptAsync()} />; } export {Page};

docs.expo.dev/versions/latest/sdk/auth-session · github.com/expo/expo · github.com/expo/expo/issues ·

Fix for breaking change in expo-constants to only support new manifests. (#24267 by @wschurman) This version does not introduce any user-facing changes. This version does not introduce any user-facing changes. This version does not introduce any user-facing changes. Remove references to startAsync from js doc. (#23150 by @alanhughes) Remove unnecessary test. (#23154 by @alanhughes) This version does not introduce any user-facing changes. Remove all auth proxy APIs.

August 18, 2022 - You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. ... I implemented Facebook Sign-in with expo-auth-session and when trying to login I get an error in response URL Blocked.

February 3, 2023 - import React, { useEffect } from "react"; import { View, Text, Button } from "react-native"; import * as AuthSession from "expo-auth-session"; import * as Google from "expo-auth-session/providers/google"; import * as WebBrowser from "expo-web-browser"; WebBrowser.maybeCompleteAuthSession(); const SocialLoginOptions = (): JSX.Element => { const [request, response, promptAsync] = Google.useAuthRequest({ androidClientId: "id0000.apps.googleusercontent.com", iosClientId: "id0000.apps.googleusercontent.com", expoClientId: "id0000.apps.googleusercontent.com", }); useEffect(() => { console.log("respo

The setup for Google, Apple, or GitHub will follow the same general steps. The previous diagram shows a high-level overview of the OAuth flow. However, the preferred method for a client to obtain an authorization grant from the user is to use an authorization server as an intermediary, which is exactly what you can build using Expo API Routes.

When you open an authentication session with AuthSession, it first visits https://auth.expo.io/@your-username/your-app-slug/start and passes in the authUrl and returnUrl (the URL to redirect back to your application) in the query parameters.

In May 2020 we rewrote expo-auth-session as a pure JS replacement for most of the authentication systems in Expo.