realm-js icon indicating copy to clipboard operation
realm-js copied to clipboard

What went wrong: Execution failed for task ':realm:configureCMakeDebug[arm64-v8a]'.

Open SrinjoyBarman opened this issue 1 year ago • 9 comments

How frequently does the bug occur?

Always

Description

What went wrong: Execution failed for task ':realm:configureCMakeDebug[arm64-v8a]'. [CXX1420]/node_modules/realm/binding/android/CMakeLists.txt debug|arm64-v8a : Could not read '/realm/binding/android/.cxx/Debug/4b4ho4y1/arm64-v8a/configure_fingerprint.bin': While parsing a protocol message, the input ended unexpectedly in the middle of a field. This could mean either that the input has been truncated or that an embedded message misreported its own length.

Stacktrace & log output

No response

Can you reproduce the bug?

Always

Reproduction Steps

No response

Version

latest - 12.13.0

What services are you using?

Local Database only

Are you using encryption?

Yes

Platform OS and version(s)

react native 0.75.1

Build environment

Which debugger for React Native: ..

Cocoapods version

No response

SrinjoyBarman avatar Aug 19 '24 05:08 SrinjoyBarman

➤ PM Bot commented:

Jira ticket: RJS-2890

sync-by-unito[bot] avatar Aug 19 '24 05:08 sync-by-unito[bot]

The same error

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':realm:buildCMakeDebug[arm64-v8a][realm-js-android-binding]'.
> com.android.ide.common.process.ProcessException: ninja: Entering directory `/Users/pprnd/Documents/yalla_cashier/node_modules/realm/binding/android/.cxx/Debug/4u3k63y5/arm64-v8a'
  [1/6] Building CXX object CMakeFiles/realm-js-android-binding.dir/src/main/cpp/jni_utils.cpp.o
  [2/6] Building CXX object CMakeFiles/realm-js-android-binding.dir/src/main/cpp/platform.cpp.o
  [3/6] Building CXX object CMakeFiles/realm-js-android-binding.dir/Users/pprnd/Documents/yalla_cashier/node_modules/realm/binding/jsi/react_scheduler.cpp.o
  FAILED: CMakeFiles/realm-js-android-binding.dir/Users/pprnd/Documents/yalla_cashier/node_modules/realm/binding/jsi/react_scheduler.cpp.o 
  /Users/pprnd/Library/Android/sdk/ndk/26.1.10909125/toolchains/llvm/prebuilt/darwin-x86_64/bin/clang++ --target=aarch64-none-linux-android23 --sysroot=/Users/pprnd/Library/Android/sdk/ndk/26.1.10909125/toolchains/llvm/prebuilt/darwin-x86_64/sysroot -DREALM_APP_SERVICES=1 -DREALM_DEBUG=1 -DREALM_ENABLE_SYNC=1 -DREALM_HAVE_EPOLL=1 -Drealm_js_android_binding_EXPORTS -I/Users/pprnd/Documents/yalla_cashier/node_modules/realm/binding/android/.. -I/Users/pprnd/Documents/yalla_cashier/node_modules/realm/binding/android/../../binding/jsi -I/Users/pprnd/Documents/yalla_cashier/node_modules/realm/binding/android/../../bindgen/src -I/Users/pprnd/Documents/yalla_cashier/node_modules/realm/binding/android/../../bindgen/vendor/realm-core/bindgen/src -I/Users/pprnd/Documents/yalla_cashier/node_modules/react-native/ReactCommon/callinvoker -isystem /Users/pprnd/Documents/yalla_cashier/node_modules/realm/prebuilds/android/arm64-v8a/include -isystem /Users/pprnd/Documents/yalla_cashier/node_modules/realm/binding/android/.cxx/Debug/4u3k63y5/arm64-v8a/openssl/include -isystem /Users/pprnd/.gradle/caches/8.8/transforms/01d6119a8d36e0b6029d3bf994628a51/transformed/react-android-0.75.1-debug/prefab/modules/jsi/include -isystem /Users/pprnd/.gradle/caches/8.8/transforms/01d6119a8d36e0b6029d3bf994628a51/transformed/react-android-0.75.1-debug/prefab/modules/reactnativejni/include -isystem /Users/pprnd/.gradle/caches/8.8/transforms/01d6119a8d36e0b6029d3bf994628a51/transformed/react-android-0.75.1-debug/prefab/modules/turbomodulejsijni/include -isystem /Users/pprnd/.gradle/caches/8.8/transforms/2f2930249991e77f3723e14ca29648a4/transformed/fbjni-0.6.0/prefab/modules/fbjni/include -g -DANDROID -fdata-sections -ffunction-sections -funwind-tables -fstack-protector-strong -no-canonical-prefixes -D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security  -O2 -std=c++20 -frtti -fexceptions -Wall -fstack-protector-all -fno-limit-debug-info  -fPIC -fvisibility=hidden -pthread -MD -MT CMakeFiles/realm-js-android-binding.dir/Users/pprnd/Documents/yalla_cashier/node_modules/realm/binding/jsi/react_scheduler.cpp.o -MF CMakeFiles/realm-js-android-binding.dir/Users/pprnd/Documents/yalla_cashier/node_modules/realm/binding/jsi/react_scheduler.cpp.o.d -o CMakeFiles/realm-js-android-binding.dir/Users/pprnd/Documents/yalla_cashier/node_modules/realm/binding/jsi/react_scheduler.cpp.o -c /Users/pprnd/Documents/yalla_cashier/node_modules/realm/binding/jsi/react_scheduler.cpp

serhii-yalla avatar Aug 19 '24 14:08 serhii-yalla

It is likely related to https://github.com/realm/realm-js/issues/6850 which we are currently working on

kneth avatar Aug 19 '24 14:08 kneth

Please clear any caches, try v12.13.1 and report back if this issue persists.

kraenhansen avatar Aug 21 '24 12:08 kraenhansen

Thanks @kraenhansen! The new version (12.13.1) fixes the issue! 🙂

avencat avatar Aug 21 '24 16:08 avencat

@avencat note that even though this is a Gradle build failure, the underlying error is different from that of #6845. I'm waiting for @SrinjoyBarman to confirm the new release fix this issue too.

kraenhansen avatar Aug 22 '24 05:08 kraenhansen

Hi, I have the same problem with [email protected].

  • What went wrong: Execution failed for task ':realm:buildCMakeDebug[arm64-v8a][realm-js-android-binding]'.

java.nio.file.FileSystemException: E:\ReactNative\RealmMoviesApp\node_modules\realm\binding\android\build\intermediates\cxx\Debug\4f3s2yy4\obj\arm64-v8a\libreactnativejni.so: The process cannot access the file because it is being used by another process.

I appreciate any help in solving this issue. I am trying to do a Ream Movies app example.

lalithasj avatar Aug 26 '24 20:08 lalithasj

@lalithasj this is a different error from the one @SrinjoyBarman posted above. Please create your own issue with steps outlining how to reliably reproduce it.

kraenhansen avatar Aug 27 '24 05:08 kraenhansen

@kraenhansen thanks for your reply. After restarting everything, it's working.

lalithasj avatar Aug 27 '24 17:08 lalithasj

Closing this as it seems the issue went away. @SrinjoyBarman please reopen if it persists.

kraenhansen avatar Sep 10 '24 10:09 kraenhansen