Failure to Launch on iOS 27

Solar2D iOS
1

Currenly my app and any other solar2d app using the latest build will fail to launch on iOS 27

From what I gather from searching is that Apple has made the UIKit scene-based lifecycle mandatory for apps built with the iOS 27 SDK. Apps still using only the old UIApplicationDelegate lifecycle now fail at launch

[Device] UITraceInitialize: registering notify listener
Sep 24 15:04:54.100 [Device] handle_trace_notification: received notify (state=0)
Sep 24 15:04:54.121 [Device] alm_acquire_pageins_recording_assertion: acquired pageins recording assertion!
Sep 24 15:04:54.122 [Device] Will add backgroundTask with taskName: <private>, expirationHandler: <__NSGlobalBlock__: 0x1faa9a738>
Sep 24 15:04:54.122 [Device] Reusing background assertion <BKSProcessAssertion: 0x103501f60>
Sep 24 15:04:54.124 [Device] UserDefaults(com.apple.gms.availability, 501
Sep 24 15:04:54.125 [Device] registering darwin observer for name: com.apple.gms.availability.notification
[Device] registering darwin observer for name: com.apple.os-eligibility-domain.change.greymatter
[Device] registering darwin observer for name: com.apple.language.changed
[Device] will update observations for 0 observers
Sep 24 15:04:54.125 [Device] will update observations for 0 observers
Sep 24 15:04:54.126 [Device] Event deferring policy changed: finalScene:N->Y (token: com.apple.frontboard.systemappservices/FBSceneManager:sceneID%3Acom.rebelbinary.onlyone-default)
[Device] Scene gained keyboard focus (scene: <UIWindowScene: 0x107dc8280>, responder: (nil), wantsKB: N)
[Device] -[_UIRemoteKeyboards prepareToMoveKeyboard:withIAV:isIAVRelevant:showing:notifyRemote:forScene:] position: {{0, 0}, {0, 0}} visible: 0; notifyRemote: 1; isMinimized: NO
[Device] Requesting keyboard scene for (FBSceneManager):sceneID:com.rebelbinary.onlyone-default
Sep 24 15:04:54.126 [Device] failure in void _UIApplicationEvaluateRuntimeIssueForNoSceneLifecycleAdoption(void)_block_invoke (UIApplication_RuntimeIssues.m:106) : Application failed to launch: UIScene life cycle is required for apps built with this SDK. See "Transitioning to the UIKit scene-based life cycle" in the UIKit documentation for more information on migration.

2

Iā€™ve been using the iOS 27 beta for months now and have built/released a few updates over the past months (latest one was today). I get the popup when I try to build about the iOS mismatch but it still works.

Which version of Xcode are you using?

Side note: How can we get iPhone Duo support so it doesnā€™t run letterboxed when a user opens their device.

3

Yah Itā€™s probabaly that Iā€™m building with the latest version of xcode 27. Apps open fine on ios 27 devices with a basic project, but the moment I add any plugin and make a build with it, it falls apart and I get that error. Going to revert back to xcode 26 to get the project working again. Xcode mismatches had been running ok in the past.

4

This is being looked at, will have update on duo support soon

1 Like
5

Glad I didnā€™t update to Xcode 27 then. Iā€™ll stick with 26 until thereā€™s a proper update for it.

@Scott_Harrison Looking forward to hearing more about duo support!

6

I accidentally built a version with xcode 27, that build runs just fine on my ios26 device and then submitted for review. Fortunately the reviewer was running an ios27 device and it crashed during launch and submission rejected. I then downgrade xcode to 26.6 and then built and resubmitted all good.

7

There is also the issue with the Transporter App, I get an error even on xcode 26

Invalid Swift Support. The SwiftSupport folder is empty. Rebuild your app using the current public (GM) version of Xcode and resubmit it. (90424)

My workaround is to open the ipa (as. a zip) and compress the payload and use that as the ipa thus removing the empty swift folder

8

Yeah, I have to do this same workaround too with Xcode 26.

9

If anyone wants to early access to a beta build, you can download it here

Contains Fixes to Support iOS 27 and Xcode 27

Edit: you do need be signed into GitHub to be able to download

10

The link is not available, can you please check.

11

Itā€™s direct download link and triggered the download, but been blocked by Browser when download finished.

12

Same for me. Chrome says it is a dangerous download and gives me no option to override that.

Out of interest Scott, does that build have anything iPhone Duo specific in it? (Iā€™m just curious)

13

Oh thatā€™s weird, I mostly use safari

that build does not contain iPhone Duo, I will have something cool that I am working on, will post on Friday

1 Like
14

Hi,

knowing that I made everything with github action, how can I remove the ā€œSwiftSupportā€ file from the ipa ?

I also have the same problem, but I donā€™t want how to make this workaround with github action inside the ā€œdeliver.shā€ file.

Thank you.

15

Removing the SwiftSupport on the fly during the github process also worked.

I add this line in the deliver.sh file to zip the ipa, remove the empty folder inside and switch extension again in an ipa.

mv Util/*.ipa "Util/final.zip";zip -d "Util/final.zip" SwiftSupport/*;mv Util/final.zip "Util/myapp.ipa"

image
image917Ɨ137 3.56 KB

Sincerely.

16

Here is fold support update btw

1 Like
17

Any idea when all these fold changes will make it into a released build?