"authorization" works but doesn't return anything

Issue

I’ve got “authorize” to work against the Coinbase API. It authorizes and I get an email from then to say my app has been associated with my account. I also get redirected back to my app using Deep Linking.

The problem is “authorize” doesn’t return anything. I would have expected to receive something?

import { authorize } from 'react-native-app-auth';

authorize() {
    authorize(config)
    .then(response => {
        console.log(response);
    })
    .catch(error => {
        console.log(error);
    });
}

I have also tried this but it doesn’t return anything either:

authorize = async () => {
    try {
        const authState = await authorize(config);
        console.log(authState);
    } catch (error) {
        console.log(error);
    }
};

The only time I see any feedback is if I cancel before it is authorized. Then it says the user has cancelled but if it is successful I get no feedback after returning to the app except for the email from Coinbase saying it was successful.

---

Environment

• Your Identity Provider: Coinbase
• Platform that you’re experiencing the issue on:
  • iOS
  • Android
  • iOS but have not tested behavior on Android
  • Android but have not tested behavior on iOS
  • Both
• Are you using Expo, e.g. ExpoKit?
  • No
  • Yes, I’ve not ejected
  • Yes, but I have ejected to ExpoKit
  • Yes, but I have ejected to vanilla React Native

[boris-etingof-flarehr]

I can confirm, with Azure B2C authorize promise doesn’t get resolved. No exceptions cought. No error logs running this from Xcode. Authentication modal comes up, I can enter the mobile number for TOTP, then enter TOTP code, modal closes but the promise returned by authorize doesn’t get resolved.

UPDATE: In my case redirectUrl value msauth.com.company.app://auth was missing trailing forward slash. That resulted to shouldHandleURL in OIDAuthorizationService.m to return false negative as @mion mentioned. Adding / fixed the issue.

await authorize({
      clientId: 'xxx-xxx-xxx-xxx-xxx',
      redirectUrl: 'msauth.com.company.app://auth/', <--- Added `/` here
      scopes: ['openid', 'offline_access'],
      serviceConfiguration: {
         authorizationEndpoint: `${baseUrl}/authorize`,
         tokenEndpoint: `${baseUrl}/token`,
      },
});

[mion]

@whittlem I was having the exact same issue and I’m using the same approach of having an HTML page redirect to a custom URI (such as foo://auth).

I just tried the update from @pbfrias17 answer and it works! Comment out OIDAuthorizationService.m line 113 and run it again, it should return now. The problem is here in line 113:

  if (![self shouldHandleURL:URL]) {
    return NO;
  }

The problem is that the custom URI that the app receives through deep linking is not the same as the one it was configured with (the one starting with https), and this check returns NO.

Other than this ugly fix, I guess the alternative is to use Universal Links. It would be nice to see some mention of this in the docs because I think lots of people would try this approach before turning to Universal Links.