expo: SDK33 ejected with expokit, android sync failed with 'no value for is provided'

🐛 Bug Report

Environment

Expo CLI 2.19.4 environment info: System: OS: macOS 10.14.5 Shell: 3.2.57 - /bin/bash Binaries: Node: 10.15.3 - ~/.nvm/versions/node/v10.15.3/bin/node Yarn: 1.16.0 - /usr/local/bin/yarn npm: 6.9.0 - ~/.nvm/versions/node/v10.15.3/bin/npm Watchman: 4.9.0 - /usr/local/bin/watchman IDEs: Android Studio: 3.4 AI-183.6156.11.34.5522156 Xcode: 10.2.1/10E1001 - /usr/bin/xcodebuild npmPackages: @types/react: ^16.8.19 => 16.8.19 @types/react-native: ^0.57.60 => 0.57.60 expo: ^33.0.0 => 33.0.4 react: 16.8.3 => 16.8.3 react-native: https://github.com/expo/react-native/archive/sdk-33.0.0.tar.gz => 0.59.8 npmGlobalPackages: expo-cli: 2.19.4

app’s target: ExpoKit (for Android)

Steps to Reproduce

1、expo init project 2、expo eject --eject-method expokit 3、open ejected android project in Android Studio

Expected Behavior

successfully synced

Actual Behavior

sync failed for the following reason:

Execution failed for task ‘:expo-app-auth:processDebugAndroidTestManifest’. Manifest merger failed : Attribute data@scheme at manifestMerger2378475533296953441.xml requires a placeholder substitution but no value for <appAuthRedirectScheme> is provided.

temporary workaround

edit node_modules/expo-app-auth/android/build.gradle and add

manifestPlaceholders = [
    'appAuthRedirectScheme': 'host.exp.exponent'
]

to android.defaultConfig

then the project synced without error, but we consider this a bad practice to have to modify a library file

About this issue

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

Most upvoted comments

@WouterFlorijn Try “gradlew assembleDebug --stacktrace” command. And check errors in detail. I think this is an IDE problem. When I executed gradlew command, I released that actually I’ve diff. error about “androidx”

Same thing as @c00piser - I updated to Android Studio 3.4 and started receiving this error. Downgrading to 3.3.x got rid of it.

I was having the same problem after upgrade Android Studio to ver 3.4. Then I downgrade back to 3.3.2 and the problem solved

having exactly the same issue. same gradle version.

update:

somehow disappeared the error. $ ./gradlew clean restart android studio

all good