Search Issue Tracker
Third Party Issue
Votes
5
Found in [Package]
1.8.2
Issue ID
OXRB-222
Regression
No
[OpenXR] Build fails due to AndroidManifest merge conflict with OpenXR
Steps to reproduce:
1. Open the attached user's project "UOPENXR.zip"
2. Make sure OpenXR is selected in the XR Plugin management
3. Build for Android
4. Observe the build error
Expected results: Build does not fail due to AndroidManifest merge conflict with OpenXR
Actual results: Build fails due to AndroidManifest merge conflict with OpenXR
Reproducible in: OpenXR 1.8.2 (2021.3.29f1, 2022.3.6f1, 2023.1.7f1, 2023.2.0b3)
Environment tested on: Windows 10
Notes:
-Issue only reproduces when OpenXR is selected as the Plugin
-Issue only reproduces when Oculus SDK is integrated into the project
-Issue does not reproduce on a new project when integrating Oculus SDK and Enabling OpenXR
-Error message:
Execution failed for task ':launcher:processReleaseManifest'.
> Manifest merger failed : Attribute meta-data#com.oculus.supportedDevices@value value=(quest|quest2) from [:unityLibrary] AndroidManifest.xml:94:13-41
is also present at [:unityLibrary:xrmanifest.androidlib] AndroidManifest.xml:21:13-49 value=(quest|quest2|cambria).
Suggestion: add 'tools:replace="android:value"' to <meta-data> element at AndroidManifest.xml:92:9-94:44 to override
Comments (1)
-
ceitel
Jan 26, 2024 19:34
Any workarounds for this?
Can't seem to get it to build and upon attempting to add the suggested replacement metadata to \Assets\Plugins\Android\AndroidManifest.xml I've found that it is already included as the following line:
<meta-data android:name="com.oculus.supportedDevices" android:value="quest2|questpro" replace="android:value" />
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on various stack traces when using Texture2D.CreateExternalTexture() while rendering
- Clicking on section text in Node Library > Context folder throws NullReferenceException errors
- Node Library window sections text in Context folder are not visible when Editor is set to Light Theme
- "Scene Depth Difference" Node has an input Port which is called Position WS, directly referring to the World Space Position, when only the View Space Position can reflect if the object's depth is below or above the Plane
- Missing documentation page for Visual Effects Defaults
Resolution Note:
This issue stems from the meta Core SDK Packages, which are published by meta, so we will be rejecting this issue. This specific conflict is fixed with recent versions of the Meta Core SDK. Please update your project.