Authorize promise does not resolve for Microsoft authentication in IOS

[bsoft-Paulraj]

Issue

I faced a problem of Microsoft authentication authorize promise not resolved or reject in IOS, but it works well in android.

I just have this log in xcode
Background Task 13 ("Called by XXX, from -[RNAppAuth issuer:redirectUrl:clientId:clientSecret:scopes:additionalParameters:serviceConfiguration:skipCodeExchange:useNonce:usePKCE:resolve:reject:]"), was created over 30 seconds ago. In applications running in the background, this creates a risk of termination. Remember to call UIApplication.endBackgroundTask(_:) for your task in a timely manner to avoid this.

Environment
Identity Provider: Custom Oauth2 Compliant Provider
Platform: iOS (13.7 and 10.3.1)
React Native: 0.74.3
React Native App Auth: 8.0.0
Not using Expo

[j-q-in-berlin]

Did you manage to find anything? We ran into a similar issue.

[Barak-S]

Any update here? We are facing the same issue as we are trying to upgrade our authentication from the previously archived "react-native-msal" package. Any progress here would be greatly appreciated

In my example below, we only get the initial log when authorizing. We will get the catch if for example, we terminate the initial msal login screen. However, after entering credentials, the promise seems to hang infinitely rather than resolve and we don't get any additional logging

console.log('Starting signIn process...'); authorize(config) .then(result => { console.log('Authorization Result:', result); }) .catch(error => { console.error('Authorization Error:', error); console.error('Detailed Error Message:', error.message); }) .finally(() => { console.log('signIn function complete.'); });

[lm123987]

Has anyone found any resolutions for this issue? I am all of a sudden encountering it as well in iOS authenticating with Microsoft AD FS. Reproducing with react-native-app-auth versions 6.4.3 (which I've been using for a while with no trouble), 7.2.0, and 8.0.1 on iOS version 18.2. There have been no recent code changes in my app so it seems to me that it may have started with one of the recent iOS version updates.

[Shaddix]

I had the same issue, turns out the redirectUrl field in my config was missing the trailing slash .
I.e. I had
{ ..., redirectUrl: 'my.app.bundle.id://oauth', ...}
changing it to
{ ..., redirectUrl: 'my.app.bundle.id://oauth/', ...}

fixed the issue