Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

screen_hint doesn't work when using the connection param in authorize() #1020

Closed
5 of 6 tasks
frArdouin opened this issue Dec 17, 2024 · 1 comment
Closed
5 of 6 tasks
Labels
bug This points to a verified bug in the code

Comments

@frArdouin
Copy link

frArdouin commented Dec 17, 2024

Checklist

Description

I'm using v3.2.1 of react-native-auth0.

I'm using screen_hint in my authorize function to show the signup prompt in my 2 applications. It's working well for the one that is not using the connection props to target another tenant. When I'm using connection, screen_hint is not taking into account anymore. Maybe because a a redirection that occur afterward. The documentation is not very helping and have very few details about screen_hint.

Reproduction

Here screen_hint will not work (connection to another tenant is needed for this app)

const {accessToken, refreshToken} = await auth0.webAuth.authorize({
    additionalParameters: {
      screen_hint: 'signup',
    },
    audience: AUTH0_AUDIENCE,
    scope: AUTH0_SCOPE,
    connection: AUTH0_CONNECTION,
    maxAge: 0
});

This works (connection to another tenant not needed for the second app)

const {accessToken, refreshToken} = await auth0.webAuth.authorize({
      additionalParameters: {
        screen_hint: 'signup',
      },
      scope: AUTH0_SCOPE,
      audience: AUTH0_AUDIENCE,
      maxAge: 0,
 });

Additional context

No response

react-native-auth0 version

3.2.1

React Native version

0.75.4

Expo version

No response

Platform

iOS

Platform version(s)

16.0

@frArdouin frArdouin added the bug This points to a verified bug in the code label Dec 17, 2024
@Widcket
Copy link
Contributor

Widcket commented Jan 13, 2025

Hi @frArdouin,

When you specify a social connection value, the Auth0 Universal Login page is bypassed, and the other Identity Provider's login page is loaded.

The connection value is specific to Auth0. To configure your connection, check the options available for said connection in the Auth0 Dashboard.

In any case, this is not an SDK issue. If you still need assistance, please open an Auth0 support ticket.

@Widcket Widcket closed this as completed Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This points to a verified bug in the code
Projects
None yet
Development

No branches or pull requests

2 participants