Many of our games have inexplicable errors in iOS 15.4 beta after exporting and causing the game to terminate. It does not exist in iOS 15.3. Is the new system triggering a bug in the Unity WebGL project?
This problem also occurs in Unity’s demo in AssetStore:Dragon Crashers - URP 2D Sample Project | Tutorial Projects | Unity Asset Store
Compiled from Unity2021.2.11f, ran on iPhone13 promax(iOS 15.4)
Maybe it has nothing to do with the Unity version, because we have a project using Unity2019 also encountered. IL2CPP+WASM will encounter some problems with 15.4 safari?
We’re getting the exact same problem when running our games on mobile safari, on the iOS 15.4 beta. Works fine on iOS 15.3.
No point in sharing our logs, since we’re getting the exact same as @OceanX000 posted.
The problem seems to appear when we add any kind of UI to a scene (regardless of if it’s using OnGUI or a Canvas object).
We’ve put together a clean sample project that triggers this crash (just the default scene with a UI image added to it, no change to the build options) - GitHub - davidmmgo/UnityWebGLTest: Small test project to validate canvas behavior on iOS15.4 beta
Hi there, having those same errors on iPhone SE running iOS 15.4 beta (19E5235a) while trying to load on Safari the simplest project @davidg describes above.
This is an iOS issue outside of our control, appearing to be related to WebKit loading/executing WASM. It’s currently marked as a P1/Major issue. I certainly hope Apple will resolve it before releasing 15.4.
This issue has not been resolved with the release of iOS 15.4.
The issue is not registered in Unity IssueTracker, is Unity Technologies aware of the situation and can they proceed to address it?
If you need more information, we can help.
Thank you.
We also ran into this showstopper bug on iOS15.4. @brendanduncan_u3d do you have any updates on the bug that’s on Apple’s side now? Did they have an ETA on when that’s going to make it into a patch? In the meantime, did anyone find any workarounds for this bug?
@M-SugayaTakuma
We are very aware of this problem and are working as hard as we can on trying to find a solution. We do not have an ETA. The problem is coming from memory corruption from the WASM VM on iOS 15.4. We have a ticket filed with Apple, have been pushing them as much as we can, and are working on trying to find a solution and/or workaround on our side if at all possible.
@brendanduncan_u3d
I appreciate that you are doing everything in your power to investigate a solution.
However, it seems that Apple will need to resolve the underlying issue, is there any action we can take to get Apple to respond?
I am frustrated that Apple has not responded in any way.
I am seeing some promising results from investigating if there’s anything Unity can do to get around the WASM issue. I have found a file that I can swap out during the compilation process, and at least initial tests have eliminated the crash. So there is at least hope of a solution, even without Apple getting their stuff together.
That said, there are other issues with iOS 15.4 WebKit besides the WASM crash. There were several serious WebGL graphics regressions, which have been affecting the other WebGL engines too.
So, we are all in a generally bad point in time for Web on Apple, but I know a number of the WebGL graphics issues have already been patched in Apple’s WebGL implementation, and there’s hope for the WASM issue, so hopefully this point point in time will be short.