Correct Flash CS6 iOS publish settings for iPhone?

[kishliver]

My programmer and I are trying to publish an iOS app for iPhone from Flash cs6 and are being rejected because "Your app did not run at iPhone resolution and/or 2x iPhone 3GS resolution when reviewed on iPad. The contents of your app are not displayed within the confines of the screen."

In Flash CS6 iOS publish settings there is an option to export for iPad Only, iPhone Only, and for iPad and iPhone. iTunes Connect is sending us a screenshot that shows what we see when we publish a development IPA file using the iPad and iPhone setting. But the IPA file we submitted to them was published using the iPhone Only settings which when viewed on the iPad2 shows up inside the little iPhone 1X frame and can be expanded to 2X as well. I believe this is what they are saying is not happening when they do the same.

Has anyone else who uses Flash had this issue? If so what stage size and what publish settings should be used when trying to create an iPhone only app?

Thanks in advance, Patrick

[Skogemann142]

kishliver wrote:

If so what stage size and what publish settings should be used when trying to create an iPhone only app?

iPhone only app should be published with stage size:

640x960 for portrait view

960x640 for landscape view

... if the app are going to be fullscreen.

[kishliver]

When I publish it as iPhone Only, using the 960x640 stage size above, and then load it onto my iPad2, I'm getting the little iPhone frame, but the app is too big and I only see the upper left quarter of it inside the little frame. I am assuming that Apple will want this to work on iPad2 and 3 as well as iPhone 3GS and 4.

[Colin Holgate]

It's possible that you have put in lines to set the stage alignment and scale. Take those lines out, and then things should be ok.

[kishliver]

Thanks Colin, that worked! We still need to submit it to apple, but it solved the issue of the 960x640 not working correctly on the ipad. Thanks!

[caco_chapira]

Guys Adobe are investigating about it, please vote in my bug report,
and maybe it get stronger enough to Adobe fix the bug!

https://bugbase.adobe.com/index.cfm?event=bug&id=3938642