Search Issue Tracker
Third Party Issue
Third Party Issue in 2022.2.X
Votes
1
Found in
2022.2.15f1
Issue ID
UUM-32849
Regression
No
Gradle build fails with error "Execution failed for task ':unityLibrary:processReleaseManifest'" when building project
Reproduction steps:
1. Open the attached “BugRepro” project
2. Click Edit > Project Settings… > Player > Settings for Android > Publishing Settings
3. Disable Custom Keystore
4. Click File > Build Settings… > Android > Build
Expected result: The project is successfully built
Actual result: Gradle fails with the error “Execution failed for task ':unityLibrary:processReleaseManifest'.”
Reproducible with: 2022.2.0b3, 2022.2.15f1
Couldn’t test with: 2020.3.47f1, 2021.3.22f1 (couldn’t test because of error “Assets/Oculus/Interaction/Editor/AutoWiring/UnityObjectAddedBroadcaster.cs(74,50): error CS0117: ‘SceneManager' does not contain a definition for ‘loadedSceneCount'“), 2022.2.0a1, 2022.2.0b2 (couldn’t fix compiler errors), 2023.1.0b12, 2023.2.0a10 (couldn’t test because build fails with error “Error building player because script class layout is incompatible between the editor and the player.”)
Reproducible on: Windows 10 Pro 22H2, Ubuntu 22.04
Note: Full error: “
FAILURE: Build failed with an exception.
- What went wrong:
Execution failed for task ':unityLibrary:processReleaseManifest'.
> A failure occurred while executing com.android.build.gradle.tasks.ProcessLibraryManifest$ProcessLibWorkAction
> Manifest merger failed : android:exported needs to be explicitly specified for element <activity#com.unity3d.player.UnityPlayerActivity>. Apps targeting Android 12 and higher are required to specify an explicit value for `android:exported` when the corresponding component has an intent filter defined. See https://developer.android.com/guide/topics/manifest/activity-element#exported for details.
“
Comments (2)
-
schmosef
May 11, 2023 01:29
The issue was fixed in the v53 release of the Oculus Integration asset.
-
schmosef
Apr 16, 2023 07:37
The above error is related to building for Android/Meta Quest using v50 of the "Oculus Integration" asset and using the Oculus menu to "add store compatible android manifest".
After adding the android manifest, builds for Android fail with gradle errors.
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Issue is resolved by upgrading to Oculus Integration V53 from the Asset store.
Resolution Note (2022.2.X):
Issue is resolved by upgrading to Oculus Integration V53 from the Asset store.