-
Notifications
You must be signed in to change notification settings - Fork 233
Closed
Labels
bugThis points to a verified bug in the codeThis points to a verified bug in the code
Description
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
Version 5.1.0 crashes on Expo 53 with newArchEnabled: false on iOS with the following error:
Arugument 3 (NSNumber) of A0Auth0.initializeAuth0WithConfiguration has unspecified nullability but React requires than all NSNumbers arguments are explicitly marked as `nonnull` to ensure compatibility with Android.
Reproduction
- Create a new Expo 53 project (e.g.:
npx create-expo-app --template default@53); - In
app.json, set"newArchEnabled": false; - Import
'react-native-auth0'somewhere in the JS/TS code (e.g.:import Auth0 from 'react-native-auth0';); - Build the Expo development client for iOS;
- Install the development client on an iOS device (or on the iOS simulator);
- Start the development server (
expo start --dev-client) and connect the development client to it; - The development client will crash.
Additional context
Example projects, where the error can always be reproduced:
- https://github.com/drubetti/auth0-react-native-sample/tree/master/00-Login-Expo
- https://github.com/drubetti/auth0-expo53-issue-demo
The development client does not crash on Android.
The previous version 5.0.1 works on both Android and iOS.
react-native-auth0 version
5.1.0
React Native version
0.79.2
Expo version
53
Platform
iOS
Platform version(s)
18.6
Metadata
Metadata
Assignees
Labels
bugThis points to a verified bug in the codeThis points to a verified bug in the code