Closed BloodyMonkey closed 1 year ago
i had the same issues and i debugged it by changing :
note*** : you should set up your system environment to your path by adding cmake , mingw64 and MinGW
Like i said, I don't want to enable Hermes.
aah okey so you can enable/disable it manually by replacing flags[:hermes_enabled]
with true
or false
and clean your project before you run it
Lol you don't even read my question.
Plus, flags[:hermes_enabled]
is for iOS
BUT Android compilation seems to use hermes anyway.
That's happening because you're using the New Architecture. For the New Architecture, we have to build React Native from source. Even if you're using JSC, there is a module inside React Native which needs Hermes. That's why you're building it. You won't be using Hermes at runtime thouhg.
In 0.71 we fixed this so you won't be building Hermes at all
@cortinico
Having the same issue, although it is stuck on the buildCMakeDebug
process endlessly ( I've been waiting for more than 1 hour) and it hinders the build process. Is it possible to disable the step somehow in 0.70.5?
Is it possible to disable the step somehow in 0.70.5?
As of now for Windows users experiencing extremely long build time like you, the easiest is to either:
Is it possible to disable the step somehow in 0.70.5?
As of now, the easiest is to either:
- Try 0.71.0-rc2
- Disable the New Architecture on 0.70.5
Thanks! I was able to finally produce a build, leaving only one architecture instead of two in the reactNativeArchitectures
gradle property and running the build within android studio itself.
It seems that running build script using react-native cli is less performant for some reasons.
I forgot to mention that this page contains several tips on how to speedup your build: https://reactnative.dev/docs/next/build-speed
I forgot to mention that this page contains several tips on how to speedup your build: https://reactnative.dev/docs/next/build-speed
It was the first thing a came back to when trying to tackle the issue. Still I have to understand why cli run from VSCode/detached terminal is performing worse than android studio launch.
It could be some system resources distribution, but still.
Still I have to understand why cli run from VSCode/detached terminal is performing worse than android studio launch.
That's because Android Studio lets you pick an Architecture (on the menu on the side) and passes that information to the build system. For the CLI you'll have to use --active-arch-only
or other flags suggested in the page.
Description
I upgraded a project from 0.61.5 to 0.70.5. I disabled hermes because of a conflict with debugging and use_native_modules. BUT Android compilation seems to use hermes anyway.
Tasks like this are run
ReactAndroid:hermes-engine:buildCMakeRelease[x86_64][libhermes]
orReactAndroid:buildCMakeDebug[armeabi-v7a][fabricjni,hermes-executor-debug,etc]
Compilation failed and i suspect it's related.
See my problem here
I'm i missing something ?
Version
0.70.5
Output of
npx react-native info
System: OS: macOS 12.6 CPU: (8) arm64 Apple M1 Memory: 486.47 MB / 16.00 GB Shell: 3.2.57 - /bin/bash Binaries: Node: 19.0.1 - /opt/homebrew/bin/node Yarn: 1.22.19 - /opt/homebrew/bin/yarn npm: 8.19.2 - /opt/homebrew/bin/npm Watchman: 2022.09.12.00 - /usr/local/bin/watchman Managers: CocoaPods: 1.11.3 - /opt/homebrew/bin/pod SDKs: iOS SDK: Platforms: DriverKit 21.4, iOS 16.0, macOS 12.3, tvOS 16.0, watchOS 9.0 Android SDK: Not Found IDEs: Android Studio: 2021.3 AI-213.7172.25.2113.9014738 Xcode: 14.0.1/14A400 - /usr/bin/xcodebuild Languages: Java: 11.0.17 - /Users/bil/.jenv/shims/javac npmPackages: @react-native-community/cli: Not Found react: 18.1.0 => 18.1.0 react-native: 0.70.5 => 0.70.5 react-native-macos: Not Found
Steps to reproduce
Can't reproduce with a fresh project
Snack, code example, screenshot, or link to a repository
android/build.gradle
app/build.gradle