Crash issue when building to iOS devices with Unity 2019.4.3f1 and Xcode 26.4

I am currently using Unity 2019.4.3f1 for our project. Due to Apple’s new policy, we need to use Xcode 26 or later to build projects after April 28, 2026. Therefore, I created a test build project in Unity 2019.4.3f1, which contains some basic UI components such as Buttons, Texts, and Images, along with simple Button event handlers.

I exported the iOS project and built it with Xcode 26.4 (I upgraded to the latest version since I just performed the update recently). The build succeeds, but when running on an iOS device, an error occurs that directly crashes the process (app terminates unexpectedly). Below are the error location, log information, and the Xcode version:

Error log:(enabled “Development Build” in Unity’s build settings)
ErrorLog.txt (15.0 KB)

Error location:

Xcode version: 26.4

I exported the relevant resources and code from the test build project in Unity 2019.4.3f1 as a UnityPackage, then imported that package into a new Unity project created with Unity 2022.3.62f1. After building with Xcode 26.4, it runs normally.

In Unity 2019.4.3f1, I have tried various methods but cannot get it to run properly. With Unity 2022.3.62f1, it runs without any modifications. So for Unity 2019.4.3f1, aside from upgrading to Unity 2022 or later, is there any other way to build successfully with Xcode 26 and have it run normally? Or is upgrading the Unity version the only solution?

Has anyone encountered a similar issue? Any suggestions would be greatly appreciated. Thank you.

Unity 2019.4 is not supported. The best thing you can do is to update to the latest patch of the 2019.4.x line.

Thank you for your suggestion. However, I have tried Unity 2019.4.4f1 and still have the same issue.

No. The latest versions can be found on the Archives page: 2019.4.41f2 issued at Oct 15, 2025.

I apologize for the late reply. I’ve been busy with other things recently.

Thank you for your suggestions. However, we have already upgraded to Unity 2022.3.62f2, which resolved the compatibility issue.

Thank you again for your answers and advice
:slight_smile: