iOS 26 SDK

[kiyokiyo123]

I have gotten next message from Apple.
“Starting April 28, 2026, all iOS and iPad apps must be built with the iOS 26 SDK
or later, included in Xcode 26 or later.”

When can I get the new AIR sdk?

[MurrayHamilton]

I had this issue yesterday, but I downloaded the latest SDK via the manager and it fixed it. I can’t remember the exact version number though and I can’t check at the moment, sorry (I’m posting from my phone).

The release notes didn’t mention that it’s built with the iOS 26 SDK but neither Transporter nor App Store Connect complained, so I guess it must be!

[ajwfrost]

https://airsdk.harman.com/release_notes?q=51.3.2.1

The AIR SDK itself isn't actually built using iOS 26 SDK, but it doesn't need to be.. the applications that you build with it are what needs to be, which is what's been updated in here hence the applications should be acceptable to the App Store now.

[MurrayHamilton]

Ah right, thanks for explaining - always good to learn something!

[Michoko92]

Hi,

I just submitted an IPA built with the latest SDK (51.3.2.1) on Windows 11, and I got this issue from the review process:

ITMS-90725: SDK version issue - This app was built with the iOS 18.5 SDK. Starting April 28, 2026, all iOS and iPadOS apps must be built with the iOS 26 SDK or later, included in Xcode 26 or later, in order to be uploaded to App Store Connect or submitted for distribution.

Could it be due to an ANE that is compiled with an older version? Is there a way to check my IPA before submitting it, and be sure it shows the correct iOS SDK version?

Thank you!

[ajwfrost]

Hi - that's unexpected, would it be possible for us to get the IPA file so that we can examine the details on a mac to see what's going on inside it?

Upload link: https://transfer.harman.com/requests/Mx0Jn1DjqrlaChoNNLjzgm

thanks

[Michoko92]

Sure, just sent it to you. Thank you for having a look!

[ajwfrost]

Well your Info.plist file looks correct - at least, it has all the same values in it as we get when compiling an app natively on macOS.

However, I can see this in your load commands:

Load command 11
      cmd LC_BUILD_VERSION
  cmdsize 32
 platform 2
    minos 12.0
      sdk 18.5
   ntools 1
     tool 4
  version 17.0.1

vs our build:

Load command 9
      cmd LC_BUILD_VERSION
  cmdsize 32
 platform 2
    minos 12.0
      sdk 26.2
   ntools 1
     tool 3
  version 1230.1

Can you check your "ld64 command line" from the ADT log (or by running the ADT packager whilst viewing the AIR SDK Manager 'troubleshooting' page)? It should have -platform_version ios 12.0 26.2 near the end of it..

When I check on a Windows machine here, the version code above is used, and the resulting binary has the load command:

Load command 10
      cmd LC_BUILD_VERSION
  cmdsize 32
 platform 2
    minos 12.0
      sdk 26.2
   ntools 1
     tool 4
  version 17.0.1

The only way I can see it getting an earlier iOS SDK version is if you're using a platformsdk argument that includes 18.5 within the path name...

thanks

[Michoko92]

Thank you, Andrew. You were right about the platformsdk argument. I didn't use it explicitly while packaging, but your remark rang a bell. I reviewed all the adt.cfg files on my system and found one with an uncommented "iOSPlatformSDK=" line. As soon as I commented it out, everything worked as expected.

Sorry for the false alarm, and thank you so much for your awesome support! 🙏

[ajwfrost]

Good to hear! thanks

[Gokul617]

Hi

I am currently working with Adobe AIR and facing an issue after upgrading from AIR 51.2.2.3 to AIR 51.3.2.1

In AIR 51.2.2.3, my iOS app builds and runs successfully. However, after upgrading to AIR 51.3.2.1, the app crashes on launch.

Upon checking the ADT logs, I found the following:

AIR is unable to detect the iOS SDK version
It defaults to an incorrect value:
-platform_version ios 12.0 26.2

Log messages:
"Could not call --show-sdk-version for iphoneos, setting to default 26.2"

This seems to be causing the crash during app launch.

Environment details:

OS: Windows
AIR Version: 51.3.2.1
Working Version: 51.2.2.3
Build Type: ipa-test (local packaging)
Using multiple ANEs (AdMob, ironSource, Firebase)

Additionally, I am seeing warnings like:
"Using default implementation for native extension (androidx, playservices, etc.)"
(Assuming these are Android-specific and not related to the crash.)

