Search Issue Tracker
Won't Fix
Votes
1
Found in
5.3.5p7
Issue ID
813569
Regression
Yes
[iOS] App crashes in PresentGLES(UnityDisplaySurfaceGLES *) on devices without Metal support
Steps to reproduce:
1) Download and open the attached project.
2) Build and deploy a Debug build to an iOS device without Metal support (iPhone 5, for example).
3) Start the game.
4) When the first level loads, exit to Main Menu through an icon on the top-left.
5) Hold 4 fingers on the screen simultaneously until a menu appears.
6) Select 'Unlock everything'.
7) Swipe until you see level 30 and select it.
8) Navigate the player character to the robot directly above it and click on it.
The player character gets shot by a turret. At this point the game crashes with around 40% chance in PresentGLES(UnityDisplaySurfaceGLES *) if it doesn't crash, navigate to the same robot again after the level restarts. Reproduces with both GLES2 & GLES3.
Reproduced on:
5.3.5p8 - iPhone 5, 9.2 (did not reproduce on the rest of the tested devices)
5.3.5p7 - iPhone 5, 9.2; iPhone 6+, 8.0; iPad Pro 9.7", 9.3.
Did not reproduce:
5.3.5p3
Comments (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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
KJoanette
Apr 18, 2017 10:53
Why is this a "will not fix"? This breaks a lot of devices.
KJoanette
Nov 16, 2016 14:25
We are having this issue as well and it's causing us a lot of problems on these devices. We need this fixed ASAP.
Still occurs in 5.4.2p4