I am developping some apps for iOS using Flash CS 5.5. I have the apple certificate and all the necessary files. When I try to publish in the Flash, the .swf are generate, and a message "Publishing..." appears. After a while this message just disappear and the .ipa is not generated.
The problem is that I already generate 5 .ipa's in this same way...using the same certificate, etc. And there is no message of any error...any ideas?
Thanks and sorry for the bad english =P
Hi ottilie_haase, the problem was that my folder name hava especial character. If any folder or file in the project hava a especial character, the AIR will not generate the IPA. But there is no error message for this.
Thanks for your fast reply.
But unless "_" and "-" are special characters I think this is not my problem... I found this document (sorry, german) about known problems which mentioned the .fla file which I don't have... I am not sure wether this is a hint, but I'll give it a try.
Flash loves to forget where to publish your SWF. Go in publish settings and make absolutely sure your SWF is publishing to the right location. That means, hit the browse button, go to the location, hit OK. Try again.
Have you ever made any IPAs yet so far or is this your first? As in, did you ever get it to work before but suddenly it's not working?
This is the first time that I want to generate an .ipa, so it never worked before.
I'm sure that the .swf is published to the right directory (bin-debug), its modification date changed when I am starting to publish an .ipa. But, just to be really sure, where do I have to change the .swf location? My Flash Builder is in german, so I have to translate (which is not always that intuitive...).
I've found a possibility to change a directory (bin-debug is default) under project > properties > flex build path (? I think) > output folder. Is this where I would have to change it?
By the way: Thanks for replying me, I really appreciate it.
I hope I didn't something wrong while generating certificates and keys. That's a complex process... but so far everything worked without any error message (except of generating the .ipa file, of course...).
It is not the certificates or keys. If they are wrong, you cant even generate the SWF while publishing and a error message will appear. My flash is in portuguese (Brazil), but I think that you are in the rigth menu.
Are you doing this in a Mac or Windows? Are you using Flash CS 5.5 or Flex?
Wait, your first post said Flash CS5.5. Now you're saying Flash Builder. I'd definitely use Flash Builder if you have it and can use it but let us know which one.
As for Flash CS5.5 it's not just about where to place the SWF unfortunately. You ALSO need to (every time) go into the AIR for iOS settings and specify where the IPA file should be. You very well could be making it and it's just not the location you think it is. Otherwise it certainly should generate an error.
Keep your Java Runtime Environment up to date as well. There be a lotta java in these waters yarr.
In Flash Builder the SWF is put into (based on if you press debug, run or release build) the bin-debug or bin-release folders (or whatever you told it to name them during project creation time). Flash Builder will not screw up like Flash CS5.5 and put the files elsewhere. You can depend on the IPA showing up in the proper folder.
In both situations your .p12 file and .mobileprovision must be correct for the device and application you're exporting. The application ID specified in the XML must match as well. But these things generate errors in Flash Builder. Flash Pro I'm not so sure about.
Thank you all for helping me - but I found out that there was indeed something wrong with some certificate or key.
I tried building the .ipa with the cmd (I'm on Windows) and there I got an error message saying so.
Because I generated the certificates and keys with a Mac but intended to use them on Windows for developing something went wrong, I think. I then followed the steps for creating them on Windows described here and with those finally the .ipa was generated.
I generate my .p12 on a mac using keychain access. Its' so much easier than using (what I assume you're using) OpenSSL or such. I use a menu item to create the request, submit to apple, apple sends back my certificate. I install it, right-click on the kind I'd like (distribution or developer) and export a p12. It takes about 5 minutes.
However, then the certificate requires being updated by that mac unless you can get the seed the certificate request was signed with. I'm not even going to get into that...
I'm just stating I use a .p12 from a mac and I only EVER develop on a Windows machine.
One thing that is confusing to developers is the multi-step provisioning process. This can trip up your IPA creation every time.
When you want to make a new app, you must create an App ID for it on the portal. After you do that you create a mobile provision for it and/or based on the type you add in the devices that are allowed to use it.
Here's the PITA.
You must now go back to your developer or distribution certificate and recreate it because that new App ID is not automatically part of it. It is soooooo annoying. Now you need to hit the rolldown on the certificate, make SURE your new app is included in it, grab the certificate and regenerate a new .p12 file. Totally annoying as all hell. If you didn't regen that .p12 after you made your new App ID it will never work.
Apple is really stupid about this. The mobileprovision should be tied to the .p12 the .cer generates somehow so any app ID from that certificate ID is valid automatically without regenerating this p12 every time.
This is only a pain for a developer who's learning. I tend to set a wildcard and use a specific app ID so I can generate a bunch of test apps using the same mobileprovision and .p12. But that's not something they explain to you.