Unintended Manifest Modifications by XRSessionFeatureBuildHooks for Non-AndroidXR OpenXR Platforms in Unity

Hi Google Team,
we have noticed an issue with the XRSessionFeatureBuildHooks Class in Unity Projects that use the OpenXR plugin across multiple plattforms.

When the AndroidXR Package is present in the project, the class injects additional configurations in the manifest files on build time, regardless of whether the current build target is AndroidXR or another OpenXR Plattform.

Currently the compiler flag UNITY_OPEN_XR_ANDROID_XR is defined as soon as the AndroidXR package is included in the project, rather than being conditional on the actual build profile. As a result, AndroidXRBuildUtils.IsUnityAndroidXRActive() always returns true, leading to unwanted manifest modifications for non AndroidXR builds.

Please adjust the detection logic in ProvideManifestRequirement() and AndroidXRBuildUtils.IsUnityAndroidXRActive(), so that they only modify the manifest and return true respectively when the active build target is AndroidXR.

Thanks

Best regards
David Schrott
SAP SE

Start by locating XRSessionFeatureBuildHooks.ProvideManifestRequirement() and AndroidXRBuildUtils.IsUnityAndroidXRActive(), then inspect how the active Unity build target or profile is detected. Done means non-AndroidXR OpenXR builds leave manifests unchanged while AndroidXR builds still receive the required modifications.

Written by the indexing model from the issue text.