Skip to main content
Inspiring
February 12, 2019
Answered

Publishing to App Store

  • February 12, 2019
  • 3 replies
  • 3057 views

Hi

I can produce an In House App fine and publish to an attached iPad whilst doing so and test there.

Using the exact same Animate .fla file

When I try and produce an app for the Distribution to the App Store

If I try to publish to a connected iPad I get this error:

iPad: The device has encountered an unexpected error. Installation Error: ApplicationVerififcationFailed.

This happened whether I used an App store provisioning profile or an Ad Hoc one.

I can publish ok if I don't try to publish to a connected iPad.

Then when I try and load onto the iPad using Xcode I get:

A valid provisioning profile for this executable was not found.

I found a thing about Assets.car so I created one of those and had it in the root directory and also attached it as a file in the included files in the AIR for iOS General section.

Can any help me work out what I am doing wrong.

This topic has been closed for replies.
Correct answer ASWC

You need dev certificate and profile to work and develop locally, you need distribution certificate and profile to upload to appstore. You also need to switch on/off the <Entitlements>, on for appstore, off for dev.

3 replies

Inspiring
February 15, 2019

ASWC is right.

On Animate CC 2019 AdHoc is only working with a Devt Certificate and Prov Profile.

I now have the app up on Apple Store Connect and I am testing it in Testflight on my iPad so all is good. I can test it that way before submitting for review.

You seem to need have the Assets.car attached (helpful info on that here AIR Native Extension Tutorials by airnativeextensions  ) but also the 72x72 and 156 x156 icons added within the Air for OS Icons panel in Animate CC.

NB I get a warning saying the iOS SDK is version 12 - which seems wrong as I am using AIR SDK 32 - but it is only a warning so the app load goes ahead ok.

So for anyone in my position who finds this:

1) Publish to your iPad using a Devt certificates and Provisioning Profile with Ad Hc as the target to test locally.

2) After that once you use a Distribution Certificate and Provide Profile you need to upload to Apple Store Connect and then use the Testflight app on your iPad to download the app to test.

PS The Application Loader application is inside X-Code 10.0, click on the left most Menu (Xcode) and select Open Developer Tools - Application Loader is launched from there.

Many thanks ASWC and Flipline for your help on here!

Best Tommy Banana

Inspiring
February 15, 2019

Where is Application Loader?

By the way I phoned Apple Develop support and asked where to find Application Loader and was told that it wasn't Apple Software.... !!!

Inspiring
February 18, 2019

Application Loader is part of xcode. You need to have xcode installed in your mac, and then go to xcode - developer tools - application Loader, connect with your credentials and upload your app.

Flipline
Inspiring
February 12, 2019

If you're publishing a build for the App Store, you can't test that on your own devices locally, it's only for submission to the App Store and that version can only be played if it's retrieved from the App Store.

We'll usually publish an Ad Hoc version to test locally on devices, since it's functionally nearly the same as an App Store build, and it can be installed on your own devices.  If you're using Animate, you'd switch iOS deployment type to "Ad hoc", and then use your Distribution Certificate and an Ad Hoc provisioning profile.

For the App Store build you'd use your Distribution Certificate and your App Store provisioning profile (and switch deployment type to Apple App Store), and as long as everything worked correctly on your device with the Ad Hoc build then the App Store build should be fine as well.  If you really want to test that App Store build you would first have to upload it to the App Store through Xcode / Application Loader, and then you should be able to test it using Apple's beta-testing system with TestFlight.

Inspiring
February 12, 2019

Thanks so much for the reply.

Is can I check.

You use the same .p12 certificate.

But make an ad hoc provisioning profile for the same APP ID.

Set the target to ad hoc.

Do you have an Ipd attached and post publishing add it to the iPad for testing?

I am trying this and I am still getting the same error.

Can I Ask:

1) Which version of AIR SDK are you using? Does it matter?

2) Have you created an Assets.car file and if so how are you linking it into the AIR comp[iler?

3) DO you think it has anything to do with not having the correct number or sizes of App Icons or Launch Screen images?

Inspiring
February 13, 2019

You're right, I should have specified that Entitlements are automatically added in AIR 31+, if you're using an older version of AIR you'd need to update.

I suppose it depends on what kind of apps you're developing, but ad hoc builds are most definitely important for us for local testing.  Dev builds have wildly different performance compared to an adhoc/appstore build in our games, usually running at 20-24 fps in a dev build vs. 30 fps in an adhoc.  Since adhoc and appstore builds are virtually identical we'll switch to an adhoc build at the end of development for performance tuning, so we have a better idea of how it'll run for the end user, because dev builds definitely don't give us that.  We make heavy use of vector graphics in gpu mode, so I'm not sure if that performance disparity with dev/adhoc for us is related to that, but we see a big difference.


Ouch! yeah vector graphics ... Mobile device don't like those one bit. Since some of our app came from legacy Flash apps we took the extra steps to convert everything to raster and run in GPU mode (if we really need super perf we go direct mode and Stage3D) and perf is very good. Also we took that step in order to make later conversion to other tech easier (most having no vector graphic support) which is what happened when we converted to HTML5 and WebGL.

ASWCCorrect answer
Inspiring
February 12, 2019

You need dev certificate and profile to work and develop locally, you need distribution certificate and profile to upload to appstore. You also need to switch on/off the <Entitlements>, on for appstore, off for dev.