AIR 51.1.1.2 - Keyboard does not come out on many devices

[fix89]

After updating our app with Air 51.1.1.2 we received numerous reports of users who did not see the keyboard when they touched an input text. We were forced to send a new update released with AIR 51.0.1.4 where the problem does not exist.

[ylazy]

Hi!
You should provide more details to determine where the problem is. What operating systems / devices are your users using? What framework are you using? What component is affected? Can you provide a sample code that can reproduce the problem?

[fix89]

It’s an Android only bug. I was unable to replicate the problem on my devices, but many of our app users reported the problem, many had a Samsung device.

[ajwfrost]

@fix89 we've not been able to reproduce this on Samsung devices here but we may not be checking the exact same thing. Can you confirm whether this is happening for TextField objects that are in 'input' mode, or for StageText objects? And do they say that the keyboard just doesn't appear, or might it be that it appears then immediately disappears? Plus: do you use the runtime in 'background' mode on Android?

If you can provide an APK file that we could use to reproduce this, it would be useful (along with whatever instructions are needed to get to the location where the keyboard should be triggered..)

thanks

[maxddd23]

I also encountered the same issue.

TextFiled requires multiple clicks to call up the keyboard.

The following videos are for AIR versions 51.0.1.3 and 51.1.1.3 respectively

51.0.1.3 AIR version 51.0.1.3 is working fine.

746685657.270856.mp4

51.1.1.3 AIR version 51.1.1.3 is calling keyboard difficult.

746685657.363998.mp4

Devices known to have this issue
1.Samsung Galaxy S21
2.Samsung Galaxy S23 Ultra
3.Samsung Galaxy Tab S7 FE

Please check this issue, thank you.
If you need an apk file, I will make an additional one and provide it to you.

[fix89]

Any news on this? We can not use the latest AIR SDK

[fix89]

Latest AIR 5.1.1.4 fix this issue?

[maxddd23]

HI

I only listen to the MouseEvent.CLICK event.

I can confirm that this problem does not exist in 51.0.1.3.

So I wanted to confirm if this is a 51.1 specific issue.

I can't tell if it's caused by slight movement of my fingers.

Because sometimes the keyboard cannot be displayed even if you click hard.

This problem has caused considerable distress to some users.

My app does not use the scroller component, it is just a simple input TextField.

But it still happens.

If you can correct this issue or have better suggestions for optimization.

Please help me. Thank you.

[ajwfrost]

Thanks - just to confirm/clarify, when I was mentioning the touch down/move events, these are the direct events we are getting from the Android system and handling internally, rather than what we're passing on to the AS3 code (which would be independent of our changes here). So it's not related to which events you're listening to, but from the code changes that went in, it's related to what actually happens from the Android OS from the touch events.

It's currently actually a one-pixel sensitivity and probably the way some screens work, as a finger approaches the screen you'd get an additional touch point, but then if you press, the touch "point" given would be at the heaviest pressure point, which may then be different.

By the sounds of it though - I will revert the earlier change in its entirety, and we'll make sure we don't have a side-effect like this when we put back in the handling for pass-through scrolling (i.e. where you're trying to scroll the whole application and you happen to touch in a text field).

thanks

[maxddd23]

Thank you for your support.

[fix89]

Thank you! Do you have a date for the new AIR release? Or is it possibile to have a beta release to test?

[ajwfrost]

Hi - hopefully we will get our next release towards the end of next week, or early in the following week - but for now, the attached can be unzipped and placed over the 51.1.1.4 SDK, in /lib/android/lib folder.
android_patch.zip

thanks