expo: [expo-app-auth][bare] authWithConfiguration throws on Android

Using expo-app-auth in a bare-workflow project throws: Failed to log in ExpoAppAuth.Get Auth: Missing experienceUrl in the experience Constants

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Reactions: 5
  • Comments: 25 (6 by maintainers)

Most upvoted comments

In line 307 in AppAuthModule.java, it checks the experienceUrl if the appOwnership is not standalone. But for bare workflow, the appOwnership is guest.

Changing the line to

if ("expo".equals(constantsService.getAppOwnership())) {

can fix the issue.

But I am not sure if there is any impact on other functions.

In line 307 in AppAuthModule.java, it checks the experienceUrl if the appOwnership is not standalone. But for bare workflow, the appOwnership is guest.

Changing the line to

if ("expo".equals(constantsService.getAppOwnership())) {

can fix the issue.

But I am not sure if there is any impact on other functions.

Man works like a charm.

A comment about the expo, I never use it again in my life, the support is practically non-existent. Every week they change lib or have an update that breaks the project. If you use expo and are reading this, stop using it right now …

I think that’s a legit fix. See here for my (uneducated) guess as to why https://github.com/expo/expo/issues/4544#issuecomment-573102166

@brentvatne Sorry I thought deprecated meant it is supported for now but migration is recommended, wouldn’t dropped support would be a better message than deprecated.

Edit: BTW I moved to react-native-app-auth and its working fine for my use cases