Predicitve text/suggestion above keyboard doesn't work? - ios

My whole Xcode project has a weird behaviour,dont know what is causing this issue I am getting prediction and suggestions above my keyboard, but when I click on the text it doesn't call any method or when I try clicking on the predicited text it doesn't work.
is there by chance because of using third party pods?have tried all types of textContentType I get suggestion like name,phonenumber,otp but unfortunately when I tap on it it doesn't work
its behaviour is literally like the predicition has user interaction disabled

Related

Why does Android ViewPager2 looses focus when switching between tabs?

I have a ViewPager2 on my Android App. One of the pages contains an EditText field.
The scenario I encountered is as follows:
Set focus on the text field -> keyboard shows
Switch to another page -> keyboard dismisses (the field lost focus)
Go back to the previous tab and set focus on the text field again -> the field will gain focus but immediately the focus would clear. Tapping on the field again will get the focus back.
I prepared a small demo app to demonstrate this issue: https://github.com/hilaza/SwitchTabsBugDemo
I debugged it and what I found was that the ViewPager clears the focus from my page, thinking that a page was selected. Debugging it further I saw that it has something to do with the RecyclerView's didChildRangeChange method which wrongly assumes that something has changed.
Does anyone happen to know why it's happening and what can I do to work around this?
This is a strange bug happens because of Recycler behaviour. Unfortunately, cannot explain why it happens, but know for sure that this row might help you:
pager.offscreenPageLimit = 1
Or the equivalent in Java. This may help because it disables some of Recycler behaviour. Will be happy if someone explains it better. Faced the same issue and resolved it with this one.

IOS steals focus from first input element for some reason

working on a React/Material-UI based series of forms. The autofocus HTML property works as expected, but for some strange reason the page, upon load, is stealing focus away from the first text field, and applying it somewhere in the middle.
This is especially annoying since I have validation onBlur, which will throw up a little error message saying to the user that the first field needs to be filled out. How do I keep iOS Safari from stealing that focus?
I had a similar problem to this using TextField with multiline set to true (rendering a <textarea>). I'm not sure why, but I was able to narrow it down to a minHeight that I had set on the textareaStyle prop for TextField. My problem showed up on both iOS and Safari so I'm guessing it's got to do something with webkit. Removing the minHeight rule solved my issue of the focus being stolen.

resignFirstResponder() in Third-Party Keyboards

I have a third party keyboard that currently contains a UISearchBar(that is first responder on start) and the user is able to search for content (i.e. gifs) to be able to copy, paste, send to friends, etc.
In theory, after entering text in the bar and pressing search, the user should be able to enter text in the application's actual UITextView (i.e. the message field in the messages app) but for some reason this doesn't work and although typing works, nothing actually appears.
I have tried searchBar.resignFirstResponder(), self.becomeFirstResponder() and many combinations of .endEditing(true) to no avail.
I know it is possible to do this as apps like Giffy do it but I can't figure it out for the life of me.
Any help would be greatly appreciated.
Keyboard extensions with built-in search bars usually implement their search bar as a UILabel, adding custom text handling behavior that modifies the text property of the label based on user input.

UITextField Cursor and Keyboard Issue

My app was running fine on ios 8.4, but now after trying it on ios 9 beta, once the app is opened, the cursor on the UITextfield doesn't show up.
The keyboard doesn't come up. Shouldn't it come automatically?
The app works perfectly fine till ios8.4. Can some one help me out?
After one tap gesture on the UITextField, cursor doesn't show up at all.
Also, I tried checking the tintColor property as well as suggested by some users, but it is default blue.
Is there some specific change made in the way keyboard works on ios9?
A Situation - When I click on Login button, Alert message is displayed and then on pressing ok, the keyboard appears with a cursor but I can type only 1 character and suddenly the cursor and keyboard disappears. Then again, click on login, get the error message, cursor is available, type 1 character and cursor and keyboard disappears again.
Why is cursor on visible when tapped on a UITextField. This according to me must be a simple automatic thing. I have used resignFirstResponder and becomeFirstResponder too.
Anything to do with the Views here? For example, super view or something?
Thanks in advance!
Shrikant Kekane
The situation you have described is not happening when I tried the same.
The steps I followed:
Drag and drop one UITextField in Storyboard.
Give it required constraints.
Build & Run.
Keyboard and cursor both work perfectly in iOS9 simulator.

iPad text input and text selecting not working properly

This will be difficult to explain so I won't paste any code.
I'm implementing a wysiwyg editor on my site called wysihtml5 and there are several issues when selecting the textarea/editor with the iPad. On a desktop browser, all is fine, the text can be selected, edited, pasted etc. But on the iPad multpiple issues occur:
Can't tap anywhere in the text to move the cursor there
If I manually move the cursor, all of a sudden I can't type anything anymore
Tapping outside of the texteditor doesn't bring the keyboard down
Basically I'm just hoping there's someone who has had similiar experiences with iPad cursor not behaving correctly in text input fields and what possible solutions there might be. I'm stuck and have no idea how to debug this.
Did you use touch event? iOS has a bug: you can't input in editable iframe if you are listening(or had listened) any touch event(touchstart, touchmove...), I tested this bug occurs even you listen other elements but iframe itself. yes, it's a serious bug, you can check out:
wysihtml5 issues98

Resources