[INFO][APPLE] Update your editor to receive UIScene lifecycle support

Unity Engine
, , , , , , ,
1

Hello Apple developers,

Apple now requires applications for iOS, iPadOS, tvOS, and visionOS to adopt the UIKit scene-based life cycle. According to Apple: “In the next major release following iOS 26, UIScene lifecycle will be required when building with the latest SDK; otherwise, your app won’t launch”. We expect the next major release to follow the regular WWDC schedule, with a beta release in Summer 2026, and a public release in Autumn 2026.

Over the next weeks we are releasing updates to the Unity Engine Apple Platform to support this change. Update your project to one of these versions or higher to ensure you meet the new requirements.

  • Unity 6.5: 6000.5.0a3+ Released December 16th 2025
  • Unity 6.4: 6000.4.0b8+ Released February 19th 2026
  • Unity 6.3 LTS: 6000.3.8f1+ Released February 11th 2026
  • Unity 6.0 LTS : 6000.0.68f1+ Released February 18th 2026
  • Unity 2022 xLTS: 2022.3.72f1+ Released February 11th 2026

Please update to a supported version at your earliest convenience and perform end-to-end testing on your application. Submit any issues you find through the Unity bug report system. Our development team actively monitors these reports and will address issues promptly.

2022.3 rise in minimum requirement
From 2022.3.72f1, the minimum OS version supported is iOS/iPadOS/tvOS 13. This is due to the UIScene only being available from this version. If you need to still support iOS 12 devices you can remain on an older version.

My project is using an older Unity version and I am unable to upgrade

This update is for currently supported Unity versions only. You can review the changes to the Unity x Apple Glue Layer in Unity 6.0+ and decide if they can manually be applied to your own project using an earlier version. You will also need to manually raise your minimum supported iOS/tvOS/iPadOS version to 13, as UIScene is only available from that version onwards. Please note that any issues reported relating to manual changes or bespoke customisations to the Unity x Apple Glue Layer, will not be addressed.

Files that have changed to support UIScene lifecycle:

Classes/Unity/DisplayManager.mm
Classes/UnityAppController.h
Classes/UnityAppController.mm
Info.plist
Classes/UI/UnityScene.h (new file)
Classes/UI/UnityScene.mm (new file)

The two new files (UnityScene.h & UnityScene.mm) also need to be added to the Xcode project targeting UnityFramework.

Do I have to support this change?

Yes, this is a hard requirement from Apple, the platform holder. We strongly encourage you to update to a compatible version of the editor.

Which Apple Platforms are affected?

  • iOS / iPadOS
  • tvOS
  • visionOS

Known issues
2026-03-06 As of 2022.3.72f1 the minspec is still displayed as iOS 12, please manuallly change to iOS 13 until this is fixed.

5 Likes
[iOS] Future Requirement: Migrating to UIKit Scene-Based Lifecycle (TN3187) - Unity Support Roadmap?
Xcode 26.4 update causing crashes on scene loading
In Case You Missed It: February & March Edition
Screen safe area issues in Unity 2018 LTS
Screen safe area issues in Unity 2018 LTS
2

Thanks! It’s very helpful to see those files for those of us supporting older Unity versions.

Is there any way you could perhaps make a patch file outlining the specific diffs applied in those files, or at least calling out the high points? (eg, “have this delegate, hook it up here, also have this entry in your info.plist,” etc.)

4

Are VisionOS Polyspatial projects also affected by this?

The latest Polyspatial version doesn’t render sprites and doesn’t work with the IAP package. Both issues have been reported for almost two weeks and no update whatsoever. visionOS Release Notes 3.0

1 Like
6

They are focusing on bugfixes!

1 Like
7

Hello,
Glad to see Unity is already on this and all we have to do is to update to new version.

What does it mean for already released applications?
Will they suddenly stop working after said release and therefore we have to update all released games with this updated Unity?

Cheers

8

No, according to Apple documentation, this will only be an issue when building with the new SDK:
In the next major release following iOS 26, UIScene lifecycle will be required when building with the latest SDK;
From: TN3187: Migrating to the UIKit scene-based life cycle | Apple Developer Documentation

2 Likes
9

Hi,

URL scheme data is not received via AppDelegateListener.onOpenURL on iOS when using 6000.3.9f1.

A reproducible project has been submitted as bug report IN-135643.

1 Like
10

Hi, thanks for the report. We are aware of this issue and will address it.

11

Hi,

We reviewed the code in 2022.3.72f1 and found that the old ApplicationDelegate-related code has been removed. Since UIScene is supported only on iOS 13 and later, this suggests that Unity 2022.3 no longer supports iOS 12.

However, the documentation (Unity - Manual: System requirements for Unity 2022.3) still states that Unity 2022.3 supports iOS 12+.

Is Unity planning to support both ApplicationDelegate and UISceneDelegate in 2022.3?

1 Like
12

Hi Alan thank you very much for raising this,

After 2022.3.72f1 only UIScene is supported and it will require a min iOS/iPadOS/tvOS of 13+. This is necessary due to the hard requirement by the platform holder.

We will update our documentations to clarify the 13+ requirement. We will also update the editor to provide the correct min number. In the meantime if you encounter build issues please manually change it from the editor dropdown.

If you still need to make your application available on iOS 12 devices you would need to remain at a 2022.3 version before .72f1.

1 Like
13

I see that the issue with deep links was addressed https://issuetracker.unity3d.com/issues/ios-application-dot-deeplinkactivated-does-not-get-invoked-while-app-is-running-when-uiapplicationscenemanifest-is-added-in-info-dot-plist, but in our case universal links are still not working even after the upgrade. Does anyone have the same issue?

14

Would be great if you could submit a small repro project as bug with your specific use case of deeplinks. Might be that there are multiple entry points/events for deeplinks, and only some got fixed.

15

Configuring Universal Links isn’t quite as straightforward, as the domain must be associated with a valid team + app IDs. Unfortunately, I can’t send our details along with the repro project, but I can provide detailed instructions on how to configure them.

UPD: this is done, waiting for feedback from the Unity team.

16

Hello, is this update also required for native iOS/iPadOS apps using Unity as a Library?

1 Like
17

Interested to know as well if it’s required for UaaL and what are the impact.
We tried as is with a 6000.0.62f1 UaaL build in a native app and it seems to work, but no idea if there is potential side effects.