Microsoft SwiftKey Android Support Forums

I have an issue when i enter an email address or URLs. swiftkey adds space after the dot. i have to then manually erase that space to keep entering the email address or URL. But now when i turn off the "Auto Space" i have another problem. Normally swiftkey always adds a space after a word which is fine. But now after turning of Aut Space off, when i enter a period, the space after the word still remains. so the space is not deleted automatically. This works only when Auto Space feature on. This is a bit inconsistent behaviour. Could this be fixed?

Since years I have this issue. Everytime i swipe to write the word "already", almost always swiftkey enters it as "ashtray". The accuracy is increased if i do the swipe very slowly and going very carefully over the letters. Is there a way to change this so the word already is predicted instead?

This happens with both the Released version and beta version. I use beta, and it is version 8.10.28.4. This only happens when you are in Book mode, aka two screens.

When you have the keyboard open, and you then open settings. This is what happens.

Settings opens on the opposite screen

If you attempt to swipe the settings window up, so that you can next swipe it off the screen to close, this will not work. The Settings window will remain whatever size it was left, you can interact with it, and the screen behind. But you must turn the screens off, wait a few seconds then turn back on to be able to remove the settings application. Sometimes, SurfaceQuickStep will stop responding.

So Microsoft did something really great: they allowed certain apps like Bitwarden to insert text into the keyboard. (See my previous post about SwiftKey). Bitwarden now inserts my randomly generated passwords into login forms, which is amazing. I only have to select the Bitwarden logo under the text prediction menu in SwiftKey and voila. The same applies to To-Do: just select the To-Do logo in the prediction menu and you can choose which task to insert. But one thing that I noticed is that the widget disappears after you have pressed the widget logo and inserted a string of text. This is not a problem in general, but if you have selected the wrong item from a widget (i.e. the wrong password from Bitwarden or the wrong To-Do task) and then go back to delete the pasted text data from the login form, you then will not get to see the widget pop up in the prediction menu. It does not appear a second time or ever. Even if the field is empty again. So you spilled your first chance. It has disappeared, even if you need it a second time. That's why I would like to suggest a new feature for widgets. Situation: The user takes the cursor off the text field (outside the form) to scroll down or click somewhere else and returns to the form again. They then click/tap inside the same text field again. (Maybe to add something more or re-enter a different text string). Suggestion: Show the widget again. Make the widget active in the prediction field if the cursor dissappears from the field (field is inactive so to speak) but then reappears on the same field (field is active now). What SwiftKey does right now: it only gives you the option to insert text from a widget like To Do or Bitwarden the first time. So even if you delete the whole entry in the form field, press outside of the field and then back inside, it does not bring up the insertion option from To-Do or Bitwarden. Why not let SwiftKey behave the same way every time the user enters or activates a text field?

So instead of having to reload the page so SwiftKey reloads its Bitwarden/To Do widgets in the prediction menu: make SwiftKey even smarter.

Hi, I think the night mode in the regular adaptive theme is not dark enough for me at least so... could you please

implement a high contrast adaptive theme (both with and without symbols) 

and/or

a way to set which theme you want for your phone in light mode and which you want for dark mode

tysm have a nice day whoever reads this :-) :3

Hi, I noticed this problem: sometimes when using the numeric keypad, when clicking on Backspace , in event onKeyDown, the key property has a non-correct value, and that's where Undefined comes in. This happens when there is a value in the input field, and if you make several clicks in a row, then the key field will have the correct value for 3-4 clicks

I saw someone else half address this, but whenever I try to add a semicolon after using flow input I get a space been the last word and the punctuation. If I want to use a semicolon or make my own made-up-phrase, I either have to backspace the last letter of what I've swiped (flowed) so it knows to look at what comes next as individual characters, or use the arrow keys to back up after hitting that semicolon and backspace spaces. Same applies to hyphenated words or series of words, but there's no reason to have the semicolon/colon/hyphen or dash not but the end of the preceding word. Particularly with the semicolon. I tend to like my punctuation as a way to fragment what would be a run on sentence and other areas where it would be appropriate but SwiftKey wants there to be space on either side of the ";" character or when using hyphenations. It should always hug the word to the left like a comma would; this range is same idea applies to full-on commas as well: it wants to have a space on either side instead of jumping back to the end of the last word like typing a period would. Why not give some (slightly) more obscure punctuation and symbols the period and comma treatment where after flowing a word it auto-spaces, but if a period, comma, or second space is input next that keyboard will smartly insert the formatting and punctuation before the auto-space between words.

Another hiccup I have that's always a fight is, for example, I want to list a file extension, SwiftKey will fight me to the pain several times in a row to not have it try to reformat that section to a URL.

It's to the point that I will flow a word, [backspace], [backspace], retype last letter of word and then long-pressing the "n" key for my semicolon to be in the proper place.

Side note:if the keyboard has to autocorrect the second half of a hyphenated word or expression it will add a space between the hyphen and the word it fixed looking like "blahblib- blahblah", assuming it had to fix my 'blahblah' for me, when the goal was "blahblib-blahblah".

SwiftKey is still hands down the most robust, well-rounded keyboard and I want you guys to continue to dig in your heels, keep pushing the envelope, and retain that innovation and magic autocorrect advantage without it getting too bogged down and keep it first time user friendly!

Keep up the stellar work guys!
-Ty

Also if you wanted to add gravy it'd be nice to have a way to flow on a larger screen (5.5" on my Pixel XL) when I'm manipulating the phone entirely with one hand without totally scrunching up the keyboard with the one-handed layout.

Al estar jugando al (pugb)
e por supuesto utilizo este teclado por defecto en mi dispositivo... El teclado horizontal no es correcto, queda más pequeño que la medida de la pantalla y quedan afuera algunas letras como la letra L / P porfavor espero que puedan solucionarlo pronto porque de verdad es una molestia

I have always found SwiftKey's autospacing aggravating, especially when typing IP addresses and URLs. That is why I have turned off autospacing. However, SwiftKey still puts spaces in between autocompleted words and punctuation, which is equally aggravating. Since Flow basically utilizes autocomplete, it makes this a constant and pervasive problem. 

SwiftKey should automatically remove trailing spaced on autocomplete and Flow completed words when punctuation is added or give users the option to turn off autospacing for autocomplete/Flow as well.

I have just spent 2 hours trying to debug why my relative's new wifi password which I set wasn't working, and it was because I had added a punctuation character at the end of the password and swiftkey added a space.

Is there a setting or workaround to do this? If not, please disable this when filling in a password field.