-
Notifications
You must be signed in to change notification settings - Fork 231
Open
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
I upgraded react-native-auth0 from v4.6.0 to v5.0.1.
authorizeWithSMS now fails with "[InvalidTokenError: Invalid token specified: must be a string]"
My code is the same as before:
creds = await authorizeWithSMS({
phoneNumber: '.....',
code: '.....',
scope: 'offline_access',
audience: '.....'
});
Reproduction
- Send SMS Code using: sendSMSCode({ phoneNumber: '......' });
- Sign in with phone number using the authorizeWithSMS
creds = await authorizeWithSMS({
phoneNumber: '.....',
code: '.....',
scope: 'offline_access',
audience: '.....'
});
I always get the error [InvalidTokenError: Invalid token specified: must be a string]
Additional context
No response
react-native-auth0 version
5.0.1
React Native version
0.80.2
Expo version
No response
Platform
iOS
Platform version(s)
18.3
Metadata
Metadata
Assignees
Labels
bugThis points to a verified bug in the codeThis points to a verified bug in the code