Android build failing on Windows

Development
1

Branch: dev

Post doing yarn install in root of the project and then inside the app-mobile directory, I tried running gradlew.bat installDebug in android directory, resulting in below error:

Task :react-native-quick-crypto:buildCMakeDebug[arm64-v8a] FAILED
C/C++: ninja: error: mkdir(CMakeFiles/reactnativequickcrypto.dir/C/Users/mrjha/Desktop/Personal/Projects/joplin/packages/app-mobile/node_modules): No such file or directory

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':react-native-quick-crypto:buildCMakeDebug[arm64-v8a]'.
com.android.ide.common.process.ProcessException: ninja: Entering directory `C:\Users\mrjha\Desktop\Personal\Projects\joplin\packages\app-mobile\node_modules\react-native-quick-crypto\android.cxx\Debug\4w6p5m1r\arm64-v8a'
ninja: build stopped: .

C++ build system [build] failed while executing:
@echo off
"C:\Users\mrjha\AppData\Local\Android\Sdk\cmake\3.22.1\bin\ninja.exe" ^
-C ^
"C:\Users\mrjha\Desktop\Personal\Projects\joplin\packages\app-mobile\node_modules\react-native-quick-crypto\android.cxx\Debug\4w6p5m1r\arm64-v8a" ^
reactnativequickcrypto
from C:\Users\mrjha\Desktop\Personal\Projects\joplin\packages\app-mobile\node_modules\react-native-quick-crypto\android
ninja: error: mkdir(CMakeFiles/reactnativequickcrypto.dir/C/Users/mrjha/Desktop/Personal/Projects/joplin/packages/app-mobile/node_modules): No such file or directory.

It seems the error is related to react-native-quick-crypto package, there is also a thread on SoF for this: android - React Native quick crypto Encryption build failed - Stack Overflow, but no answers.

Anyone have some idea on this?

2

I haven't come across this error before, but I don't think there is a need to run install from inside the app-mobile directory.

I just run 'yarn install' from the root directory for the initial build of Joplin, then when I make any changes I run 'yarn tsc' from the root as well. If the installDebug command is required for debugging then I can't help you there unfortunately, as I have not attempted to debug the code. But if this is blocking development for you at the time being, you could do things the old fashioned way and add temporary console.log entries to the code and rebuild the typescript, to avoid needing to use a debugger to find the information you need. That's what I have been doing so far