Skip to main content
grahamsmith10151448
Inspiring
September 29, 2014
Question

Air 15 known issues - wrong screen size and dpi

  • September 29, 2014
  • 4 replies
  • 3173 views


Will the next update of Air 15 solve the issues below..

the dpi problem with iPhone 6 plus is a show stopper,  i cant get away with delivering a reduced dpi

... under pressure to update 20+ applications  ...


Known Issues AIR  15.0.0.183

[ iPhone 6 Plus] [Launch image] A blank screen observed in apps when Default-568h@2x is packaged.

[ iPhone 6 Plus] Wrong screen size and dpi is returned through the runtime APIs .

[ iPad 3 and later] iPhone Launch image(Default@2x. png ) appears on iPad if iPhone launch images are packaged along with iPad launch images

Well done to the Air team for the good work done so far, not easy keeping up with Apple on IOS8  at the moment...

This topic has been closed for replies.

4 replies

Known Participant
April 11, 2015

>>the dpi problem with iPhone 6 plus is a show stopper,  i cant get away with delivering a reduced dpi

Is this issue fixed with AIR 17 SDK?

AIR gives me for iPhone 6+ devices "640x1136px / 326 DPI" instead of the correct size and dpi of "1080×1980px  / DPI 401"

Is it me or is this a know issue?

kheftel
Inspiring
April 14, 2015

according to the above posts, have you made sure that you have iphone 6+ launch images in your app, and that the device is not in zoomed in mode?    

Known Participant
April 15, 2015

Yes, I have the iPhone 6+ launch image in my app.

"and that the device is not in zoomed in mode?"

How does an iPhone gets into the "zoomed mode"? Is there a setting I need to add to prevent this?

Many thanks

New Participant
March 12, 2015

I am having simliar issue where I can get the iphone 6 launch image to work but not the iphone 6+ when using Default-414w-736h-landscape@3x.png, 2208x1242.  Also the stage.fullScreenWidth/Height give 1472x828, which is 2/3 the expected dimensions or 736x414 at scale factor 2, not 3.  I hope adobe fixes this soon or we won't be able to launch new games with Apple as it is a requirement to have your apps Iphone 6/6+ optimized.  If this isn't fixed soon were pretty much forced to abandon adobe and move onto another software solution that will allow us to build for Apple.

kheftel
Inspiring
March 12, 2015

while this is unfortunate that it's not fixed yet, as far as I know you are not *required* by apple to optimize for iphone 6/6+.  I have a batch of 5 game apps that will be submitted in the very near future that are not optimized for iphone 6/6+, and I am not aware of anything that says it will be rejected because of that.

As I stated above, just optimizing for iphone 5, in my case case at least, still looks great on iphone 6/6+

Adobe Employee
March 13, 2015

Thanks for raising the concern,

However, I would request you to please re-verify the issue once by adding launch images as per the blog Launch Images on iOS with Adobe AIR.

If you still face the issue, please let us know.

Regards,

Jitender

New Participant
November 25, 2014

Any news on this? I am starting a new iphone-project in december. still getting a wrong launch-image in portrait-mode and wrong stage size. Should i go with swift now?

Inspiring
December 1, 2014

Yeah, I was planning to do an update and don't have the iPhone to test so want to make sure it is fixed before beginning to test.

tekintatar
Inspiring
September 29, 2014

yes we are under pressure too. I think below issue is related to known issues as well. I hope these will be fixed soon

Bug#3831747 - Adobe Air Initiates the wrong launch Image on iPhone 6 - Possible App Rejection by Apple Review Team for a…

kheftel
Inspiring
October 28, 2014

With the latest AIR SDK (15.0.0.349), I can get iphone 6+ launch screens to be used properly (Default-414w-736h-landscape@3x.png, 2208x1242), but stage.fullScreenWidth/Height give 1472x828, which is 2/3 the expected dimensions or 736x414 at scale factor 2, not 3.

Inspiring
November 13, 2014

Is there a bug report for the stage size?  I use this to adjust the layout and air 16 beta still has this as an issue.  Is the value that the stage size returns with this bug constant?