expo: Expo build failed / SDK 48

Removed expo-cli from dependencies, it worked for me

What worked for me was to make sure that the namespace in android/app/build.gradle was correct and then run ./gradlew clean and then run the android app again.

For some reason the namespace generated with expo prebuild was wrong.

I.e. My MainApplication.java file was located in com/company/app folder so the namespace should be com.company.app.

I faced same error.

Expo is generated wrong namespace. I fixed the problem following this is steps;

1. Check your npm project name in package.json file.
2. Check your app.json file, iOS bundleIdentifier and android package paramters must be same as your package.json name with prefix com.

For Example package.json

{
  "name": "foo.bar",
  ...

and app.json

...
 "ios": {
      "supportsTablet": true,
      "bundleIdentifier": "com.foo.bar"....
"android": {
      "package": "com.foo.bar",....

It fixed my problem.

I was able to resolve this issue by running all commands using local package instead of global one i.e.:

• npx expo prebuild instead of expo prebuild
• npx expo run:android instead of expo run:android

Removed expo-cli from dependencies, it worked for me

Very niice, This worked for me.

I deleted android build folder in the root directory & then tried eas build --platform android that seemed to resolve this error.

what a clown fiesta

For me, the problem was wrong configuration entries in expo-build-properties. Removing those fixed it.

["expo-build-properties", {
  android: {
    // compileSdkVersion: 31, <- this is not right
    // targetSdkVersion: 31,
    kotlinVersion: "1.6.21"
  }
}]

I needed this to set a specific Kotlin version for the library I use, but Expo SDK 48 uses Android compileSdkVersion and targetSdkVersion set to API level 33 across all Expo modules. ref: https://blog.expo.dev/expo-sdk-48-ccb8302e231

The compileSdkVersion in particular was the problem for me. I ended up just setting kotlinVersion: "1.6.21" and removing the others and it works fine.

These build settings may be in the library or plugin configs, so I would suggest checking those as well. (You may need to update those libraries or settings)

Se eliminó expo-cli de las dependencias, funcionó para mí

Funciono!

#21477 (comment)

No, it not work ,(

[stderr] /home/expo/workingdir/build/android/app/src/main/java/com/eshka2k23/driver/MainApplication.java:67: error: cannot find symbol
[stderr]     ReactNativeFlipper.initializeFlipper(this, getReactNativeHost().getReactInstanceManager());
[stderr]     ^
[stderr]   symbol:   variable ReactNativeFlipper
[stderr]   location: class MainApplication
[stderr] 1 error
w: Detected multiple Kotlin daemon sessions at build/kotlin/sessions
Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
See https://docs.gradle.org/7.5.1/userguide/command_line_interface.html#sec:command_line_warnings
Execution optimizations have been disabled for 6 invalid unit(s) of work during this build to ensure correctness.
Please consult deprecation warnings for more details.
968 actionable tasks: 968 executed
[stderr] FAILURE: Build completed with 2 failures.
[stderr] 1: Task failed with an exception.
[stderr] -----------
[stderr] * What went wrong:
[stderr] Execution failed for task ':app:compileReleaseJavaWithJavac'.
[stderr] > Compilation failed; see the compiler error output for details.
[stderr] * Try:
[stderr] > Run with --stacktrace option to get the stack trace.
[stderr] > Run with --info or --debug option to get more log output.
[stderr] > Run with --scan to get full insights.
[stderr] ==============================================================================
[stderr] 2: Task failed with an exception.
[stderr] -----------
[stderr] * What went wrong:
[stderr] java.lang.StackOverflowError (no error message)
[stderr] * Try:
[stderr] > Run with --stacktrace option to get the stack trace.
[stderr] > Run with --info or --debug option to get more log output.
[stderr] > Run with --scan to get full insights.
[stderr] ==============================================================================
[stderr] * Get more help at https://help.gradle.org
[stderr] BUILD FAILED in 8m 30s
Error: Gradle build failed with unknown error. See logs for the "Run gradlew" phase for more information.

I dont have “android” folder. I use clean Expo project and i not use any gradle config files.

wow… so the error already occured from the default app??

yes

Same problem, no android folder. Just clean expo project with all default files.

It’s very strange that when I don’t build locally its fine, but when i add the --local tag its suddenly broken 🤔

expo downgrade 47
expo doctor

It make me another problems. I solve all this problems by downgrade to SDK 46.

The history:

1. Half a year ago i am start with SDK 45 (crossplafrom application for iOS and Adroid) ;
2. Month ago - EXPO.IO deprecate SDK 45 ;
3. I am upgrade application (from SDK 45) to SDK 48 and successfuly submit/publish it to Apple Strore and Google Play ;
4. My client asked me to change the color scheme - I changed a value in variables, but the application wasn’t building anymore ;
5. I downgrade from SDK 48 to SDK 46… and oh thank god… This nightmare was over.

What worked for me was to make sure that the namespace in android/app/build.gradle was correct and then run ./gradlew clean and then run the android app again.

For some reason the namespace generated with expo prebuild was wrong.

I.e. My MainApplication.java file was located in com/company/app folder so the namespace should be com.company.app.

What about developers who not use gradle? I seems - SDK 48 from a box (as is) should work without any fixes!!! It may work correctly by default as (for example) SDK 46! Now any build in EXPO is - paid! 1$ - Android and 2$ - iOS, …How its solve the problem? ))) Maybe this will up the quality of the EXPO in the future.

Hi there! It looks like your issue requires a minimal reproducible example, but it is invalid or absent. Please prepare such an example and share it in a new issue.

The best way to get attention to your issue is to provide a clean and easy way for a developer to reproduce the issue on their own machine. Please do not provide your entire project, or a project with more code than is necessary to reproduce the issue.

A side benefit of going through the process of narrowing down the minimal amount of code needed to reproduce the issue is that you may get lucky and discover that the bug is due to a mistake in your application code that you can quickly fix on your own.

Resources

• “How to create a Minimal, Reproducible Example”
• “How to narrow down the source of an error”

Common concerns

“I’ve only been able to reproduce it in private, proprietary code”

You may not have spent enough time narrowing down the root cause of the issue. Try out the techniques discussed in this manual debugging guide to learn how to isolate the problem from the rest of your codebase.

“I didn’t have time to create one”

That’s understandable, it can take some time to prepare. We ask that you hold off on filing an issue until you are able to fully complete the required fields in the issue template.

“You can reproduce it by yourself by creating a project and following these steps”

This is useful knowledge, but it’s still valuable to have the resulting project that is produced from running the steps, where you have verified you can reproduce the issue.

#21477 (comment)

No, it not work ,(

[stderr] /home/expo/workingdir/build/android/app/src/main/java/com/eshka2k23/driver/MainApplication.java:67: error: cannot find symbol
[stderr]     ReactNativeFlipper.initializeFlipper(this, getReactNativeHost().getReactInstanceManager());
[stderr]     ^
[stderr]   symbol:   variable ReactNativeFlipper
[stderr]   location: class MainApplication
[stderr] 1 error
w: Detected multiple Kotlin daemon sessions at build/kotlin/sessions
Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
See https://docs.gradle.org/7.5.1/userguide/command_line_interface.html#sec:command_line_warnings
Execution optimizations have been disabled for 6 invalid unit(s) of work during this build to ensure correctness.
Please consult deprecation warnings for more details.
968 actionable tasks: 968 executed
[stderr] FAILURE: Build completed with 2 failures.
[stderr] 1: Task failed with an exception.
[stderr] -----------
[stderr] * What went wrong:
[stderr] Execution failed for task ':app:compileReleaseJavaWithJavac'.
[stderr] > Compilation failed; see the compiler error output for details.
[stderr] * Try:
[stderr] > Run with --stacktrace option to get the stack trace.
[stderr] > Run with --info or --debug option to get more log output.
[stderr] > Run with --scan to get full insights.
[stderr] ==============================================================================
[stderr] 2: Task failed with an exception.
[stderr] -----------
[stderr] * What went wrong:
[stderr] java.lang.StackOverflowError (no error message)
[stderr] * Try:
[stderr] > Run with --stacktrace option to get the stack trace.
[stderr] > Run with --info or --debug option to get more log output.
[stderr] > Run with --scan to get full insights.
[stderr] ==============================================================================
[stderr] * Get more help at https://help.gradle.org
[stderr] BUILD FAILED in 8m 30s
Error: Gradle build failed with unknown error. See logs for the "Run gradlew" phase for more information.

added new plugin such as

const { withMainApplication } = require('@expo/config-plugins');
const withoutAndroidFlipper = config => {
  return withMainApplication(config, async config => {
    const mainApplication = config.modResults.contents;
    const newContents = mainApplication?.replace(
      "ReactNativeFlipper.initializeFlipper(this, getReactNativeHost().getReactInstanceManager());",
      "",
    );
    config.modResults.contents = newContents;
    return config;
  });
};
module.exports = withoutAndroidFlipper;

and add the link to it inside the app.json “plugins”: [“./plugins/withoutAndroidFlipper”]

Seems like expo team forgot to remove the flipper from the assembled version of the app

I never manage to build the Expo app. it was a wrong decision for me to use it. I can run it in an emulator but when I need to build it I get the same error as yours. too bad.

What worked for me was to make sure that the namespace in android/app/build.gradle was correct and then run ./gradlew clean and then run the android app again.

For some reason the namespace generated with expo prebuild was wrong.

I.e. My MainApplication.java file was located in com/company/app folder so the namespace should be com.company.app.

It worked!! I created my app with the package name “app.name” and for some reason the namespace was “com.name”, it worked as soon as I changed the “com” to “app”

This issue was a journey. I think I finally got everything working the way I needed. I’ll list my steps below.

I basically ran into two main issues:

1. The namespace in android/app/build.gradle was being generated incorrectly (it seemingly references the app name rather than the package ID. For example, my name was “AppName (env)” and my package was “com.app.env”. In the build.gradle, it was using namespace “com.appnameenv” (seems like the app name with parenthesis and spaces removed). This should have been com.app.env and caused things not to load correctly.
2. The release version of ReactNativeFlipper.java is created in the wrong folder AND has the wrong package name. For example, it was being generated in android/app/src/release/java/com/appnameenv/ReactNativeFlipper.java and used package name com.appnameenv. Both of these seem to be based on the app name like above, but it should have been generated as android/app/src/release/java/com/app/env/ReactNativeFlipper.java with package name com.app.env.

It’s important to note that the second issue only appears on release builds (I use expo to create builds in the cloud). The first issue impacts dev builds and release builds.

In order to fix this, I referenced several of the other fixes on this thread to create a single expo plugin that:

1. Fixes the namespace in the build.gradle
2. Removes ReactNativeFlipper from the MainApplication.java (I didn’t need it)

Inside my withAndroidExpoFix.js file:

import { withAppBuildGradle, withMainApplication, createRunOncePlugin } from '@expo/config-plugins';

/**
 * This plugin is a temporary fix that is needed to fix Android builds on Expo 48.
 * There are two main issues:
 * 1. The namespace in android/app/build.gradle needs to match
 * the application id (like com.app.env), but it is set incorrectly
 * 2. The folder structure and package name in android/app/src/release/com/XXX/ReactNativeFlipper.java
 * is not created correctly
 */
const withAndroidExpoFix = (config) => {
  // Fix the namespace in android/app/build.gradle
  config = withAppBuildGradle(config, (config) => {
    const buildGradle = config.modResults.contents;
    const namespace = config?.android?.package?.toString?.();
    const newContents = buildGradle.replace(/namespace (.*)\n/, `namespace '${namespace}'\n`);
    config.modResults.contents = newContents;
    console.log(`[withAndroidExpoFix] Change build.gradle namespace to ${namespace}`);

    return config;
  });

  // Remove ReactNativeFlipper
  config = withMainApplication(config, async (config) => {
    const mainApplication = config.modResults.contents;
    const newContents = mainApplication?.replace(
      'ReactNativeFlipper.initializeFlipper(this, getReactNativeHost().getReactInstanceManager());',
      ''
    );
    config.modResults.contents = newContents;
    console.log(`[withAndroidExpoFix] Remove ReactNativeFlipper`);

    return config;
  });

  return config;
};

export default createRunOncePlugin(withAndroidExpoFix, 'withAndroidExpoFix', '1.0.0');

Inside my app.config.js file:

plugins: [
     // Had to create a custom plugin to fix an Android issue on Expo 48
     './plugins/withAndroidExpoFix'
]

After testing, I’ve been able to run it locally and the release build finally succeeded. Hope this helps anyone else who is dealing with both issues.

It seems I’ve been doing it all wrong this whole time lol. Using npx expo prebuild vs expo prebuild worked for both platforms for the first time. Thank you.

What worked for me was to make sure that the namespace in android/app/build.gradle was correct and then run ./gradlew clean and then run the android app again.

For some reason the namespace generated with expo prebuild was wrong.

I.e. My MainApplication.java file was located in com/company/app folder so the namespace should be com.company.app.

you are right, very strange expo give a wrong namespace.

but the difference is i’m using the old expo eject (it still works perfectly), not expo prebuild, after I upgraded from version 47. So changing it to the correct namespace fixed the debug build.

===

Oh, I have found that ReactNativeFlipper.java in the release folder is created with the wrong package name. do not forget to change it too

I dont have “android” folder. I use clean Expo project and i not use any gradle config files.

wow… so the error already occured from the default app??

Alternatively you can downgrade to 47: expo upgrade 47.

Yes, then after this adjustment make sure your

“resolutions”: { “@expo/config-plugins”: “~6.0.0”, “@expo/prebuild-config”: “~6.0.0”, “expo-modules-autolinking”: “1.1.0” }

is upto date or atleast this version, then run expo doctor to make sure everything is okay from expo end

Well, now the package R does not exist errors are gone.

For the ReactNativeFlipper error you will need this patch: main…iegik:expo:patch-3

Alternatively you can downgrade to 47: expo upgrade 47.

I downgrade to SDK 47 and …get new problems ,( Expo.IO - is deamn hell! Today it work, tomorrow it don’t work ,(

Invariant Violation: Failed to call into JavaScript module method AppRegistry.runApplication(). Module has not been registered as callable. Registered callable JavaScript modules (n = 11): Systrace, JSTimers, HeapCapture, SamplingProfiler, RCTLog, RCTDeviceEventEmitter, RCTNativeAppEventEmitter, GlobalPerformanceLogger, JSDevSupportModule, HMRClient, RCTEventEmitter.
        A frequent cause of the error is that the application entry file path is incorrect. This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.
at node_modules/react-native/Libraries/Core/ExceptionsManager.js:95:17 in reportException
at node_modules/react-native/Libraries/Core/ExceptionsManager.js:141:19 in handleException
at node_modules/react-native/Libraries/Core/setUpErrorHandling.js:24:39 in handleError
at node_modules/expo/build/errors/ExpoErrorManager.js:25:19 in errorHandler
at node_modules/expo/build/errors/ExpoErrorManager.js:30:24 in <anonymous>
at node_modules/@react-native/polyfills/error-guard.js:49:36 in ErrorUtils.reportFatalError

Invariant Violation: ViewPropTypes has been removed from React Native. Migrate to ViewPropTypes exported from 'deprecated-react-native-prop-types'.
at node_modules/react-native/Libraries/Core/ExceptionsManager.js:95:17 in reportException
at node_modules/react-native/Libraries/Core/ExceptionsManager.js:141:19 in handleException
at node_modules/react-native/Libraries/Core/setUpErrorHandling.js:24:39 in handleError
at node_modules/expo/build/errors/ExpoErrorManager.js:25:19 in errorHandler
at node_modules/expo/build/errors/ExpoErrorManager.js:30:24 in <anonymous>
at node_modules/@react-native/polyfills/error-guard.js:49:36 in ErrorUtils.reportFatalError
at node_modules/metro-runtime/src/polyfills/require.js:237:40 in guardedLoadModule
at http://192.168.1.27:19000/node_modules/expo/AppEntry.bundle?platform=ios&dev=true&hot=false&strict=false&minify=false:null in global code

Invariant Violation: Failed to call into JavaScript module method AppRegistry.runApplication(). Module has not been registered as callable. Registered callable JavaScript modules (n = 11): Systrace, JSTimers, HeapCapture, SamplingProfiler, RCTLog, RCTDeviceEventEmitter, RCTNativeAppEventEmitter, GlobalPerformanceLogger, JSDevSupportModule, HMRClient, RCTEventEmitter.
        A frequent cause of the error is that the application entry file path is incorrect. This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.
at node_modules/react-native/Libraries/Core/ExceptionsManager.js:95:17 in reportException
at node_modules/react-native/Libraries/Core/ExceptionsManager.js:141:19 in handleException
at node_modules/react-native/Libraries/Core/setUpErrorHandling.js:24:39 in handleError
at node_modules/expo/build/errors/ExpoErrorManager.js:25:19 in errorHandler
at node_modules/expo/build/errors/ExpoErrorManager.js:30:24 in <anonymous>
at node_modules/@react-native/polyfills/error-guard.js:49:36 in ErrorUtils.reportFatalError