I've spent a few days trying to research this as I feel the answer would be a 1 liner, but here goes:
This question does not refer to custom keyboards on iOS but to the system keyboard that pops up for first responders.
I noticed that the default keyboard on most apps is shorter and more slick than the keyboard I end up getting on my app.
Here are the keyboards (sorry for not uploading the photos, I don't have enough rep yet)
Most apps:
http://i.imgur.com/FRU19oy.png
The keyboard I'm getting:
http://i.imgur.com/poEiNGs.png
Is it a some config that I'm missing? An OS version target issue?
Thanks!
You can add the following to your code:
textField.autocorrectionType = UITextAutocorrectionTypeNo;
Where textField is your text field or text view that is showing the keyboard.
It looks like you have a custom keyboard enabled on your device - you can disable it within the keyboard settings at the OS level. The "stretched" keyboard some apps experience is related to the scaling that takes place to stretch up iOS 7 apps to iPhone 6/6+ but it doesn't look like this is the issue you're experiencing based on the screenshots.
Related
I have a small issue, the issue is the Keyboards that I am adding from settings -> General-> Keyboards -> Japanese are not getting visible in my iOS App. For example, I added Japanese Keyboard Kana and listed it on the top list, it is still not getting displayed in my App. However it is getting displayed in other Apps like Apple Notes and all.
Did anyone face the same issue. I really need solution for this.
Thanks here is the screenshots of my keyboards added in keyboard section
Press the globe icon to switch between keyboard layouts. Its position will differ slightly depending on the layout.
For my existing iOS-projects, I noticed a keyboard bug when I run the app's on an iOS 11.1 simulator / real device: The bar above the keyboard is flipping high and down, after I switched from one textfield to another. For testing purposes, I created a new iOS project from scratch and the bug occurs again. Does anybody have the same issue (and maybe a solution)?
Under the link https://ufile.io/en8eg there is a demonstration video.
Greetings!
Try turning off the predictive text, I think that's what you were referring to when you said "the bar above the keyboard".
Try this in the viewDidLoad:
textField.autocorrectionType = .no // Swift 4
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.
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.
I am coming across a strange bug in my app, that I believe is an iOS 6 bug.
I have a UITextView that contains some text that has some links and phone numbers. In my storyboard, I have Links & Phone Numbers checked under 'Detection' for my UITextView. In code I also do:
_txtvFooter.editable = NO;
_txtvFooter.dataDetectorTypes = UIDataDetectorTypeAll;
The issue I am having is a strange one, but when I run my app onto my device (or sim) from Xcode, the UITextView detects all of the links fine, and I can click them. If I then run the app not in debug (not running through Xcode), the links show as black standard text and cannot be touched. Note this is only happening on iOS 6.
On the iOS 5 simulator, the links show as blue and are clickable no matter if the app is run in debug, or just ran from the simulator.
I have looked all over the internets, and cannot find a solution or anyone else who has reported this issue. Does anyone know if something changed in iOS 6 specifically? I thing is, like I said it detects the links when run straight from Xcode, so to me it seems like an iOS 6 bug.
Any help is appreciated!
I found what was causing my issue. What I was doing was placing a UIView in the footer of a UITableView in Storyboard that contained a UITextView.
The fix was dumb... I removed the UITextView from the UIView and just used that as the footer (I at one point had multiple textviews in the footer) and the links began detecting.
I still believe this is a bug though-- because if you do need to use a UIView the links would not detect from the textviews within.