Keyboard buttons disappear and keyboard rendered wrong on iOS9 - ios

I'm getting reports of keys disappearing or becoming invisible on iPhone native keyboard and have also seen this happen on my iPhone 4S. The keyboard is setup for dark appearance decimal pad.
The bug is typically accompanied by this message.
Can't find keyplane that supports type 8 for keyboard iPhone-Portrait-DecimalPad; using 4131139949_Portrait_iPhone-Simple-Pad_Default
The problem seems to go away if I background the app and open another app and then come back.
As you can see in the screenshot the background of the keys also seems to be wrong for "dark" setting.
Snapshot of missing keys

Related

iOS: When VoiceOver is turned ON using the Accessibility shortcut of triple clicking Home Button, the screen gets turned off

The accessibility elements are being read correctly in the background, i.e the labels being read can only be heard but cant see the screen as it blacks out, just the screen goes dark. Anybody come across the issue?
Verified this is in iOS 11 with iPhone 6s, iPhone 7 plus.
(Project is in Swift although it must not matter)
Found out that with 3 finger triple tap on screen , the above setting gets disabled. And the Accessibility Voice Over starts to work as normal, i.e reading the labels with the screen turned ON.

UIKeyboardWillChangeFrameNotification not always called

When developing an app for iOS, I've encountered a strange problem.
To be precise, it's about a chat app. Inside the chat view controller, the message input box should stick to the keyboard when it appears. I've got that one covered with the UIKeyboardWillChangeFrameNotification.
However, the problem is that this notification is not called when I change from the default keyboard to the emoji keyboard, which is slightly taller, the notification is not called (I'm leading both UIKeyboardWillChangeFrameNotification and UIKeyboardDidChangeFrameNotification to the same selector, none of them is called, I've tested it by doing a NSLog and setting a breakpoint). That results in the keyboard overlapping the message box. I made some screenshots to visualize the problem.
Default keyboard
Emoji keyboard
I've tested it on an iPhone X and on the iPhone 8 Plus Simulator, but there, everything's fine because the auto-completion bar makes up the difference between the two keyboards.
Am I implementing the wrong notification? How should I solve this problem?
Okay, it seems like this was an actual bug in iOS 11. It seems to be fixed in iOS 11.2.6.

iPad mini Keyboard issue with ios8.x version

Sometime when I try to enter a text in textfield or textview , the key board comes up too large to fit on screen. so only part of the key board and keys are visible. I can turn the I pad sideways and make the missing keys visible, but then the keys won't work anyway. i have not done any keyboard customization in my app. I don't know whether it is an app issue or OS issue. Have you ever faced this type of issue?
Can you please help me to resolve this issue?
Device:iPad mini
Model=iPad2,7
OS Version=8.4.
The accessibility settings are turned off on this iPAD. Customers have reported the app is crashing if they press any key after G , after keyboard is zoomed in like shown in the attached picture.

keyboard displays in simulator on one machine, and not on another

So I just switched the keyboard type for the three textViews I have on one of my viewControllers to use the Number Pad keyboard. I also added a library (not a cocoapod) for a custom ScrollView object that I added to the view; the Scrollview makes all subviews scroll up/down to respond to instances of the keyboard being displayed onscreen.
It displays fine when I run the code on my machine's simulators (simulators for iPhones 5s and 6.) But when the other guy on the project tries it, the keyboard shows up briefly on the 5s simulator before hiding. On his simulator for the 6, the keyboard doesn't appear at all.
Could it be the custom Scrollview screwing with the UI? I'll post a link to the repo..I'd post some code but aside from this object, I can't think of anything else that could be responsible.
https://github.com/michaeltyson/TPKeyboardAvoiding
If you tap into a textfield and the keyboard does not appear, hit command+k on your physical keyboard to bring up the simulator one. You will still be able to type with your physical keyboard but the simulator one will come up as well.
Try command+shift+k. That turns on and off the simulated hardware keyboard. I have had it fix this kind of issue before, even when I didn't realize I had it turned on.

Decimal Pad keyboard not working properly in iOS 8

I'm developing an iOS 8 app in Xcode 6.0.1 and running it on my iPhone 5 (which has iOS 8.0.2 on it). In my app, I'm using a UITextField with the Decimal Pad keyboard type (I use the Xcode storyboard to set the keyboard type). Everything worked as expected when I was using iOS 7 and Xcode 5. However, after updating my software, I'm having this problem:
Every time I click on the UITextField, the Decimal Pad keyboard pops up normally (although the decimal button in the lower left corner is a half the size it should be), but then the UITextField won't animate upwards above the keyboard (like it used to) and the following message gets printed out on the console (however, my app does not crash):
Can't find keyplane that supports type 8 for keyboard iPhone-Portrait-DecimalPad; using 1425143906_Portrait_iPhone-Simple-Pad_Default
A number of "solutions" on the internet suggest going to iOS Simulator > Hardware > Keyboards and toggling an option in there. However, I'm not running my app on a simulator; I'm running it on my phone, so this solution does not work.
Thanks for the help!
Turns out, the issue with the UITextField animation was not due to the keyboard problem. I needed to set up constraints in Xcode's storyboard for the UITextField, make outlets for them in my view controller, and use the constraints to programmatically move the UITextField. I have that working now. However, the error message still pops up when the decimal pad comes up. I guess I can just ignore it until Apple fixes it.
EDIT:
I reported the bug to Apple.

Resources