-
Notifications
You must be signed in to change notification settings - Fork 21
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
reason": "TOKEN_RESPONSE_NOT_OK #124
Comments
Looks like there were some items missing in the .env file. After adding those, I get a fresh new error:
Am I supposed to create a user in Twilio? The Auth0 logs show a successful login. |
Hi @ashsharma1 , did you fill out the It seems like you have correctly configured Auth0, but the app is failing at the |
We have an additional README in the server for setup: https://github.com/twilio/twilio-voice-react-native-app/tree/main/server#readme |
Hi @kpchoy Thanks for the prompt response. I have fixed the issues with the .env files and now I am past the stage of getting the user info. Now I get a fresh set of errors in the log.
|
It looks like some of your Twilio env variables are incorrect. Can you double check and make sure those values match the values in Twilio Console. |
After creating a brand new twilio account, I still get errors:
Looks like when the app tries to register for voice, it receives an error. I have checked the token on JWT.io and it looks fine. Can you please update the documentation on what all specific things should we do on a twilio side account to make this work. Thanks. |
The Here is a link to Here is another to Do you have any errors in your server? |
I am running the server in the repo under /server. I have not changed its code in any way. And its doing the auth with auth0 fine. |
Hello @ashsharma1 are you still encountering this issue? |
I set up the app and the server. While authenticated via username+pwd with auth0, I got the following response in the Log:
I didn't see setting up any JWKS in the instructions. Is there anything I am missing here?
The text was updated successfully, but these errors were encountered: