Search Issue Tracker
Third Party Issue
Votes
0
Found in [Package]
2019.4
2020.1.11f1
2020.2
2021.1
2021.2
Issue ID
1306532
Regression
No
[iOS] Status reports as "Tracking" after denying camera access
Reproduction steps:
1. Download and open the attached "ARF 4.1 Camera Auth Tracking State Bug.zip" project
2. Build and deploy the project to iOS
3. Press "Don't allow" when a camera permission notification appears
4. Observe the Xcode console window
Expected result: Console doesn't report camera status as "Tracking"
Actual result: Console shows a message reporting camera status as "Tracking"
Reproducible with: 2019.4.21f1, 2020.2.6f1, 2021.1.0b8, 2021.2.0a6
Could not test with: 2018.4 (Console errors when downgrading)
Note: Screenshot of the issue attached below
Note: Issue does not reproduce consistently (6/10 times), if unable to reproduce, delete the application from your device and repeat all steps from step 2
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
- Rendering locks up when not looking at a transparent material on Meta Quest 2
- Volumetrics break when using a Custom Pass to create a Thickness Buffer for Alpha Clipping
- All tests are run instead of only the failed ones when the "Rerun Failed" button is pressed
- GameObject is not masked when the "Render PostProcessing Effects" pass executes with a resolved non-MSAA Color target and MSAA DepthStencil target
- [Android] Gfx.WaitForGfxCommandsFromMainThread high performance usage and inconsistency when built Player scene has Canvas GameObject on a specific Project
Resolution Note:
The tracking data printed is based directly on data surfaced to us by ARKit and, as a result, is a third party issue. Here is a link in case if you would like to report this bug directly to Apple: https://developer.apple.com/bug-reporting/