I implemented Azure AD B2C for authorization following the documentation, with the redirect URL set to 'com.myapp.app://auth/callback'. and also added the deep linking to the forgot password screen navigation with the schema "myapp.app"
In the Azure AD B2C login flow, the forgot password link is set to "myapp.app://forgotpassword". On Android, everything works as expected—when the forgot password link is clicked, the authorize function throws an error, which triggers navigation to the correct screen via deep linking. However, on iOS, the authorize function neither returns nor throws an error, causing it to get stuck.
Issue
I implemented Azure AD B2C for authorization following the documentation, with the redirect URL set to 'com.myapp.app://auth/callback'. and also added the deep linking to the forgot password screen navigation with the schema "myapp.app"
In the Azure AD B2C login flow, the forgot password link is set to "myapp.app://forgotpassword". On Android, everything works as expected—when the forgot password link is clicked, the authorize function throws an error, which triggers navigation to the correct screen via deep linking. However, on iOS, the authorize function neither returns nor throws an error, causing it to get stuck.
Is there a workaround or fix for this issue?
Environment
Azure AD B2C
iOS
0.75.2
8.0.0