Could you please confirm:

Is this a known issue in AIR 51.3.x?
Is Mac/Xcode remote build now mandatory for correct iOS SDK detection?
Is there any workaround to fix the incorrect platform_version (26.2)?

Kindly suggest the correct approach to resolve this issue.
Please find the attached ADT logs.

Thank you for your support.
adtlog.txt

[ajwfrost]

Hi

The reason it can't detect the version is because that is only possible on macOS, but the idea of falling back to defaults means it will use values that should be correct/acceptable - and in this case -platform_version ios 12.0 26.2 is what you should be getting for an iPhone application.

Default implementations for ANEs would happen if there's no iphone-specific platform support, and looking at the list, yes I think you're right in assuming this is fine for those Android-specific ones.

The most likely reason for the crash I suspect is if you have an ANE that depends on a symbol that has moved between libraries .. if you're linking with the stubs (which I assume, as I don't see a -platformsdk argument) then this is a limitation of that mechanism..

But to find out for sure, it would be good to get the analytics off the phone, are you able to send us the IPS file from the privacy/analytics settings? See https://airsdk.harman.com/support#ipa_symbols and search for "IPS" - even better if you're able to set it up for outputting the symbol data file and then rebuild/package/deploy/crash it again..

thanks

[itlancer]

@ajwfrost
I have the same crash issue using AIR 51.3.2.1 and 51.3.2.2. I have AIR application for iOS which built by Windows machine. Everything worked fine before updating AIR 51.3.2.x.
Our application have 2 our own native extensions which worked fine for many years. And seems that one of them still works fine but with another, on first ExtensionContext.createExtensionContext() or ExtensionContext::call() we get immidiate crash without any usefull info in Console. Only one obvious difference that second one have framework which added by packagedDependency.

We don't use any -platform_version settings.
What should I take a look at to make it work again/find a reason?

[itlancer]

Strangely, but rebuild that ANE from scratch (Xcode .a lib and ANE itself) using latest AIR SDK did the trick and right now everything works fine again in my case.

But I found another critical issue with AIR 51.3.2.x: #4224

[Gokul617]

Hi

Thanks for your response. I removed some ANEs that were only used for the Android version, and the app is now running without any crashes.

Old ANE :

com.distriqt.Firebase
androidx.multidex
com.google.android.datatransport
com.google.dagger
androidx.cardview
androidx.room
androidx.work
com.distriqt.playservices.CloudMessaging
com.distriqt.Core
com.distriqt.playservices.AdsIdentifier
com.distriqt.playservices.Base
androidx.appcompat
androidx.browser
androidx.core
com.distriqt.InAppBilling
androidx.exifinterface
com.google.guava
com.bumptech.glide
com.distriqt.Share
com.google.code.gson
com.distriqt.Application
com.google.firebase.core
com.distriqt.IDFA
com.distriqt.ApplicationRater
com.google.android.play
com.distriqt.playservices.Ads
com.distriqt.Adverts
androidx.constraintlayout
androidx.vectordrawable
com.distriqt.firebase.Auth
com.distriqt.firebase.Database
org.jacoco
org.ow2.asm
io.insert.koin.koincore
androidx.webkit
androidx.datastore
com.distriqt.playservices.Cronet
com.jetbrains.kotlinx
com.distriqt.square.okhttp3
com.distriqt.admob.IronSource

Current ANE :

com.distriqt.Firebase
com.distriqt.Core
com.distriqt.playservices.Base
androidx.appcompat
androidx.browser
androidx.core
com.distriqt.InAppBilling
com.distriqt.Share
com.distriqt.Application
com.google.firebase.core
com.distriqt.IDFA
com.distriqt.ApplicationRater
com.distriqt.Adverts
com.distriqt.firebase.Database

[marchbold]

Were you able to identify which extension was the issue? Was it ironsource, I haven't updated that one in a while due to time restraints.

[BMGMobile]

Hi, we are having a similar issue after upgrading, and I suspect it is an outdated ANE. There are several candidate ones i'm looking at, is there a way to verify that a given ANE will be compatible with the new ios SDK?
In particular I suspect com.distriqt.ExpansionFiles as it is deprecated but I want to make sure before working on removing it

[marchbold]

Expansion files does have a stub implementation on ios but nothing major that should cause an issue. It's definitely deprecated though so would suggest removing it in new builds.