I'm creating a signup journey with phone, birthday, ssn, etc using the stepper widget. I'm using firebase for phone auth so on ios, it reads the message and there is a keyboard suggestion with the OTP code. However, the "From Messages - 12345" suggestion stays on the keyboard even after I've used it. It looks like it finally disappears after ~3-4 minutes but I need to hide/remove it right after the phone step. Initially I thought it might be because I'm using a stepper so it's technically one screen. I tried hiding and showing the keyboard to "refresh" the keyboard but the suggestion still shows on all my text fields.
I've tried the solutions here: https://github.com/flutter/flutter/issues/22828
They don't work for me.
enableSuggestions: false,
autocorrect: false
I can't use keyboardType: TextInputType.visiblePassword because my keyboard has to be numbers.
Related
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
I'm building a chat app using MessageKit, Firebase and InputBarAccessoryView pods.
I've found out that when I input a Memoji (aka sticker) in the textfield of the InputBar and press the "send" button, in the database the Memoji will be saved as "\n", which of course will be rendered as a blank bubble in the receiving user screen. The issue is exclusive to Memoji, regular emojis works fine.
Before sending, I already check if the user is trying to send an empty string, and if the case the message is not sent at all to the database, but I don't know how to check if a Memoji is being input.
Plus, in the textbar the Memoji is rendered awfully, see pic here, so the best solution would be cutting the problem at its roots and removing the option to input Memoji in the textfield or directly removing them from the keyboard.
I'm searching for a way to to remove Memoji from users keyboard, or to handle at best these issues, but i've found nothing googling.
Memojis work this way: when selected from the keyboard, they are pasted into the TextView.
So i just found a decent solution directly from the InputBar API:
messageInputBar.inputTextView.isImagePasteEnabled = false
This removes the possibility to paste images in the TextView, and alongside Memojis are removed from the keyboard.
Bit of a strange question: we are working on an iOS app made with a 3rd-party engine (Unity). We've encountered what appears to be a bug in the engine - randomly, when the soft keyboard is shown, a "Passwords" button appears at the top of the keyboard. Tapping this button brings up a list of websites that you've previously saved passwords for.
I've never seen this button in any other circumstance and have no idea what causes it to appear. What I'm looking for right now is information about this button - any API docs about it, what Objective-C / Swift code you'd normally use to show it, etc. I'm hoping this additional information will make it easier to find a workaround or at least file a bug report with Unity.
In iOS apps you get automatically this password autofill button on the top of the keyboard if you set the textContentType property of UITextField to any of these:
• username,
• password,
• newPassword,
• oneTimeCode
More about this you can read on this link: Enabling Password AutoFill on a Text Input View
Hope it helps.
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.
I'm development an app through titanium. When I was running it on actual iPad, I got a bug that keyboard cannot close if guided access was enabled.
Scenario:
Guided Access is on in settings
Focus on a TextField, keyboard shows up
Triple click on home button, start Guided Access. (With Password). Note, the keyboard is still up for textfield.
Click "Resume" button, return back to app.
Now, if you try to dismiss keyboard, it just stuck there. And keyboard no response until next TextField or TextArea.
And this always happens. I'm not sure if this is a bug from Titanium or iOS itself. I'm trying to replicate by native objective c code.
Does anyone have clue how to fix this?
Thanks
UPDATES:
I've tried to replicate by native SDK. Nothing happened. So I guess this is a bug only for Titanium.
Finally address the problem, when you open the number pad for guided access then go back to app, it will cause the textfield lose focus. So, if user tap/click the textField, then there will be no problem.
And there is another scenario: There are two window, A and B. B has a textField, and I've set it focus when it opened. In Window A, I triple click home button and open the number pad to enter password. Go back to app, open window B. Now since I've programmatically focus the textfield, so nobody click the textField. Now if you try to dismiss the keyboard without touch/click the textfield, you will see the same bug happened before. While if you click the textField, manually re-focus it, there will be no problem.