Im getting a crash in some Unity code I don’t have access to. Im running an iOS build from 5.5 on my iPhone 7 plus ( metal enabled ). Anyone know what line this might be or workaround fix?
The line is: GfxDeviceMetal::InvalidateState() (GfxDeviceMetal.mm:1341)
2879714–211338–crash.log.txt (65.7 KB)
We are having the same problem. Our app crash before splash screen at random. 2 of 3 starts works great. Seems to crash at InvalidateState(). We use Xcode 8 and Unity 5.5.0p1. Tested on iPhone 7 and iPhone6+. Would be very thankful for a fix!
Same here.
Have you found any solution to that?
Have you tried 5.5 patch1, seems there some fixes
Same in patch 1 
Just made a new build, with metal removed from my graphics API in build settings. App still crashes in the same way as before
Please file bug report so they can fix for patch 2-3 as priority…
Bug report filed.
“We have identified this issue as a duplicate of an existing known bug and we will be closing the issue. The information you have supplied will help us further in the resolution. The ticket link is broken now, but I can assure you that the fix is coming.”
Same issue in 5.5 P1, crash on start up with the same stack. Does anyone have a workaround in place? I doubt we could ship an iOS game in this state.
Anyone have the link to the bug report?
This is serious issue, I hope its resolved in Patch2
Agreed, I’ve just spent the last 18 hours reverting to our last git commit on 5.4.2 and redoing the last 3 days work again 
On reflection it was my own fault for allowing our project to be upgraded to 5.5 at such a late stage of development (I know better). The splash screen was just too much temptation. Lesson learned (again 
) we’ll be waiting for 5.5.1 now.
I feel your pain, I wait weeks for a fix to release on mobile (Windows Mobile random crash)
Then a new issue created on a different mobile platforms.
Thing is each beta 5.5 and 5.4 they always seem to be testing engine as standalone, and poor testing of specific mobile platforms, hence always mobile platform issues. I dont know what Unity want more. Keep asking for bug reports its end 2016 and there testing is still not up to scratch. Its easy to find bugs and log em, but regression testing seems to be failing… Anyway dont want to complain, just wish for dedicated mobile QA for specific platforms to run some regression on live projects…
We have the same issue as well with P1. 5.5 seems pretty unstable.
Actually - once I removed the metal support completely from the player settings, the Metal crashes stopped for me.
This is of course - just a workaround.
Ah yes, disabling Metal does is a workaround despite others on the thread being unsuccessful. Works for us.
We’re looking forward for the actual fix and re-enabling Metal again.
I’m getting the same issue.
It happens when I’m changing some graphics settings forcing some settings/shaders to be recompiled. Sometime it disappears once I launch the build a second time.
When it happens, this is how I fix it:
If it happens after a new xcode projet has been generated, I launch the build a second or third times and it stop happening.
If it happens after I update the xcode project using append, I rebuild the project using replace and it stop happening after I launch the build 1-2 times.
This make developping on iOS a bit tedious
Does anyone have a bug report id for this?
We had exactly the same problem…The solution that worked for us was to build using OpenGLES2 as the default GraphicsAPI. This is definitely a serious bug and Unity should fix it as soon as possible…
Also having this issue, and like many others, starting a second time seems to get around the crash. Unfortunately we rely on Metal, so GLES isn’t a solution for us.
The exact line from the crash reporter is GfxDeviceMetal::InvalidateState() (GfxDeviceMetal.mm:1341)