■Environment
Device: NTT QONOQ, MiRZA
Spaces AR SDK 1.0.1
Dual Render Fusion
Thank you for reporting this issue. It has been logged with the SDK team for further investigation.
Hi,
Thank you for your response.
How is the progress of this investigation?
The Jira ticket has been opened and is currently under engineering review. I have requested an update on the progress and am awaiting a response.
Based on the engineering analysis, it appears that the application is not requesting camera permissions. For further information, please refer to the following documentation:
If you are using DRF you need to do the camera checking:
https://docs.spaces.qualcomm.com/unity/setup/handling-app-permissions-fusion#permissions-for-the-openxr-runtime
Thank you for you response.
After granted camera permission, we keep getting error log as shown in figure when using Spaces SDK v1.0.1 and attached AR Camera Manager.
Cloud you please tell me how to resolve this error?
Thank you for your feedback. I have passed your notes to the engineering team and am awaiting their response.
You can fix this issue by attaching a script, get the cpu image and call image.Dispose() to release the frame.
You can find example code here:
https://docs.spaces.qualcomm.com/unity/features/camera-frame-access-feature
You can fix this issue by adding a script. In the script, get the cpu image from AR camera manager and use image.Dispose() to release the frame. Yo can see the code examples in here:
https://docs.spaces.qualcomm.com/unity/features/camera-frame-access-feature
We got feedback from engineering:
Could you please assist us by performing the following steps?
1) Force stop the app being used
2) Force stop MiRZA home app
3) Force stop Spaces Services (or the Sharp Spaces Services apk)
4) Open Settings -> Applications -> "Spaces Services" (sharp or ours) -> Permissions and send us a screenshot of this (photo from another phone is fine or screenshot from device)
5) Open Settings -> Applications -> "App that has issue" -> Permission and send us a screenshot of this
6) Issue in a cmd prompt `adb logcat -c`
7) Issue in a cmd prompt `adb logcat > camera_permission_issue.txt`
8) Start MiRZA home app and begin "Spaces Mode"
9) Start "app that has issue" and use it to generate the reported error
10) stop the adb logcat (ctrl-c in the cmd prompt)
Please send us the entire "camera_permission_issue.txt" log file along with the two images.
Afedorch-san,
Thank you for your reply.
I would send you screenshots and log file, but due to security issues I cannot post them here.
It there any way to send these files to you in a closed?
Send them to my email [email protected]
Ayano. komura. nt
Hi,
I keep getting error logs when the AR Camera manager is exist in a Unity Scene, due to this issue in Spaces SDK v1.0.1.
I understand that Spaces SDK v1.0.1 expects the AR Camera Manager to be disabled, but it is an essential component of Immersal or Marker contents.
Could you remove this log from Spaces SDK?
I have checked to error logs situations as a following,
・Using the Spaces SDK v1.0.1 sample (ControllerPrefabSampleScene), attach AR Camera Manager to Main Camera
・AR Camera Manager is enabled
・The above error occurs
・AR Camera Manager is disabled
・No error occurs
・Using the Spaces SDK v0.23.0 sample (ControllerPrefabSampleScene), attach AR Camera Manager to the Main Camera
・AR Camera Manager is enabled
・No error occurs
・AR Camera Manager is disabled
・No error occurs
Thank you!