Bug / Crash Obi Rope build error with Unity 2023.1 on APK Build for XR

[josemendez]

Hi,

We are successfully using OBI Rope with Unity 2022.3 LTS or our OpenXR Unity Project for Meta Quest 2. We upgraded to Unity 2023.1 and we couldn't generate the APK due to gradle build error. We tried everything and slowly started isolating our plugins one by one till we were able to produce the error only with OBI Rope Asset. It works well with 2022 Unity but if OBI Robe is present in the project, it does not generate the APK build for Quest 2.

We are using Unity builtin XR Plugin Management with OpenXR plugin.

Code:

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':unityLibrary:mergeReleaseNativeLibs'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.MergeNativeLibsTask$MergeNativeLibsTaskWorkAction
   > 2 files found with path 'lib/arm64-v8a/libc++_shared.so' from inputs:
      - /Users/username/23TestXR/Library/Bee/Android/Prj/IL2CPP/Gradle/unityLibrary/build/intermediates/merged_jni_libs/release/out/arm64-v8a/libc++_shared.so
      - /Users/username/23TestXR/Library/Bee/Android/Prj/IL2CPP/Gradle/unityLibrary/build/intermediates/cxx/RelWithDebInfo/3p2l6l3t/obj/arm64-v8a/libc++_shared.so
     If you are using jniLibs and CMake IMPORTED targets, see
     https://developer.android.com/r/tools/jniLibs-vs-imported-targets

We are investigating more and will share if we can isolate the problem but I have created a sample project that contains only OBI Rope plugin and an empty scene. In order to reproduce just Open the project in 2023.1 Unity and switch build platform to Android and try to Build the APK. We tested this on mac and its not generating the build. If we remove OBI Rope asset then it builds successfully.

https://drive.google.com/file/d/1er0W8T6...sp=sharing

Hi,

If you're using the Burst backend (which is the recommended approach, since the native-library based Oni has been deprecated for some time now), there's no need to use libc++_shared.so. You can simply remove the library / exclude it from the build.

kind regards,