Legend

Answered

New AIR version (21.0.0.176) - still no Windows fix?

Forum|Forum|9 years ago
March 11, 2016
6 replies
2993 views

A new non-beta version of AIR was released yesterday, but in the release notes it still says we can't package IPA on a Windows machine for release.

Adobe, is this for real? It's been a while since AIR 19.

Development

This topic has been closed for replies.

Correct answer Roshan Chhetri

Hi All,

The issue of invalid build has been fixed on both Win and Mac AIR SDK's.

Please find the fix here: Download Adobe AIR 22 Beta - Adobe Labs

Thanks for your patience. Kindly let us know if you have any queries.

-Roshan

Adobe Air

R

Roshan ChhetriCorrect answer

Adobe Employee

Hi All,

The issue of invalid build has been fixed on both Win and Mac AIR SDK's.

Please find the fix here: Download Adobe AIR 22 Beta - Adobe Labs

Thanks for your patience. Kindly let us know if you have any queries.

-Roshan

Adobe Air

saglam.mehmet

Participating Frequently

Great news, thank you very much...

J

Julien26

Inspiring

For information, my app got accepted and is now live ! So the final IPA was built with Air 20 on Windows (with Animate CC), and the P12 certificate was exported from Keychain on the mac ! And of course I had to use Application Loader to send the IPA.

Lars LaboriousAuthor

Legend

That's good news!

Makes you wonder if you can actually export the P12 on Windows as well (with OpenSSL) as long as you create a new certificate.

A

Anonymous

>Makes you wonder if you can actually export the P12 on Windows as well (with OpenSSL) as long as you create a new certificate.

Doesn't help with ANEs - our Windows build was rejected although we could test and debug on devices. Wasting a lot of time now as FB4.7 no longer works consistently under El Capitan either - have had to uninstall/reinstall a couple of times this week already as it keeps corrupting itself. We're ditching AIR for new work but have several apps to maintain - Animate doesn't cut it - is there a good run down pro/cons page on 3rd party IDEs for OSX anyone can recommend.

J

Julien26

Inspiring

If the problem is for creating the P12 on Windows, the label in the release note should be changed ! It says the following :

[iOS][Win] IPA packaged on Windows machine cannot be submitted to the Apple App store. Error "This build is invalid" occurs in iTunes connect.

I think that a lot of developers have a mac for the Application Loader, so they should know that if the certificate is created on a mac they will be able to upload the IPA ! I was ready to spend my afternoon configuring the mac to build the application with command lines and adt, luckily for me I decided to take 15 minutes to test the build with Windows !

Colin Holgate

Inspiring

The part you quote is in the list of things that were fixed. That is, you can now submit to the Mac App Store. This discussion is about submitting to the iOS store, as mentioned in the known issues list:

[iOS][Win] IPA packaged on Windows machine cannot be submitted to the Apple App store. Error "This build is invalid" occurs in iTunes connect.

The problem may not be to do with the P12, but if Mac users cannot submit without updating the P12, I would expect Windows users to also have to update the P12. Julien26 did make a new P12, and seems to have got past the Application Loader stage.

J

Julien26

Inspiring

Yeah I saw after sending my post that I didn't quote the correct line. I edited my post but the modification doesn't appear (but it's still there if I try to re-edit my post... it's strange).

J

Julien26

Inspiring

My app is still waiting verification ! I'll let you know when the status changes.

And yes I created a new certificate for that upload on my mac, because my previous certificate expired. I followed the steps on developer.apple.com to create the new certificate, and I exported the .p12 file directly from the Mac Keychain. I could use it on Windows without problem.

Like Colin said, I see in the mac keychain that Apple's certificate expired because I have a warning that my certificate isn't valid, even if I installed Apple's latest version. But I'm pretty sure that if the certificate wasn't OK the Application Loader would have told me something, so I hope that my app will be accepted !

Colin Holgate

Inspiring

You using a Mac to make the P12 is a different combination to others who are doing all stages on Windows.

BTW, you should delete the expired certificate from Keychain Access. Until I did that I couldn't even install onto my own devices.

J

Julien26

Inspiring

Hi guys,

Just a question : I'm using Air 20, and I just tried to package the new version of my app for the App Store using Animate CC on Windows, and that worked pretty well, as usual. I have been able to send the binary with Application Loader, select the binary in itunesconnect and submit the new version for verification.

Will the bug appear later in the process, or didn't I encounter the bug ? Because I don't want to wait 6-10 days to finally have the app rejected because of that bug.

Thanks in advance

Lars LaboriousAuthor

Legend

Hi Julien26,

Last time I tried submitting an app - with version 20 - it failed when trying to upload through Application Loader, so I'd say it does look promising if you got it passed that point.

Two questions: Have you heard anything from Apple yet? And are you using new p12 / certificates (ref. what Colin is talking about)?

Anki_AG_

Adobe Employee

Hi,

Yes, we certainly understand the inconvenience you might be facing because of this. However, I am sorry to inform that we're still investigating this issue, and there hasn't been any significant progress on it. The problems that we're facing is that things have changed from Apple verification side, and it isn't looking straight forward to port these new changes on signing process for a Windows system. I would want to re-iterate that the issue comes into picture only while uploading the final IPA, and it shouldn't hinder any development or testing phases. So, you may still continue all your development on a Windows system, the final IPA build however should be packaged on a Mac for a successful upload to iTunes store.

Thanks,

Adobe AIR Team

Lars LaboriousAuthor

Legend

Thanks for answering.

Good to know you are still actively trying to solve it.

The problem for indie developers like me, is that we don't have unlimited access to equipments. Meaning, in my case, while we do have a simple Macbook for uploading IPAs through Application Loader, packaging is normally done on Windows where all the files reside. So there's no quick fix using the Mac for packaging - since we would have to install Adobe Animate CC on the Mac and move all files to generate the swf for packaging + creating the keychain there (instead of using openSSL on Windows). Or am I missing something?

We might be better off giving up Windows.

Anki_AG_

Adobe Employee

Hi,

You just need Mac machine for packaging the final ipa. Please use this adt command on Mac

adt -package -target ipa -storetype pkcs12 -keystore <certificate> -storepass <password> <ipa name> <xml> -C <swf> -C <assets>

Before that please make sure that certifcate has been added to the keychain of Mac machine. If possible, please try this out.

Thanks,

Adobe Air Team

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded