Synopsis

Switching to the Meta Quest platform under Build Profiles generates the following OpenXR warnings and fails to enable relevant OpenXR Interaction Profiles. A workaround is to create a custom Build Profile based on Meta Quest, then switch to this Build Profile.  But switching to the Meta Quest platform should work robustly; otherwise the Switch Platform button should be grayed out, or its limitations should be spelled out clearly in the Users' Manual. 

{{Oculus Touch interaction profile could not be enabled in OpenXR settings.}}
{{UnityEditor.EditorAssemblies:ProcessInitializeOnLoadMethodAttributes () (at /Users/bokken/build/output/unity/unity/Editor/Mono/EditorAssemblies.cs:153)}}

{{Meta Quest Pro interaction profile could not be enabled in OpenXR settings.}}
{{UnityEditor.EditorAssemblies:ProcessInitializeOnLoadMethodAttributes () (at /Users/bokken/build/output/unity/unity/Editor/Mono/EditorAssemblies.cs:153)}}

{{Meta Quest Plus interaction profile could not be enabled in OpenXR settings.}}
{{UnityEditor.EditorAssemblies:ProcessInitializeOnLoadMethodAttributes () (at /Users/bokken/build/output/unity/unity/Editor/Mono/EditorAssemblies.cs:153)}}

Steps to reproduce:

1. Use Unity 6000.3 to crate a new project using URP Template (or open repro project attached). 
2. File > Build Profiles > Meta Quest > Switch Profile
3. Check Console window for warnings. 
4. Check Edit > Project Settings > XR Plug-in Management > OpenXR Enabled Interaction Profiles.

Actual results: 

Console warnings listed above in Synopsis appear in Console window. 

There are no enabled interaction profiles in OpenXR Project Settings.

Expected results: 

No warnings in Console; three relevant interaction profiles enabled.

Reproducible with versions: 

Unity 6000.3.6f1 + OpenXR 1.16.1.

Also occurred in Unity 6.2, so not flagging as regression.

Not reproducible with versions: 

Can’t test with versions: 

Tested on (OS): 

Warnings occurred on MacBook Pro when setting Build Profile to Meta Quest.