Adobe AIR iOS 12.1 support

[atulpere]

Hi All

While uploading the app on App Store, got the below warning message:

"SDK Version Issue - This app was built with the iOS 11.0 SDK. Starting March 2019, all iOS apps submitted to the App Store must be built with the iOS 12.1 SDK or later, included in Xcode 10.1 or later."

Can anyone please guide me, what would be the quickest resolution for the same.

Thanks

Atul

[amritag9336052]

Hi Atul,

Thanks for reporting the issue!

We are looking into it.

[44142744]

Is there any update on this issue please with more detail other than 'we're looking into it'?

People have been asking about this since last December and March is fast approaching.

All developers using Air in iOS apps need a response on this ASAP as it will become impossible to update our apps using Air after the end of this month.

?!

[Rohit Guglani]

Hello All,

We have done a AIR beta today, you can download it from Adobe AIR 32 Beta | application development - Adobe Labs which contains the fix for this issue.

Regards,

Rohit

[rewb0rn]

Thanks Rohit!

[atulpere]

Hi Rohit

We tried the latest Beta version as suggested by you but it ended up with below error.

Packaging failed!

Packaging error message:

Compilation failed while executing : ld64

Packaging output:

ld: entry point (start) undefined. Usually in crt1.o for architecture arm64

Undefined symbols for architecture armv7:

"_OBJC_CLASS_$_NSObject", referenced from:

     _OBJC_CLASS_$_CTAppDescriptor in libRuntimeHMAOT.arm-air.a(CTContentPlayer.o)

     _OBJC_CLASS_$_ExtensionInfo in libRuntimeHMAOT.arm-air.a(CTContentPlayer.o)

     _OBJC_CLASS_$__CTPlayerTimerGlue in libRuntimeHMAOT.arm-air.a(CTPlayer.o)

     _OBJC_CLASS_$_ServiceASyncOnMainThread in libRuntimeHMAOT.arm-air.a(CTPlayer.o)

     _OBJC_CLASS_$__CTGestureState in libRuntimeHMAOT.arm-air.a(CTStageView.o)

     _OBJC_CLASS_$__CTTouchInfo in libRuntimeHMAOT.arm-air.a(CTStageView.o)

     _OBJC_CLASS_$__CTTransform in libRuntimeHMAOT.arm-air.a(CTStageView.o)

     ...

"_OBJC_METACLASS_$_NSObject", referenced from:

     _OBJC_METACLASS_$__CTGameInputDevice in libRuntimeHMAOT.arm-air.a(CTGameInput.o)

     _OBJC_METACLASS_$__CTGameInputButton in libRuntimeHMAOT.arm-air.a(CTGameInput.o)

     _OBJC_METACLASS_$__CTGameInputAxis in libRuntimeHMAOT.arm-air.a(CTGameInput.o)

     _OBJC_METACLASS_$__CTDeviceRotationEventSource in libRuntimeHMAOT.arm-air.a(CTDeviceRotationEventSource.o)

     _OBJC_METACLASS_$_CTAppDescriptor in libRuntimeHMAOT.arm-air.a(CTContentPlayer.o)

     _OBJC_METACLASS_$_ExtensionInfo in libRuntimeHMAOT.arm-air.a(CTContentPlayer.o)

     _OBJC_METACLASS_$_CTApplication in libRuntimeHMAOT.arm-air.a(CTAIRApplication.o)

     ...

ld: symbol(s) not found for architecture armv7

Please check.

[atulpere]

hi Rohit

is there any further update. I have tried the beta update but no luck.

Rohit Guglani​

Thanks

[44142744]

Hi Rohit,

Is there any update on when a new version will be available that fixes the reported issues?

Thanks!

[atulpere]

hi Rohit

Any update on this?

Regards

[Flipline]

Are you using ANEs in your app?  When AIR 32 started using the iOS 12 SDK, there are a handful of things that Apple removed support for, which can cause errors when packaging apps with some older ANEs that haven't been updated for iOS 12.

In the AIR 32 Release Notes, it mentions this in the iOS SDK Upgrade notes, which might be related to your error:

We have updated some of the symbols in the stub files generated, which are in accordance with Apple’s changes. If you see below error during packaging ipa with ANE, repackage the ANE with the latest AIR SDK.

