Search Issue Tracker
Fixed in 2018.2.X
Votes
4
Found in
2017.2.0p1
2017.2.0b2
Issue ID
969730
Regression
Yes
[iOS][Metal] iOS application crashes at start when camera's clearing is set to Depth only
There are 2 different crashes depending on quality settings. If MSAA is enabled, app crashes at: BlitFramebufferAtSliceAndLevel() at BlitFramebufferMetal.mm:134 [opt]
If MSAA is disabled app crashes at: CreateNewEncoder() at MetalContext.mm:112 [opt]
This is related to specific camera settings. Changing Clear Flags or disabling HDR solve the issue.
Also, this is not reproducible with OpenGLES3 API
To reproduce:
1. Open attached project
2. Build and run on iOS device
Expected result: Application successfully launches without any issues
Actual result: Application crashes
Reproduced with: Unity 2017.2.0b2, 2017.3.0b9, 2018.1.0a4
Not reproducible with: 5.6.4p3, 2017.2.0b1
Devices: iPhone 5s iOS 9.3, iPhone 8 Plus iOS 11.0.1
Fixed in: 2018.3.0a1
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
hammadb
Aug 04, 2018 02:04
Is this actually fixed? I'm seeing this error in 2018.2 still