Can't upload to iTunes using Xcode 9

[peter_nicolai_123]

When trying to upload our app to iTunes we get this error:

Missing Info.plist value. A value for the Info.plist key CFBundleIconName is missing in the bundle '<app.bundle.xxx>'. Apps that provide icons in the asset catalog must also provide this Info.plist key. For more information see http://help.apple.com/xcode/mac/current/#/dev10510b1f7.

We are packaging the 1024x1024 appstore image but I guess we need something more here?

[peter_nicolai_123]

OK - we need something more.

As explained here: Core Foundation Keys , the Plist key that AIR uses for icons, CFBundleIconFiles, is essentially deprecated, and the newer format, CFBundleIcons, has taken precedence over it since iOS 5.0. I guess this was never updated in AIR since it still continued to work.

This newer dictionary contains a key, CFBundleIconName, which if it isn't present and pointing to a 1024x1024 appstore image, you won't be able to upload your app from XCode 9, even just for Testflight. Unfortunately our upcoming release contains iOS 11-specific features and cannot be built with an earlier version of XCode. Maybe there's a way to trick an earlier version of Xcode to upload it?

In any case it's pretty clear this should be updated ASAP.

[dews]

We're also using iOS 11 specific features for our upcoming release - Adobe please help.

[peter_nicolai_123]

Just to let people know, we tried uploading from Xcode 8 and Apple still rejected the build, so that doesn't work.

Does anyone from Adobe have a minute to post a reply to this thread just to let people know you're aware of the issue?

[Anki_AG_]

Hi,

Apple has mandated use of App Icon in case application is built with Xcode 9. So if you are using Xcode9 with platform sdk option for developing AIR application , you need to provide App Icon. For more details please refer https://help.apple.com/itunes-connect/developer/#/dev8b5cb82e2 . We are working on this issue.

Could you please let us know the steps you have used in uploading the application using Xcode8.

Thanks,

Ankit | Adobe AIR Engineering

[peter_nicolai_123]

Anki(AG)  wrote

Could you please let us know the steps you have used in uploading the application using Xcode8.

Why? It doesn't work, you can upload it but Apple will still reject it.

Finally in order to upload, we created an asset catalog and modified the plist using PlistBuddy, and then repackaged/re-signed the app so it complied with Apple's requirements. We already have to do this anyway because we are including iOS app extensions (as distinct from ANEs), but frankly I was surprised this worked, it's a very Frankenstein-like approach. For a lot of developers who don't already package their app this way, it's going to be a lot of work just for an icon. I'm assuming this will be in a future version of AIR?

[Anki_AG_]

Hi,

Glad that workaround worked for you. We are working on a solution that minimizes the hassles for developers to add app icon. The reason we asked the steps for Xcode 8, is due to the fact that till Xcode 8 app icon is not mandatory and in case app is packaged using AIR 27 then it should work fine if you are not using iOS 11 SDK using platform SDK switch.

Thanks,

Ankit | Adobe AIR Engineering

[peter_nicolai_123]

Yeah the problem is we had to use that platform switch because we are incorporating features in an ANE that only exist in iOS 11, I guess this is the situation for dews​ as well. So if we include this ANE it can't be built without that platform switch, even though we are still supporting earlier OS versions, and if it's built with that switch, Xcode 8 will still upload it but it will be rejected after uploading. (This is actually more annoying too, because when this happens, you have to change the version number before attempting to upload again, even though that build isn't visible anywhere in the iTunes dashboard.)

I don't know if our workaround is the best way to handle this but it was fairly simple after a bit of trial and error, so it shouldn't be too much work for you guys to incorporate it in the adt packaging process. Unfortunately for us, we are still unable to package our app on iOS using any version of AIR after 22 because of this issue: Tracker

Would it be possible for Adobe to make a decision to either try to fix this or mark the issue as "Won't fix" ?

[dews]

Assuming that this and other issue will be addressed in the next release, can Adobe please let us know when Air 28 is going to be up on Labs?

[Colin Holgate]

I don't know the answer, but often Flash Player and AIR SDK get updated in labs around the same time, and Flash Player 28 was updated today.

[dews]

Ah, exciting!  I notice the FP Release Notes heading is: "Flash Player 28 and AIR 27 Release Notes"

Hope there won't be too much of a delay for Air 28..

[dews]

We are using iOS 11 SDK using the platform SDK switch - when is Air 28 Beta going to be released?

[peter_nicolai_123]

Tried AIR 28 today, looks promising..

Tracker

This, or something similar, has meant we've been stuck using AIR 22 since AIR 23 came out; we use a preloader with a main SWF which would throw errors starting with AIR 23, but it seems to work again now. It would be a really big deal for us if we can finally be up to date, and it would simplify our build process a bit since it's handling the newly required way of packaging icons so we wouldn't have to.

The rendering of anything using cacheAsBitmap is messed up, but you mention that as a known issue, so we'll be checking for a fix for that.

Anyway, awesome!

[el111 · Accepted solution]

AIR 28 beta is out.

AIR now built with iOS 11 SDK

Download Adobe AIR 28 Beta - Adobe Labs

[dews]

NICE!!!!