Bug Report: Auth0 SDK Fails on Android Emulator with a0.sdk.internal_error.unknown #1001
Comments
|
I am seeing this same error on my real android device - my android emulator is able to log in as is my iOS device. |
|
Hi @robertevans1, could you share your config details and if you're using webAuth. Thanks |
|
Hi @vjo002 👋 @pmathew92 @arpit-jn and @brth31 are maintaining this project now. They will get back to you soon on this 😄 |
|
@vjo002 Thank you for bringing this issue to our notice. We will take a look at it |
|
Hi @pmathew92, Did you get a chance to look at this issue? Thanks |
|
Hey @vjo002 Can you share the exact emulator configuration? There are certain emulators without Chrome (or any other supported browsers) or without Play services that could cause this issue. Can you confirm that this is not the case? Just to be double sure, can you create a new emulator with Play services and check it for us? |
|
Thanks @poovamraj, I've done some further debugging, and it looks like our network is blocking certain elements in the SDK version. I’m not entirely sure what specifically is being blocked, but I’m more than happy to whitelist any relevant URLs if you can provide them. Also, please note that the iPhone app works fine. Below is the log from Logcat that might help with debugging on your end.
|
|
@vjo002 The callback URL shared through the logs are sensitive, I'd suggest cleaning up the logs.
Can you send the logs that are pointing you to this? |
|
Thanks @poovamraj just cleaned up a bit. That's exactly what I’m trying to pinpoint. The issue doesn't occur outside the secure network, and downgrading to SDK version 2.17.2 works fine within the secure network. It seems like something in SDK version 3.1.0 is causing a conflict with the network. |
|
Can you debug using React Native debugger - https://reactnative.dev/docs/debugging To show us the failing request? |
|
It uses inapp browser to login so can't see any logs in the debugger. But after logging in successfully it throws
|
|
@vjo002 It is even simpler to debug the Chrome Custom Tabs :) You can follow the steps here - https://developer.chrome.com/docs/devtools/remote-debugging |
|
Hey @vjo002 anything on this? |
|
Hi @poovamraj, Thanks for the CCT debugger. Please take a look at the screenshots. Looks like resume request somehow gets canceled every time I login. fyi, Preview and Response tabs are blank
|
|
This is called outside the SDK as you can see this is something our webpage handles. I will raise this internally with the team. You have raised a ticket with us as well. We will continue to analyze this and respond. |
|
Hello @vjo002, we can see that this issue is not related to SDK and since you already have a ticket with Auth0 to look into this, we will continue the conversation there. Feel free to comment here to reopen this ticket if you still consider the issue is on the SDK side. |
Checklist
Description
I am using the Auth0 SDK in a React Native application, and the authentication process works fine on both an iPhone simulator and a physical Android device. However, on the Android emulator, the login attempt fails and enters the catch block with the error: I can also confirm the login was successful from Auth0 dashboard logs.
Code Snippet:
Environment Details:
React Native Version: 0.70.14
React Version: 18.1.0
OS: macOS 14.7
Android SDK: NDK 22.1.7171670
Xcode: 16.1/16B40
Node Version: 21.6.1
npm Version: 10.2.4
Android Studio Version: 2023.1 AI-231.9392.1.2311.11076708
AVD: API 31 - 12
Reproduction
Expected Behavior:
The authorize method should succeed and return an authentication response as expected.
Actual Behavior:
The process fails on the Android emulator with the error: a0.sdk.internal_error.unknown.
Log:
Additional context
The issue does not occur on the iPhone simulator or on a physical Android device.
The error is consistently reproduced when running on the Android emulator.
Possible Causes / Notes:
Request for Help:
react-native-auth0 version
3.1.0
React Native version
0.70.14
Expo version
No response
Platform
Android
Platform version(s)
API 31 - 12
The text was updated successfully, but these errors were encountered: