Search Issue Tracker
Won't Fix
Won't Fix in 2022.3.X
Votes
0
Found in
2022.3.1f1
Issue ID
UUM-760
Regression
No
[iOS] The view is not stable when using WebCamTexture in iOS 15
How to reproduce:
1. Open the project
2. Go to the Build Settings (File>Build Settings)
3. Select iOS and build
4. Open Xcode project and build for a device
5. Rotate the device a few times and look at the screen
Expected result: The view is stable
Actual result: The view is not stable
Reproducible with: 2019.4.32f1, 2020.3.21f1, 2021.1.28f1, 2021.2.1f1, 2023.2.0a18
Could not test with: 2022.1.0a13 (In the Build the Scene was empty)
Reproduced with:
VLNQA00392 - iPad (9th generation), 15.0 iOS
VLNQA00494 - iPhone 14 Pro Max, 16.3.1 iOS
Not reproduced with:
VLNQA00358 - iPhone 12, 14.1 iOS
VLNQA00310 - iPad Pro 12.9", 13.4.1 iOS
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
- Silent crash when importing SVG files
- Animator state transition preview clips are flickering when zooming in
- [Tile Palette] Sprites not rendering when brush tool "Paint a filled box with active brush" is used for the first time
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
- "DebugAllocatorMode" option changes when changed in another Editor instance
Resolution Note:
In our tests, the issue can be resolved by stopping the webcam texture and starting it again (WebCamTexture.Stop, then WebCamTexture.Play). We recommend detecting orientation changes, and stopping the texture for, e.g., one frame.
We may re-visit this issue in the future. However, as there is a simple workaround available, we will resolve the ticket for the time being.
Resolution Note (2022.3.X):
In our tests, the issue can be resolved by stopping the webcam texture and starting it again (WebCamTexture.Stop, then WebCamTexture.Play). We recommend detecting orientation changes, and stopping the texture for, e.g., one frame.
We may re-visit this issue in the future. However, as there is a simple workaround available, we will resolve the ticket for the time being.