Skip to content
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

Authorize promise does not resolve for Microsoft authentication in IOS #1023

Open
bsoft-Paulraj opened this issue Sep 12, 2024 · 2 comments
Open
Labels
needs-repro This issue could be improved with a clear list of steps to reproduce the issue

Comments

@bsoft-Paulraj
Copy link

bsoft-Paulraj commented Sep 12, 2024

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
Copy link

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

@Barak-S
Copy link

Barak-S commented Dec 6, 2024

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.'); });

@carbonrobot carbonrobot added the needs-repro This issue could be improved with a clear list of steps to reproduce the issue label Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-repro This issue could be improved with a clear list of steps to reproduce the issue
Projects
None yet
Development

No branches or pull requests

4 participants