From the sample code, the redirect URI is as follows:
Hey Rama, I appreciate your help on this. I believe that I do actually have it working now. I'm not allowed to share the source code but in case I end up having issues again with this I could pursue one of those other two options.
The re-direct URI seems fine. Would it be possible to share your repro code (using a temporary account) via a direct message or provide network logs via direct message or debug your app through our support?
The main one that I was using was "MobileMap://auth". I had this set as a redirect URI for my ESRI application and also was in the Android code as well (DefaultOAuthIntentReceiver in AndroidManifest.xml and OAuthConfiguration in MainActivity).
Can you share the other re-directURIs format that you specified at the time of registering the app? The browsers expect it to be <my-custom-app-scheme>://<my-custom-app-host>. The semi-colon with two forward slashes is requiredThanksRama
Yes, I am already doing this. I am registering different redirect URIs to my ESRI Application for the given client id. When I reference any redirect URI I already have set that isn't `authenticate-with-oauth://auth` then I just get the infinite loop of being prompted to login. Why is this the only redirect URI that actually navigates back to the app?
Hi,When we register your app for OAuth, we have to specify the re-directURI. For a given ClientID, only the registered re-directURIs are allowed. For the sample, the redirectURI allowed is `authenticate-with-oauth://auth`. You need to register your own app.ThanksRama
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.