Skip to main content
Participant
October 20, 2015
Question

iOS keyboard problem

  • October 20, 2015
  • 1 reply
  • 519 views

Hi,

Our company have developed AIR mobile application for Android and iOS phones and tablets.

It's important to notice that our application use different orientations for different parts of application.

Android version work fine, but we face the problem on iOS version. Problem described in

https://bugbase.adobe.com/index.cfm?event=bug&id=3943007 , also I have found very similar problem in

https://bugbase.adobe.com/index.cfm?event=bug&id=4032551 (moreover, I think it's same bug).

In short, our headache is keyboard, that don't properly rotated when stage changes orientation.

There is no problem in AIR 15, but all subsequent versions of AIR have that bug, even new released 19 version.

We can't use AIR 15, as it doesn't support 64-bit Apple App Store requirement.

Is there a way to fix this, soon? Is it possible to control iOS keyboards orientation?

Maybe it's possible with native extension (ANE)?

Thanks.   

This topic has been closed for replies.

1 reply

Adobe Employee
October 21, 2015

Hi,

Thanks for reporting the issue,

Yes, we are aware of keyboard orientation problems in iOS and working no it.

Meanwhile, could you please check if these problems are solved by keeping <autoOrients> tag in application.xml to true.

Regards,

Adobe AIR Team

Participant
October 26, 2015

Thank you, for your reply.

I have done this, but the problem with keyboard still exists. This is not my screenshot (Bug#3943007 - Orientation issue AIR SDK 17 BETA 115) but it illustrates my problem:

After i manually rotate device, keyboard turn to right orientation. But we think it's bug.

Also, i have seen another problem: when iPad in landspace orientation and keyboard in landspace orientation, but keyboards size and location looks like it in portrait mode! But, since I have followed your advice and turn the <autoOrients> tag to true, i have not seen this problem yet. But it's very hard to find bug, so i am not sure, that this problem have solved.