Hi you seem to be running into a bug that we have already tracked internally. We are working on a fix in a future release of Snapdragon Spaces. 

The timing of requesting permissions and starting up the Camera Frame Access feature in OpenXR are important here. The permission needs to be given first, before the OpenXR feature starts up. 

If you want to implement a workaround:

1. Disable the following components
   1. ARCameraManager
   2. SpacesCameraPoseProvider
   3. SpacesARCameraManagerConfig
2. Create a script requesting permissions (Camera) at runtime. You may also use the CameraFrameAccessSampleManager. Here are the Unity docs on that  Unity - Scripting API: Android.Permission.RequestUserPermission (unity3d.com)
3. Register a callback to that permission request.
4.  In that callback enable the previously disabled components.

Please let us know if that works. 

Hi Shiota, 

We have a fix for this issue confirmed for the next release of Snapdragon Spaces with 0.25.0. The estimated release of this version will be end of June ~2 weeks. Please note that there can be delays if required to assure our quality standards. 

Generally giving permissions before starting the Unity player sounds like a viable solution since everything would intitialize after permissions are already given. I'm going to clarify that with our engineering team and come back to you. 

If you want to give permissions before creating the Unity Player, you need to make sure to give permissions for the Snapdragon Spaces services and the Application at that point. In theory it is a viable workaround but you will need to implement the checks that would usually be done by our Unity Plugin yourself.