Hi. This is more of a clarification question than an issue. I'm having some difficulty understanding the purpose of the redirectUrl. It seems in all cases it doesn't matter what the redirectUrl is, as long as it matches the auth provider settings and app sheme. On successful auth, the app UI doesn't actually redirect to this url, and instead redirects back to the original screen from where the auth started. Is the AppAuth library handling the redirect url behind the scenes and then redirecting back to the original screen? If so can you confirm we can't actually build a "auth callback" screen in the app?
Many thanks.
Azure B2CiOSHi @masiddee Sorry for tagging you but i'd love to get some clarification on this. It doesn't seem like the auth flow actually redirects back to deeplink as specified by the redirectUrl. Is this the expected behaviour?
I'm essentially trying to provide an "interstitial" state that happens after the browser is closed. At the moment the auth flow is:
Most helpful comment
Hi @masiddee Sorry for tagging you but i'd love to get some clarification on this. It doesn't seem like the auth flow actually redirects back to deeplink as specified by the redirectUrl. Is this the expected behaviour?
I'm essentially trying to provide an "interstitial" state that happens after the browser is closed. At the moment the auth flow is: