🔧 ninja: error: manifest 'build.ninja' still dirty after 100 tries #1941
Comments
osaidfaisal12
added
the
🔧 build error
|
huh, that's weird. maybe it was the deleteCmakeCache change |
mrousavy
changed the title
|
Does this fix your issue? #1945 |
|
Exactly the same issue for me, unfortunately that patch doesn't fix it. I previously had an identical issue when trying to build with the react-native-vision-camera package alone. The issue was due to the path length of the target folder being longer than 160 chars (I think this is a Windows limit) - the issue resolved itself when I moved the project to a parent folder. Unfortunately the explicit error message isn't shown even with verbose logging. |
|
ohh, so maybe this is just a Windows error. I don't know, I don't have a windows pc then. If you find a fix please let me know & submit a PR! |
The error disappear. but the app is crashing and it is showing "app keeps stopping" and the below description. com.facebook.jni.CppException: Compiling JS failed: 1:1:invalid empty parentheses '( )' Buffer size 3 starts with: 280a29 |
|
@osaidfaisal12 did you install react-native-worklets-core accordingly? Including the babel plugin, then restart metro with clean cache? If yes, try upgrading to latest Reanimated. |
Tried everything even download reanimated and latest version of worklets and vision camera but still app is crashing. info Opening the app on Android...
BUILD SUCCESSFUL in 55s LOG Running "campro" with {"rootTag":11} |
|
@mrousavy |
|
I believe this is just an issue on Windows, I was running into it as well while making Android builds, until I swapped to my Macbook and suddenly had no build issues. |
|
Just a weird problem with Windows. |
|
Yep also confirmed the problem goes away when you move the project to a directory with a shorter absolute file path. I've spent an unnecessary amount of time trying to find other workarounds involving CMake and ninja configuration and none of it made any difference. Ultimately it seems like an issue with ninja and Windows rather than anything specific to this project |
|
Yea this sucks. Windows paths are weird and very wanky when used with such cross-platform build systems. I think we can close this as this is not related to my library |
thanks @james-cohen , this worked for me |
|
Just a weird problem with Windows. |
Thank you |
|
For those who try a shorter path directory of project and still does not work. I suffer the same experiences and even try moving in a shorter directory won't work. What fixes my problems in Windows is syncing the time. Go to Date & Time > Additional Settings> Sync Now. Even though you set the time zone automatically, still try the Sync Now button (chances are there might be delay in time) I found the solution here: |
Thank you, I did not expect this to solve my problem but it did! |
Solved this issue for me too 🙏👍 |
has been solved, thank you |
|
After a little digging, I found this. For someone like me who is building projects in a mono repo, I cannot just simply move directories. I'm pretty much already at the root of the drive (F:/Projects) but my RN projects live inside directories like client/mobile/<app_name> that uses imports from ./_shared and such. Hopefully the patch in the link can be incorporated into this library. |
Thanks @james-cohen for sharing this here, it resolved the issue for me. |
it worked for me. |
|
i also get this error , but i didn't resolved it
FAILURE: Build failed with an exception.
BUILD FAILED in 3m 38s |
|
C:\Users\Admin\Desktop\Traveloacco UserProfile\travelacco-mobile-rn Traveloacco UserProfile contains space. try to move your project travelacco-mobile-rn in Desktop. |
How were you trying to build the app?
I tried to build my app using "npx react-native run-android" but failed. It is working fine if I uninstall worklets core library and not use frame processor. But when I use frame processor and worklets core then this issue occurs.
Full build logs
Project dependencies
{ "name": "testcamera", "version": "0.0.1", "private": true, "scripts": { "android": "react-native run-android", "ios": "react-native run-ios", "lint": "eslint .", "start": "react-native start", "test": "jest" }, "dependencies": { "react": "18.2.0", "react-native": "0.72.5", "react-native-reanimated": "^3.5.4", "react-native-vision-camera": "^3.3.1", "react-native-worklets-core": "^0.2.1" }, "devDependencies": { "@babel/core": "^7.20.0", "@babel/preset-env": "^7.20.0", "@babel/runtime": "^7.20.0", "@react-native/eslint-config": "^0.72.2", "@react-native/metro-config": "^0.72.11", "@tsconfig/react-native": "^3.0.0", "@types/react": "^18.0.24", "@types/react-test-renderer": "^18.0.0", "babel-jest": "^29.2.1", "eslint": "^8.19.0", "jest": "^29.2.1", "metro-react-native-babel-preset": "0.76.8", "prettier": "^2.4.1", "react-test-renderer": "18.2.0", "typescript": "4.8.4" }, "engines": { "node": ">=16" } }VisionCamera Version
3.3.1
Target platforms
Android
Operating system
Windows
Can you build the VisionCamera Example app?
Yes, I can successfully build the Example app here
Additional information
The text was updated successfully, but these errors were encountered: