expo: path may not be null or empty string && compileSdkVersion is not specified

I got this after upgrading to Expo SDK 49. iOS build was fine. Android not.

I was getting this error:

A problem occurred evaluating settings 'Sally POS'.
> path may not be null or empty string. path='null'

@samipe solution worked for me, all i had to do is change settings.gradle line 10 to:

includeBuild('../node_modules/@react-native/gradle-plugin')

Thanks @samipe !

@tolypash I got the same error when upgrading to Expo SDK 49 but I think your solution is kind of a weird workaround.

I had a look what the issue with the replaced line of code was. I came to this conclusion: You replaced includeBuild(new File(["node", "--print", "require.resolve('react-native-gradle-plugin/package.json')"].execute(null, rootDir).text.trim()).getParentFile()) with includeBuild('../node_modules/@react-native/gradle-plugin'). My take is, that expo wants to use react-native-gradle-plugin instead of the gradle-plugin inside @react-native.

After executing npx expo install react-native-gradle-plugin it worked without replacing code in settings.gradle.

I got this after upgrading to Expo SDK 49. iOS build was fine. Android not.

I was getting this error:

A problem occurred evaluating settings 'project'.
> path may not be null or empty string. path='null'

@samipe solution worked for me, all i had to do is change settings.gradle line 10 to:

includeBuild('../node_modules/@react-native/gradle-plugin')

Thanks @samipe !

Got this fixed by comparing my existing expo (android) files with latest changes in RN template and copying some changes by hunch: https://react-native-community.github.io/upgrade-helper/?from=0.71.8&to=0.72.1

At least in build.gradle classpath('com.android.tools.build:gradle:7.4.1') to classpath('com.android.tools.build:gradle')

and this abomination in settings.gradle includeBuild(new File(["node", "--print", "require.resolve('@react-native/gradle-plugin')"].execute(null, rootDir).text.trim()).getParentFile()) to includeBuild('../node_modules/@react-native/gradle-plugin')

Also this addition in gradlew, maybe it was necessary? No idea what I’m doing APP_HOME=$( cd "${APP_HOME:-./}" && pwd -P ) || exit

Havent done extensive tests but so far so good with newArchEnabled! 😃

this is happening in bare projects that missed upgrade instructions for the react-native gradle plugin package: https://react-native-community.github.io/upgrade-helper/?from=0.71.0&to=0.72.1#RnDiffApp-android-settings.gradle - the package name changed from react-native-gradle-plugin to @react-native/gradle-plugin.

we use a slightly different version of that diff in android/settings.gradle projects created through create-expo-app/prebuild, in order to support monorepos by default:

includeBuild(new File(["node", "--print", "require.resolve('react-native-gradle-plugin/package.json')"].execute(null, rootDir).text.trim()).getParentFile())

you should change this to:

includeBuild(new File(["node", "--print", "require.resolve('@react-native/gradle-plugin/package.json')"].execute(null, rootDir).text.trim()).getParentFile())

we always recommend reviewing the update helper diff in our upgrade instructions in sdk release notes. if you have any doubt about the changes suggested in upgrade helper diffs, you can refer to a new project on the target sdk version by creating it or looking at the template project on the corresponding sdk branch on github: https://github.com/expo/expo/tree/sdk-49/templates/expo-template-bare-minimum

Just had this issue, running ./gradlew --stop in the android directory to kill all gradle daemons then trying again worked for me.

This is likely caused by stopping an Android build early.

+1 same error here, only on android, iOS build works fine

I got this after upgrading to Expo SDK 49. iOS build was fine. Android not.

I was getting this error:

A problem occurred evaluating settings 'project'.
> path may not be null or empty string. path='null'

@samipe solution worked for me, all i had to do is change settings.gradle line 10 to:

includeBuild('../node_modules/@react-native/gradle-plugin')

Thanks @samipe !

Give this guy some tacos 🌮 🌮 🔥 💯

Same for me but it was because I using

"env": {
        "APP_NAME": "value"
}

in eas.json and it seems that Gradle override this value with “Gradle (Gradle)”.

But imho, the real problem is how node_modules/expo/scripts/resolveAppEntry.js works. It clear the console so the real error was not seen. Any error in this script returns just the infamous

A problem occurred evaluating project ':app'.
> path may not be null or empty string. path=''

trace.

This usually happen if you have a plug-in config but not the package…for instance…you remove mapbox…but still have the config in app.config.js or app.json…that’s what happen in my case…

We are getting the same error 🤔. If anyone comes up with a solution would be appreciated as this is becoming a blocker for our project. Thanks!

I’m encountering this same issue and reproduced it as well with:

❯ npx create-expo-app@latest -t expo-template-blank-typescript test-failed ❯ npx expo run:android

In my actual project I tried the suggestions of using EXPO_DEBUG=“false” as well as copying my app.config.js to app.config.json, neither of which helped.

I just want to share my point of view

to fix this remove your android project files generated by expo remove package-lock.json and node modules

npm install then run the prebuild command again

this is the clean way, we won’t need to patch the older expo configuration this is not the way. this is how i fixed it on my side

I got this after upgrading to Expo SDK 49. iOS build was fine. Android not. I was getting this error:

A problem occurred evaluating settings 'Sally POS'.
> path may not be null or empty string. path='null'

@samipe solution worked for me, all i had to do is change settings.gradle line 10 to: includeBuild('../node_modules/@react-native/gradle-plugin') Thanks @samipe !

@tolypash I got the same error when upgrading to Expo SDK 49 but I think your solution is kind of a weird workaround.

I had a look what the issue with the replaced line of code was. I came to this conclusion: You replaced includeBuild(new File(["node", "--print", "require.resolve('react-native-gradle-plugin/package.json')"].execute(null, rootDir).text.trim()).getParentFile()) with includeBuild('../node_modules/@react-native/gradle-plugin'). My take is, that expo wants to use react-native-gradle-plugin instead of the gradle-plugin inside @react-native.

After executing npx expo install react-native-gradle-plugin it worked without replacing code in settings.gradle.

Thank you @phillihoch, this solution worked for me, just don’t forget to run npx expo prebuild before local build.

just create a project not long ago and had that problem…solved it by doing this rm -rf node_modules && rm -rf yarn.lock && yarn install && yarn run android…

something curious made the android build work, i edited the node_modules/expo/scripts/resolveAppEntry.js hoping to have some debug log, adding a console.log on line 20 of that file and running prebuild + npx expo run:android did the build magically works, I can’t explain why but it worked

NOTE: i tested this in two situations, my actual project and a fresh expo project, same result in both

I experienced the same error mentioned above. If you have config plugins attached to your app.json, make sure to double-check them so that they are correctly installed/configured.

would be good if someone could help to check the error stacktrace. if that the same from Uncaught Error Error: GetEnv.NoBoolean: is not a boolean., would be good to help investigating what is the actual value.

debugging the build code, I found this error:

resolveEntryPoint(projectRoot, { platform })
Uncaught Error Error: GetEnv.NoBoolean:  is not a boolean.
    at boolish (/Users/ag/ofto/mobile/node_modules/getenv/index.js:70:15)
    at <anonymous> (/Users/ag/ofto/mobile/node_modules/getenv/index.js:84:27)
    at <anonymous> (/Users/ag/ofto/mobile/node_modules/@expo/config/build/plugins/withInternal.js:14:42)

to fix it I put EXPO_DEBUG=“false” on build process.

I think this bug is on withInternal.js:14:42