Error: Undefined symbols for architecture armv7/arm64
If we are using -platformsdk, we need to replace the ld from /Applications/Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin to /AIRSDK/lib/aot/bin/ld64/ld64 and rename it to ld64.

If you're using ANEs, you may want to try packaging without the ANEs to test if that's the problem.  If so, you may need to contact the ANE developer and mention that they'll need to update it for compatibility with iOS 12 / AIR 32.

[Paul Darky]

Hi Rohit,

Any idea when this will be fixed?

[近宇吴63385821]

Hi Rohit,

We can't uppoad any IOS App now with AIRSDK 32.0. Although the version of 32.0 BETA is ok, we can't put our APP into production using BETA version. Is there any news about newest release version? We're waiting for it.

[44142744]

Hi Rohit,

Is a further release in development?

Thanks!

Lorraine

[Frédéric C.]

A new AIR 32 beta has been released today:

Fixed Issues

AIR

Mar 15, 2019

ld error on Windows when using platformSDK option (AIR-4198796)

[scottg21861983]

We were testing video play back and have found since upgrading from 32.089 to the beta, (in order to get the ios sdk12.1 fix) android video playback no longer has audio. ios is fine this only relates to android.

[44142744]

Hi Rohit,

Is a final release in development?

Thanks!

Lorraine

[LilGames]

Hello,

It is now April 5, 2019 and Apple's deadline on submitting apps using iOS 12.1 has passed !

What is the status on this?

[Flipline]

The beta version of AIR supports 12.1, but unfortunately there's not a final public release that supports it yet.

You do have to make sure all of your ANEs will support 12.1 as well, since any ANEs that support iOS 6 or earlier will cause your app to either fail compilation or get rejected by Apple, since iOS 12.1 doesn't allow support for versions that far back.  Even if you set you app's minimumOSVersion higher, any ANEs that support those lower versions will cause problems either with compiling or with Apple.

[LilGames]

I see what you mean... I got this response after uploading to itunesConnect:

Invalid architectures - This app has invalid architecture, and may have been built with invalid build settings or incompatible tools. Try rebuilding the app with the latest Xcode version. If you are using third party development tools, contact the provider.

I guess that's it then. Adobe Air is dead to me for iOS now, since my ANEs stopped being supported too (all MilkManGames ANEs... a developer that Adobe used to promote and possibly help out financially, but I guess Adobe abandoned him and now he doesn't update them anymore).

[Flipline]

You could try switching to the distriqt ANEs here, they've been great about keeping their ANEs up-to-date to get around these new iOS 12.1 issues, we've released some app updates using iOS SDK 12.1 and their ANEs.  We used to use MilkManGames ANEs, but with no more support or updates we've had to switch ourselves.

[Paul Darky]

Hi Flipline:

I have the same issue with the Milkmangames Admob ANE (no reply to emails, no support).

I saw the distriqt ANEs website.

I just want to ask you: does their ANE support SMART BANNER, INTERSTITIALS and REWARDED VIDEO?

I don´t know why they just say: "SIMPLE ADMOB ADVERTS"

Best,

[Flipline]

Yes it does, here's a direct link to their "Development Guide" documentation with more details:

Adverts by distriqt

On the left menu under "Usage" they have separate pages for banners, interstitials, and rewarded video ads. 

Overall there's a bit more work involved vs. the MilkManGames ANE, since instead of one line of code you need to first create an AdView to hold an ad, then make an AdRequest with an AdRequestBuilder, then listen for events to determine when that AdView should be visible.  But it does give you greater control over how and when your ads load and display, plus it's updated with newer features like GDPR consent.

[Paul Darky]

Thank´s a lot for your reply!

Best,

[LilGames]

Ugh.

[smolho]

Hi Rohit,

We've just tried to submit our app with the final AIR 32 SDK to Apple and got the same error:

ERROR ITMS-90725: "SDK Version Issue. This app was built with the iOS 12.0 SDK. All iOS apps submitted to the App Store must be built with the iOS 11 SDK or later, included in Xcode 9 or later. Further, starting March 2019, all iOS apps submitted to the App Store must be built with the iOS 12.1 SDK or later, included in Xcode 10.1 or later."

Although you wrote here and in the release notes of AIR 32 that it compiled with iOS 12.1 SDK.

Why is it happening?

and what is the timeline for solution?

We can't approve our new version of the app in the AppStore!