v5.0.0-beta4 "Argument 12 (NSNumber) of A0Auth0.webAuth must not be null" when running authorize function

[ScopeSV]

Checklist

• The issue can be reproduced in the react-native-auth0 sample app (or N/A).
• I have looked into the Readme, Examples, and FAQ and have not found a suitable solution or answer.
• I have looked into the API documentation and have not found a suitable solution or answer.
• I have searched the issues and have not found a suitable solution or answer.
• I have searched the Auth0 Community forums and have not found a suitable solution or answer.
• I agree to the terms within the Auth0 Code of Conduct.

Description

I am upgrading an expo app to SDK 53, and with that, the auth0 package.
As the older packages aren't supported any longer, I have upgraded from 4.0.0 to 5.0.0-beta4.
I have done a complete prebuild, after deleting node modules, android and iOS dir, and lock file.

The app starts up fine, however when I run the authorize function from import { useAuth0 } from 'react-native-auth0' I get an error Argument 12 (NSNumber) of A0Auth0.webAuth must not be null

There are no errors in either the console or the React native dev tools console. The error is only visible in the app itself.

I haven't edited any configs from the Expo SDK 53 and auth0 4.0.0

plugins section in app.config

  [
            'react-native-auth0',
            {
                domain: 'login.24sevenoffice.com',
            },
  ],

What could this mean?

I am happy to more info if needed.

Thanks.

Reproduction

See above

Additional context

No response

react-native-auth0 version

5.0.0-beta.4

React Native version

0.79.5

Expo version

53.0.0

Platform

iOS

Platform version(s)

15.1

[subhankarmaiti]

Hi @ScopeSV,
Thanks for reporting this. Could you share the authorize call along with the parameters you're passing, including the Provider parameter?

[ScopeSV]

Thanks for your quick reply!
The authorize call looks like this

             const authResult = await authorize({
                 scope: APP_SCOPES.join(' '),
                 audience: 'https://***',
                 additionalParameters: {
                     prompt: 'login',
                     state,
                 },
             })

I have also tried with an empty function as the types indicate that both paramters are optional

authorize(
    parameters?: WebAuthorizeParameters,
    options?: NativeAuthorizeOptions,
): Promise<Credentials>

The error is the same.

The provider looks like this

 <Auth0Provider
                    domain={'theDomain'}
                    clientId={constants.AUTH0_CLIENT_ID}
                >

This configuration is identical to the one used in 4.0.0

[subhankarmaiti]

Looks like the issue has been resolved in PR #1257.
The fix should be available in the next release.

To confirm this, could you modify your authorize call to

const authResult = await authorize({
                 scope: APP_SCOPES.join(' '),
                 audience: 'https://***',
                 additionalParameters: {
                     prompt: 'login',
                     state,
                 },
             }, 
              {
                useSFSafariViewController: true
              })

or

const authResult = await authorize({
                 scope: APP_SCOPES.join(' '),
                 audience: 'https://***',
                 additionalParameters: {
                     prompt: 'login',
                     state,
                 },
             }, 
              {
                useSFSafariViewController: {
                  presentationStyle: 99
                }
              })

[ScopeSV]

@subhankarmaiti Thanks for that. I can confirm this is working.
useSFSafariViewController: true

What does this do? And is this good enough for a production app until the next release?

[subhankarmaiti]

Hi @ScopeSV,
We don't recommend using v5.0.0-beta4 in production yet, as it includes major architectural changes.
For now, you can either stick with the latest stable version or use v5.0.0-beta2, which includes TurboModule and React 19 support without the broader architectural changes.

[ScopeSV]

Thanks @subhankarmaiti
I do not believe the latest stable version would work in this case as it doesnt use Swift.
I can try beta2 and see how that works.

Is there an estimate when v5 would be stable enough for production?

[subhankarmaiti]

Thanks @ScopeSV for trying it out and sharing your feedback — that's exactly what we're looking for from the community to gain more confidence in this major refactor.
We're actively collecting input to help us move toward a stable GA release as soon as possible. Tentatively, you can expect the GA version to be released in about a month.

[CodingItWrong]

Thanks for the report @ScopeSV and the answer @subhankarmaiti! I ran into the same issue and was about to report it. The useSFSafariViewController: true worked for us as well.

In case it's helpful to anyone, I was able to replicate it in the sample app here: https://github.com/CodingItWrong/react-native-auth0/tree/webAuth-argument-12-error/00-Login-Expo

Also, if it wasn't already clear, I only get the error when running with old architecture. When running on the new architecture in the sample app, I don't get the error.

[subhankarmaiti]

Closing this issue since it has been resolved in version v5.0.0-beta.5.

[ScopeSV]

Is v5.0.0-beta.5 safe (ish) to use in a production app?
Earlier we spoke about beta.2 being the best bet for production. What is the state of beta.5?

[subhankarmaiti]

Based on the feedback we received, this version includes all fixes and improvements. It is very stable and quite close to the final stable release.