-
Notifications
You must be signed in to change notification settings - Fork 67
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
Glitch - loop to redirect to login popup, not redirect to app #181
Comments
Another weird behavior:
|
Try to replace |
what do you mean ? In my code this is not applicationId, it is literally com.myApp.staging |
If you don't have any variable or placeholder and just string there, double check the app registration - you should have the same |
I tried to create a sample app and it is working as expected on both os. android/build.gradle
gradle-wrapper.properties
AndroidManifest.xml
I mention that when i console.log azure.auth.redirectUri i got the same as the one in app registration and the same as what is in the intent-filter, meaning that the redirectUris matches |
Please check the answer below. I suppose it is your case too: |
I am not sure, because in my case the redirect uri match the one in the app registration |
Just try to use the additional parameter
|
i tried to use the I don't understand what could cause this trouble, since i just did a test by creating a new react-native app, and the flow work perfectly. Feel like something is wrong in our existing app.. |
@vmurin Do you think it's ok to delete the |
no, without intent the android OS will not know which app should be called upon callback. It is your connection between URI and the app. |
remove
|
anyone figured out how to fix it? For me there is also two apps options in the "open the link with" to redirect to the app, both called the same:
I suspect that such behavior is due to having two intent-filters which are both catching redirect, but no, for my application there are only two intent filters: main one, and the one which is explained in readme for this library. I suspect that indeed my main intent filter is somehow catching the redirect, even though in no way it should be able to catch it. It's looking like this:
But why it's happening for my app and not for others? |
what worked for me is to use custom redirect uri, different to default one (your app's package name). Then two redirect options disappear. |
I have implemented an azure login button, the flow is working well on iOS, but on Android there is a glitch that I don’t manage to fix, maybe you have already faced this issue so i take my shot
The button trigger the login popup from Microsoft as expected, but once logged in, instead of redirecting to the app it just bring me to the same page in a loop.. (Again this is not happening on IOS)
Here is a video screen of the glitch.
My manifest is the basic showed in the doc.
And my code is very basic, i create
new AzureAuth
instance and pass my client id. On the login button i call theauthorize
method with the most basic scope.The text was updated successfully, but these errors were encountered: