[SDK 46] Can't build Android app on AppCenter if Hermes is enabled #18412

TomCorvus · 2022-07-29T07:55:27Z

Summary

Hi 👋
I can't build Android app on AppCenter since SDK 46 if Hermes is enabled.

If I disable Hermes, it's working on AppCenter.
If I try to generate binary with Android Studio on my computer, it's working too (with Hermes or without)
I will send a message to AppCenter team, maybe it miss something on build environment.

Thanks for your help.

I have this error message:

> Task :expo-modules-core:extractReactNativeAARRelease

> Task :expo-modules-core:configureCMakeRelWithDebInfo[arm64-v8a]
Resolved com.google.prefab:cli:2.0.0 in :expo-modules-core:_internal_prefab_binary 
C/C++: prefabcom.google.prefab.api.NoMatchingLibraryException: No compatible library found for //fbjni/fbjni. Rejected the following libraries:
C/C++: prefabandroid.arm64-v8a: User is using a static STL but library requires a shared STL
C/C++: prefabandroid.armeabi-v7a: User is targeting arm64-v8a but library is for armeabi-v7a
C/C++: prefabandroid.x86: User is targeting arm64-v8a but library is for x86
C/C++: prefabandroid.x86_64: User is targeting arm64-v8a but library is for x86_64
C/C++: release|arm64-v8a :CMake Warning (dev) in CMakeLists.txt:
C/C++: release|arm64-v8a :  No project() command is present.  The top-level CMakeLists.txt file must
C/C++: release|arm64-v8a :  contain a literal, direct call to the project() command.  Add a line of
C/C++: release|arm64-v8a :  code such as
C/C++: release|arm64-v8a :    project(ProjectName)
C/C++: release|arm64-v8a :  near the top of the file, but after cmake_minimum_required().
C/C++: release|arm64-v8a :  CMake is pretending there is a "project(Project)" command on the first
C/C++: release|arm64-v8a :  line.
C/C++: release|arm64-v8a :This warning is for project developers.  Use -Wno-dev to suppress it.
C/C++: release|arm64-v8a :CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
C/C++: release|arm64-v8a :Please set them or make sure they are set and tested correctly in the CMake files:
C/C++: release|arm64-v8a :HERMES_LIB
C/C++: release|arm64-v8a :    linked by target "expo-modules-core" in directory /Users/runner/work/1/s/packages/app_name/node_modules/expo-modules-core/android
C/C++: release|arm64-v8a :CMake Generate step failed.  Build files cannot be regenerated correctly.

> Task :expo-modules-core:configureCMakeRelWithDebInfo[arm64-v8a] FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':expo-modules-core:configureCMakeRelWithDebInfo[arm64-v8a]'.
> [CXX1405] error when building with cmake using /Users/runner/work/1/s/packages/app_name/node_modules/expo-modules-core/android/CMakeLists.txt: Build command failed.
  Error while executing process /Users/runner/Library/Android/sdk/cmake/3.18.1/bin/cmake with arguments {-H/Users/runner/work/1/s/packages/app_name/node_modules/expo-modules-core/android -DCMAKE_SYSTEM_NAME=Android -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DCMAKE_SYSTEM_VERSION=27 -DANDROID_PLATFORM=android-27 -DANDROID_ABI=arm64-v8a -DCMAKE_ANDROID_ARCH_ABI=arm64-v8a -DANDROID_NDK=/Users/runner/Library/Android/sdk/ndk/21.4.7075529 -DCMAKE_ANDROID_NDK=/Users/runner/Library/Android/sdk/ndk/21.4.7075529 -DCMAKE_TOOLCHAIN_FILE=/Users/runner/Library/Android/sdk/ndk/21.4.7075529/build/cmake/android.toolchain.cmake -DCMAKE_MAKE_PROGRAM=/Users/runner/Library/Android/sdk/cmake/3.18.1/bin/ninja -DCMAKE_LIBRARY_OUTPUT_DIRECTORY=/Users/runner/work/1/s/packages/app_name/node_modules/expo-modules-core/android/build/intermediates/cxx/RelWithDebInfo/606m4m68/obj/arm64-v8a -DCMAKE_RUNTIME_OUTPUT_DIRECTORY=/Users/runner/work/1/s/packages/app_name/node_modules/expo-modules-core/android/build/intermediates/cxx/RelWithDebInfo/606m4m68/obj/arm64-v8a -DCMAKE_BUILD_TYPE=RelWithDebInfo -DCMAKE_FIND_ROOT_PATH=/Users/runner/work/1/s/packages/app_name/node_modules/expo-modules-core/android/.cxx/RelWithDebInfo/606m4m68/prefab/arm64-v8a/prefab -B/Users/runner/work/1/s/packages/app_name/node_modules/expo-modules-core/android/.cxx/RelWithDebInfo/606m4m68/arm64-v8a -GNinja -DREACT_NATIVE_DIR=/Users/runner/work/1/s/packages/app_name/node_modules/react-native -DREACT_NATIVE_SO_DIR=/Users/runner/work/1/s/packages/app_name/node_modules/expo-modules-core/android/build/react-native-0*/jni -DREACT_NATIVE_TARGET_VERSION=69 -DBOOST_VERSION=1_76_0 -DFOR_HERMES=true -DHERMES_DIR=/Users/runner/work/1/s/packages/app_name/node_modules/hermes-engine}
  -- Detecting C compiler ABI info
  -- Detecting C compiler ABI info - done
  -- Check for working C compiler: /Users/runner/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64/bin/clang - skipped
  -- Detecting C compile features
  -- Detecting C compile features - done
  -- Detecting CXX compiler ABI info
  -- Detecting CXX compiler ABI info - done
  -- Check for working CXX compiler: /Users/runner/Library/Android/sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/darwin-x86_64/bin/clang++ - skipped
  -- Detecting CXX compile features
  -- Detecting CXX compile features - done
  -- Configuring done
  -- Generating done
  
  CMake Warning (dev) in CMakeLists.txt:
    No project() command is present.  The top-level CMakeLists.txt file must
    contain a literal, direct call to the project() command.  Add a line of
    code such as
  
      project(ProjectName)
  
    near the top of the file, but after cmake_minimum_required().
  
    CMake is pretending there is a "project(Project)" command on the first
    line.
  This warning is for project developers.  Use -Wno-dev to suppress it.
  
  CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
  Please set them or make sure they are set and tested correctly in the CMake files:
  HERMES_LIB
      linked by target "expo-modules-core" in directory /Users/runner/work/1/s/packages/app_name/node_modules/expo-modules-core/android
  
  CMake Generate step failed.  Build files cannot be regenerated correctly.

Managed or bare workflow? If you have `ios/` or `android/` directories in your project, the answer is bare!

bare

What platform(s) does this occur on?

Android

SDK Version (managed workflow only)

No response

Environment

  expo-env-info 1.0.5 environment info:
    System:
      OS: macOS 12.4
      Shell: 5.8.1 - /bin/zsh
    Binaries:
      Node: 16.16.0 - /usr/local/bin/node
      Yarn: 3.2.2 - /usr/local/bin/yarn
      npm: 8.11.0 - /usr/local/bin/npm
      Watchman: 2022.05.16.00 - /usr/local/bin/watchman
    Managers:
      CocoaPods: 1.11.3 - /usr/local/bin/pod
    SDKs:
      iOS SDK:
        Platforms: DriverKit 21.4, iOS 15.5, macOS 12.3, tvOS 15.4, watchOS 8.5
    IDEs:
      Android Studio: 2021.2 AI-212.5712.43.2112.8609683
      Xcode: 13.4.1/13F100 - /usr/bin/xcodebuild
    npmPackages:
      expo: ~46.0.1 => 46.0.1 
      react: ^18.0.0 => 18.2.0 
      react-dom: ^18.2.0 => 18.2.0 
      react-native: ~0.69.3 => 0.69.3 
      react-native-web: ^0.18.7 => 0.18.7 
    npmGlobalPackages:
      eas-cli: 0.8.1
      expo-cli: 6.0.0
    Expo Workflow: bare

Reproducible demo

Init a bare expo app, enable Hermes and try to build it with AppCenter.
Sorry to not give repro, but the problem appears on AppCenter with minimal project setup.

The text was updated successfully, but these errors were encountered:

Kudo · 2022-07-29T10:25:21Z

hi there! could you check whether the hermes-engine package is installed and where's its path?

TomCorvus · 2022-07-29T11:04:07Z

Hi @Kudo thank you for your reply.
What command can I type to know that in AppCenter build process?

it it a monorepo, I don't know if it's important to say it

TomCorvus · 2022-07-29T11:06:56Z

Here the AppCenter answer:

Hi There, Thanks for writing to us!

48172022-07-29T07:20:42.5673880Z CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
48182022-07-29T07:20:42.5674880Z Please set them or make sure they are set and tested correctly in the CMake files:
48192022-07-29T07:20:42.5675670Z HERMES_LIB
48202022-07-29T07:20:42.5677110Z linked by target "expo-modules-core" in directory /Users/runner/work/1/s/packages/clementine/node_modules/expo-modules-core/android
48212022-07-29T07:20:42.5678080Z

Is there any env variable need to set for HERMES_LIB to run your build?

Kudo · 2022-08-01T14:48:38Z

@TomCorvus sorry i don't familiar with AppCenter build process. does the problem happen locally by running, e.g. expo run:android ?

TomCorvus · 2022-08-01T16:57:03Z

@Kudo Yes, everything works fine in my local machine. in dev or prod mode.

Kudo · 2022-08-01T18:01:07Z

that's strange. i've tried to use AppCenter with hermes and it works for me. we would need a reproducible example repo for further investigation. or maybe it's worth for you to try EAS Build

expo-bot · 2022-08-02T03:41:32Z

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

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.

EdwardDrapkin · 2022-08-05T08:51:39Z

Did this get fixed?

If so, what was the solution?

TomCorvus · 2022-08-05T09:01:07Z

I gave more information on this issue #18473
wait team answer

The prepareHermes() task was missing a declaration for file dependencies, so builds that were run alongside a clean command failed, for example in AppCenter which runs `clean app:assembleRelease app:bundleRelease` as one command. Fixes expo#18473 and expo#18412

numandev1 · 2022-08-16T18:28:15Z

For temporary use, you can use this patch pacakge expo-modules-core+0.11.3.patch

diff --git a/node_modules/expo-modules-core/android/build.gradle b/node_modules/expo-modules-core/android/build.gradle
index a57c367..93dca88 100644
--- a/node_modules/expo-modules-core/android/build.gradle
+++ b/node_modules/expo-modules-core/android/build.gradle
@@ -93,7 +93,15 @@ if (FOR_HERMES) {
   HERMES_ENGINE_DIR = new File(["node", "--print", "require.resolve('hermes-engine/package.json')"].execute(null, rootDir).text.trim()).parent
   if (REACT_NATIVE_BUILD_FROM_SOURCE) {
     // TODO(@lukmccall): Use Hermes from the `ReactAndroid:hermes-engine`
-    HERMES_AAR = file("$HERMES_ENGINE_DIR/android/hermes-debug.aar")
+    def hermesPackagePath = findNodeModulePath(projectDir, "hermes-engine")
+    if (!hermesPackagePath) {
+      throw new GradleScriptException("Could not find the hermes-engine npm package", null)
+    }
+
+    HERMES_AAR = file("$hermesPackagePath/android/hermes-debug.aar")
+    if (!HERMES_AAR.exists()) {
+      throw new GradleScriptException("The hermes-engine npm package is missing \"android/hermes-debug.aar\"", null)
+    }
   } else {
     def prebuiltAAR = fileTree(REACT_NATIVE_DIR).matching { include "**/hermes-engine/**/hermes-engine-*-debug.aar" }
     if (prebuiltAAR.any()) {
@@ -422,7 +430,21 @@ task prepareFolly(dependsOn: [downloadFolly], type: Copy) {
 }
 // END FOLLy
 
-task prepareHermes() {
+static def findNodeModulePath(baseDir, packageName) {
+  def basePath = baseDir.toPath().normalize()
+  // Node's module resolution algorithm searches up to the root directory,
+  // after which the base path will be null
+  while (basePath) {
+    def candidatePath = Paths.get(basePath.toString(), "node_modules", packageName)
+    if (candidatePath.toFile().exists()) {
+      return candidatePath.toString()
+    }
+    basePath = basePath.getParent()
+  }
+  return null
+}
+
+task prepareHermes(dependsOn: createNativeDepsDirectories) {
   if (!FOR_HERMES) {
     return
   }
@@ -444,7 +466,7 @@ afterEvaluate {
 }
 
 tasks.whenTaskAdded { task ->
-  if (!task.name.contains("Clean") && (task.name.contains('externalNativeBuild') || task.name.startsWith('configureCMake'))) {
+  if (!task.name.contains("Clean") && (task.name.contains('externalNativeBuild') || task.name.startsWith('configureCMake')|| task.name.startsWith('buildCMake'))) {
     def buildType = task.name.endsWith('Debug') ? 'Debug' : 'Release'
     task.dependsOn(extractAARHeaders)
     task.dependsOn(extractJNIFiles)
diff --git a/node_modules/expo-modules-core/android/build/.transforms/230ad94014d7c8012b95e4cd8163400f/results.bin b/node_modules/expo-modules-core/android/build/.transforms/230ad94014d7c8012b95e4cd8163400f/results.bin
new file mode 100644
index 0000000..6e09b8c
--- /dev/null
+++ b/node_modules/expo-modules-core/android/build/.transforms/230ad94014d7c8012b95e4cd8163400f/results.bin
@@ -0,0 +1 @@
+o/out

KrisLau · 2022-08-31T16:12:52Z

@Kudo I'm getting these warnings as well:

Task :expo-modules-core:configureCMakeDebug[armeabi-v7a]
C/C++: prefabcom.google.prefab.api.NoMatchingLibraryException: No compatible library found for //fbjni/fbjni. Rejected the following libraries:
C/C++: prefabandroid.arm64-v8a: User is targeting armeabi-v7a but library is for arm64-v8a
C/C++: prefabandroid.armeabi-v7a: User is using a static STL but library requires a shared STL
C/C++: prefabandroid.x86: User is targeting armeabi-v7a but library is for x86
C/C++: prefabandroid.x86_64: User is targeting armeabi-v7a but library is for x86_64
C/C++: debug|armeabi-v7a :CMake Warning (dev) in CMakeLists.txt:
C/C++: debug|armeabi-v7a :  No project() command is present.  The top-level CMakeLists.txt file must
C/C++: debug|armeabi-v7a :  contain a literal, direct call to the project() command.  Add a line of
C/C++: debug|armeabi-v7a :  code such as
C/C++: debug|armeabi-v7a :    project(ProjectName)
C/C++: debug|armeabi-v7a :  near the top of the file, but after cmake_minimum_required().
C/C++: debug|armeabi-v7a :  CMake is pretending there is a "project(Project)" command on the first
C/C++: debug|armeabi-v7a :  line.
C/C++: debug|armeabi-v7a :This warning is for project developers.  Use -Wno-dev to suppress it.

TomCorvus · 2022-08-31T19:38:49Z

@KrisLau what's your expo version?

KrisLau · 2022-08-31T20:18:13Z

@TomCorvus expo@46.0.9 and I'm using it in a bare react native project with expo-modules. Also, not sure if this is relevant to this at all but running expo doctor yields this:

Expected package @expo/config-plugins@^5.0.0
Found invalid:
  @expo/config-plugins@4.1.5
  @expo/config-plugins@4.1.5
  (for more info, run: npm why @expo/config-plugins)
Some dependencies are incompatible with the installed expo package version:
 - react - expected version: 18.0.0 - actual version installed: 18.2.0
 - react-native-gesture-handler - expected version: ~2.5.0 - actual version installed: 2.6.0
 - react-native-maps - expected version: 0.31.1 - actual version installed: 1.3.1
 - react-native-pager-view - expected version: 5.4.24 - actual version installed: 5.4.25
 - react-native-reanimated - expected version: ~2.9.1 - actual version installed: 2.10.0
 - react-native-safe-area-context - expected version: 4.3.1 - actual version installed: 4.3.3
 - react-native-screens - expected version: ~3.15.0 - actual version installed: 3.17.0
Your project may not work correctly until you install the correct versions of the packages.
To install the correct versions of these packages, please run: expo doctor --fix-dependencies,
or install individual packages by running expo install [package-name ...]

It shouldn't matter that the versions are incompatible with expo right since I'm running them with a bare react native project? Sorry if this is a dumb question I only recently migrated from unimodules so i'm not sure

alperenkarip · 2022-10-12T11:00:10Z

@KrisLau I am also getting the same error. were you able to fix this?

KrisLau · 2022-10-12T13:39:37Z

@alperenkarip I can't remember what I did that fixed it but make sure to look at the setup documentation for expo modules in addition to the migration document because the migration is missing a bunch of steps

saeedghasemi72 · 2022-10-18T14:40:05Z

same error, can anyone help us?

AjayParambath · 2022-10-20T08:30:27Z

I'm facing a similar error

Execution failed for task ':expo-modules-core:buildCMakeDebug'.
> Build command failed.
  Error while executing process D:\SDK\cmake\3.10.2.4988404\bin\ninja.exe with arguments {-C D:\ACSL PROJECTS\Nagaland Project New\mobile-app\node_modules\expo-modules-core\android\.cxx\Debug\662s1p2f\x86 expo-modules-core}
  ninja: Entering directory `D:\ACSL PROJECTS\Nagaland Project New\mobile-app\node_modules\expo-modules-core\android\.cxx\Debug\662s1p2f\x86'

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

My version :

react native 0.69.5
gradle  plugin version : 7.0.4
gradle : 7.3.3

App works fine during local build and debugging with metrobundler, but when creating signed apk it shows error

mi-mazouz · 2022-11-07T13:27:31Z

Still having this issue

Execution failed for task ':expo-modules-core:configureCMakeDebug[arm64-v8a]'.
> [CXX1212] project/node_modules/expo-modules-core/android/CMakeLists.txt debug|arm64-v8a : User is using a static STL but library requires a shared STL [//fbjni/fbjni]

Xt-Man · 2022-11-07T19:04:45Z

Hi, I´m having similar issue
`Task :expo-updates:copyReleaseJniLibsProjectOnly

Task :expo-modules-core:configureCMakeRelWithDebInfo[x86]
C/C++: prefabcom.google.prefab.api.NoMatchingLibraryException: No compatible library found for //fbjni/fbjni. Rejected the following libraries:
C/C++: prefabandroid.arm64-v8a: User is targeting x86 but library is for arm64-v8a
C/C++: prefabandroid.armeabi-v7a: User is targeting x86 but library is for armeabi-v7a
C/C++: prefabandroid.x86: User is using a static STL but library requires a shared STL
C/C++: prefabandroid.x86_64: User is targeting x86 but library is for x86_64
C/C++: release|x86 :CMake Warning (dev) in CMakeLists.txt:
C/C++: release|x86 : No project() command is present. The top-level CMakeLists.txt file must
C/C++: release|x86 : contain a literal, direct call to the project() command. Add a line of
C/C++: release|x86 : code such as
C/C++: release|x86 : project(ProjectName)
C/C++: release|x86 : near the top of the file, but after cmake_minimum_required().
C/C++: release|x86 : CMake is pretending there is a "project(Project)" command on the first
C/C++: release|x86 : line.
C/C++: release|x86 :This warning is for project developers. Use -Wno-dev to suppress it.
Task :app:bundleReleaseJsAndAssets
info Writing bundle output to:, /home/expo/workingdir/build/android/app/build/generated/assets/react/release/index.android.bundle
info Writing sourcemap output to:, /home/expo/workingdir/build/android/app/build/generated/sourcemaps/react/release/index.android.bundle.map
info Done writing bundle output
info Done writing sourcemap output
info Copying 18 asset files
info Done copying assets
Task :app:generatePackageList
Task :app:preBuild
Task :app:preReleaseBuild
Task :app:compileReleaseAidl NO-SOURCE
Task :app:compileReleaseRenderscript NO-SOURCE
Task :app:generateReleaseBuildConfig
Task :app:javaPreCompileRelease
Task :app:mergeReleaseShaders
Task :app:compileReleaseShaders NO-SOURCE
Task :app:copyReactNativeVectorIconFonts
Task :app:generateReleaseAssets
Task :app:generateReleaseResValues
Task :app:generateReleaseResources
Task :app:createReleaseCompatibleScreenManifests
Task :app:extractDeepLinksRelease
Task :app:extractProguardFiles
Task :app:mergeReleaseJniLibFolders
Task :expo-updates:compileReleaseKotlin FAILED
[stderr] e: /home/expo/workingdir/build/node_modules/expo-updates/android/src/main/java/expo/modules/updates/errorrecovery/ErrorRecovery.kt: (7, 34): Unresolved reference: DefaultNativeModuleCallExceptionHandler
[stderr] e: /home/expo/workingdir/build/node_modules/expo-updates/android/src/main/java/expo/modules/updates/errorrecovery/ErrorRecovery.kt: (19, 41): Unresolved reference: DefaultNativeModuleCallExceptionHandler
[stderr] e: /home/expo/workingdir/build/node_modules/expo-updates/android/src/main/java/expo/modules/updates/errorrecovery/ErrorRecovery.kt: (67, 60): Unresolved reference: DefaultNativeModuleCallExceptionHandler
[stderr] e: /home/expo/workingdir/build/node_modules/expo-updates/android/src/main/java/expo/modules/updates/errorrecovery/ErrorRecovery.kt: (68, 7): 'handleException' overrides nothing
[stderr] e: /home/expo/workingdir/build/node_modules/expo-updates/android/src/main/java/expo/modules/updates/errorrecovery/ErrorRecovery.kt: (77, 35): Unresolved reference: DefaultNativeModuleCallExceptionHandler
Task :expo-modules-core:buildCMakeRelWithDebInfo[x86]
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.`

KrisLau · 2022-11-07T19:22:28Z

Not sure if this is related to anyone's problem here but just in case:

[FIXED] Android build failures No matching variant of com.facebook.react:react-native:0.71.0-rc.0 was found. facebook/react-native#35210

Xt-Man · 2022-11-08T11:12:26Z

Hi @KrisLau , You're right sorry.
The link you post, solve my issue, thank you

bilmapay · 2022-11-12T07:44:31Z

Still having this issue

Execution failed for task ':expo-modules-core:configureCMakeDebug[arm64-v8a]'.
> [CXX1212] project/node_modules/expo-modules-core/android/CMakeLists.txt debug|arm64-v8a : User is using a static STL but library requires a shared STL [//fbjni/fbjni]

Hay, where you able to fix this and how please. Your issue is the same with mine. Thanks

SE-Umee · 2023-02-09T23:47:46Z

have someone fixed the issue?

TomCorvus added the needs validation Issue needs to be validated label Jul 29, 2022

brentvatne added the incomplete issue: missing or invalid repro A minimal reproducible example is required for most issues label Aug 2, 2022

expo-bot closed this as completed Aug 2, 2022

EdwardDrapkin mentioned this issue Aug 5, 2022

Add a missing gradle task dependency declaration #18518

Merged

frankcalise mentioned this issue Oct 17, 2022

Boilerplate Android build fails on Appcenter with "Could not read script '/' as it is a directory." infinitered/ignite#2049

Closed

frankcalise mentioned this issue Jan 17, 2023

[CXX1405] error when building with cmake using .../node_modules/expo-modules-core/android/CMakeLists.txt: Build command failed. infinitered/ignite#2355

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[SDK 46] Can't build Android app on AppCenter if Hermes is enabled #18412

[SDK 46] Can't build Android app on AppCenter if Hermes is enabled #18412

TomCorvus commented Jul 29, 2022 •

edited

Kudo commented Jul 29, 2022

TomCorvus commented Jul 29, 2022 •

edited

TomCorvus commented Jul 29, 2022 •

edited

Kudo commented Aug 1, 2022

TomCorvus commented Aug 1, 2022

Kudo commented Aug 1, 2022

expo-bot commented Aug 2, 2022

EdwardDrapkin commented Aug 5, 2022

TomCorvus commented Aug 5, 2022 •

edited

numandev1 commented Aug 16, 2022

KrisLau commented Aug 31, 2022 •

edited

TomCorvus commented Aug 31, 2022

KrisLau commented Aug 31, 2022

alperenkarip commented Oct 12, 2022

KrisLau commented Oct 12, 2022

saeedghasemi72 commented Oct 18, 2022

AjayParambath commented Oct 20, 2022 •

edited

mi-mazouz commented Nov 7, 2022 •

edited

Xt-Man commented Nov 7, 2022

KrisLau commented Nov 7, 2022 •

edited

Xt-Man commented Nov 8, 2022

bilmapay commented Nov 12, 2022

SE-Umee commented Feb 9, 2023

[SDK 46] Can't build Android app on AppCenter if Hermes is enabled #18412

[SDK 46] Can't build Android app on AppCenter if Hermes is enabled #18412

Comments

TomCorvus commented Jul 29, 2022 • edited

Summary

Managed or bare workflow? If you have ios/ or android/ directories in your project, the answer is bare!

What platform(s) does this occur on?

SDK Version (managed workflow only)

Environment

Reproducible demo

Kudo commented Jul 29, 2022

TomCorvus commented Jul 29, 2022 • edited

TomCorvus commented Jul 29, 2022 • edited

Kudo commented Aug 1, 2022

TomCorvus commented Aug 1, 2022

Kudo commented Aug 1, 2022

expo-bot commented Aug 2, 2022

Resources

Common concerns

"I've only been able to reproduce it in private, proprietary code"

"I didn't have time to create one"

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

EdwardDrapkin commented Aug 5, 2022

TomCorvus commented Aug 5, 2022 • edited

numandev1 commented Aug 16, 2022

KrisLau commented Aug 31, 2022 • edited

TomCorvus commented Aug 31, 2022

KrisLau commented Aug 31, 2022

alperenkarip commented Oct 12, 2022

KrisLau commented Oct 12, 2022

saeedghasemi72 commented Oct 18, 2022

AjayParambath commented Oct 20, 2022 • edited

mi-mazouz commented Nov 7, 2022 • edited

Xt-Man commented Nov 7, 2022

KrisLau commented Nov 7, 2022 • edited

Xt-Man commented Nov 8, 2022

bilmapay commented Nov 12, 2022

SE-Umee commented Feb 9, 2023

TomCorvus commented Jul 29, 2022 •

edited

Managed or bare workflow? If you have `ios/` or `android/` directories in your project, the answer is bare!

TomCorvus commented Jul 29, 2022 •

edited

TomCorvus commented Jul 29, 2022 •

edited

TomCorvus commented Aug 5, 2022 •

edited

KrisLau commented Aug 31, 2022 •

edited

AjayParambath commented Oct 20, 2022 •

edited

mi-mazouz commented Nov 7, 2022 •

edited

KrisLau commented Nov 7, 2022 •

edited