I have SwiftKey selected as my default keyboard on my android phone. When I go into teams and chat the keyboard is the stock teams keyboard and does not behave like SwiftKey. Is there a way to use SwiftKey while using the teams android app? I can not find the option within the app.

This is gone on long enough. I correctly type No, and swiftkey will either correct this to Jo or KO. 

I have long-pressed Jo and asked it to never predict it again.

Checked data.swiftkey.com and it is NOT there. 

Have English, Spanish and Portuguese as my languages and in all three of them "no" is an extremely common word, and "Jo" means absolutely jack shit. I'm getting sick of this. Swiftkey didn't use to be this stupid before the Microsoft purchase. 

Samsung S10e

Version 7.8.5.6

Android 11, Samsung One UI 3.1

When I open the Google keep app I get a SwiftKey keyboard.

How can I close this keyboard? Only people using Samsung S5E need post, as every suggestion fails, and I'm hoping this might be peculiar to the S5e 

. bj. fe. w5u. eyg. rub. ruug. eeu. otr. xyrth. lhfuu

i would use the space bar when i need to, please microsoft

when you use voice to text button now on swiftkey it brings up voice inout  , close out messages and go back in and there is no keyboard it defaults back to  voice inout automatically.

then you have to hit the keyboard button at the bottom and change back to swiftkey keybord 

it used to be you  press the button   say your message and send it , then next time your in a message it would default back to swiftkey. keyboard to type.

but now when you hit the microphone icon   it stays on all the time for all messages.

Hi!

Just wondering does Swiftkey support Android 11's in-line password manager ?

First, I will clarify some things for those who may not know and for those who might assume that I am confusing spell-checker with keyboard input prediction.

Then I will:

Bring back a problem that has been called for attention many times and explain why it happens;

Explain why I think it matters and why previous suggested workarounds are sub-optimal;

Discuss Google’s (Gboard) chosen workaround;

Give my suggestion to fix the problem.

Definitions

Input prediction (IP) (Auto-complete and auto-correction) is a feature whose main purpose in software keyboards is to allow the user to type faster. The keyboard suggests words before you type them entirely and correct words where there are typos. By auto-correcting, the keyboard allows the user to type without painstaking care and precision, which allows for faster typing.

Spell-checking (SC) is (usually) a feature of word processors or system-wide input fields (MS Word, Android, and Google Chrome for desktop, each has its own spell-checker independent from software keyboards or any input method). Its main purpose is to alert and correct the user about the orthography of a given language.

The problem

People who use simultaneous multi-language input prediction – a feature present on SwiftKey (and Gboard also) – start seeing a red underling in all words of one of the languages.

The reason is that, while SwiftKey’s input prediction does have support for multiple languages simultaneously, the android’s system-wide spell-checker active in the user’s phone (usually AOSP’s or Google’s spell-checker) does not have.

Previous suggestions

Here it has been suggested that the user should disable the spell checker:

https://support.swiftkey.com/hc/en-us/community/posts/115002878149-Red-underline-Not-a-SK-problem-

Notably, this is also the approach used by Gboard (more on that latter), but I think this is far from the ideal because it forces the user to resort to input prediction (IP) as a form of spell-checking (SC). This is a problem because, as I said in the beginning, input-prediction is a feature focused on fast typing (as it should be) and not on orthography. To illustrate, imagine how a user uses IP as SC:

The user types the word and hopes that the keyboard will correct it automatically if it’s wrong. Except that, even when typing correctly, sometimes the first prediction (the middle one in SwiftKey) is not the desired one. And other times the prediction dictionary doesn’t have the desired word. For those reasons, the exact typed word is always shown as an option, typos and all (as it should be), and the keyboard memorizes anything the user decides to input (as it should be) either by typing space and accepting the middle prediction, or by selecting the desired word in the list.

The result is that the IP learns a lot of slangs, acronyms and jargon (as is should be), but also learns misspelled words. And the user has no way of knowing if the thing he/her has typed didn’t appear as the first (middle) prediction because it was wrong or because the neural network crystal ball simply got it wrong or because the word doesn’t exist in the IP dictionary. Also, sometimes the misspelling is so different from the intended word that the latter doesn’t appear in the prediction list, and sometimes the misspelling is even presented as the first (middle) prediction.

The clear solution to that in my opinion is to have a separate mechanism for checking orthography, the spell-checker, which has to support simultaneously multi-language input as well (chrome desktop browser has that). This is a second independent layer that runs after input prediction, and is not affected by the IP dictionary. And when the user decides to tap a word and include it in the SC dictionary it is a conscious deliberate decision.

How does Gboard deal with that

https://support.swiftkey.com/hc/en-us/community/posts/115002630445-Changing-the-language-doesn-t-change-the-system-spell-checker

Here it has been said that SwiftKey cannot control the spellchecker, and that Gboard doesn’t break in the same way because it has “advanced system privileges that SwiftKey cannot access”. I’m not an android programmer, but from the tests I have done, it seems to me that Gboard has the exact same level of system access that SwiftKey has with respect to spell-checking:

If my selected system-wide spell-checker is the AOSP one, it behaves in the exact same way with Gboard as it does with SwiftKey. The thing that Gboard does different is that, along with the keyboard, the app installs a spell-checking service as well. I’m using LineageOS, which doesn’t come with Gboard or Google’s spell-checker, only the AOSP ones. And when I install Gboard, Google’s SC appears as an option.

Now, Google’s solution is far from the best in my opinion. For what I tested, the ‘Google spell-checker’ (installed by Gboard) simply disables itself if it detects that Gboard is being used and uses only the system’s language when it detects other 3rd party keyboards (exactly like the AOSP one). And I already explained my problems with both solutions.

My suggestion

Simply put together a simple spell-checker with simultaneous multi-language support and ship it within the SwiftKey app. I think this would be simple to do, just copy the default dictionaries of the SwiftKey IP as a starting point, but it would not have to deal with predictions and other complex features that a software keyboard has to deal with. Again, copy the dictionaries, any word learned by the IP should not be automatically learned by the SC.

The simplest implementation would be to have one hash table for each language. If the user decides to use two languages simultaneously, a new empty language-agnostic hash table is created. That way, when the user includes a new word to de dictionary, it is included in the language-agnostic one to avoid guessing the language of the word. Then, spell-checking a word is simply to query the word on 3 hash tables.

Why am I suggesting this to you?

https://support.swiftkey.com/hc/en-us/community/posts/360038666231-How-to-Active-Spell-Checker-in-SwiftKey

Here it has been said that SC “was never a feature of SwiftKey itself”, and that it’s an Android problem.

Indeed, if only AOSP’s SC did support multiple languages simultaneously, this problem would be solved. But I use and prefer SwiftKey; AOSP’s keyboard still doesn’t have support for simultaneous multi-language input, suggesting that this support is also not in the horizon for AOSP spell-checker; and it’s more probable that Google’s engineers will fix this only in Google’s SC, in a way that works exclusively with Gboard (as it’s the case with the ‘auto-disable SC’ workaround).

And ultimately this is a problem that (to me at least) seems extremely simple to solve and is hurting your product.

Here are some treads complaining of SC-related problems that, while not necessarily being all related to multi-language support, could benefit from a simple Spell Checker shipped inside the SwiftKey app.

https://support.swiftkey.com/hc/en-us/community/posts/115002905745-Multilingual-keyboard-underlines-all-English-as-incorrect-Spell-Checker-

https://support.swiftkey.com/hc/en-us/community/posts/360057381832-Red-underline

https://support.swiftkey.com/hc/en-us/community/posts/360041911952-Swiftkey-red-underline-is-gone-

https://support.swiftkey.com/hc/en-us/community/posts/360054924171-Red-line-under-text

https://support.swiftkey.com/hc/en-us/community/posts/115004508429--Duplicate-Android-Showing-red-underlines-for-all-words-in-second-language

https://support.swiftkey.com/hc/en-us/community/posts/360071921211-Swiftkey-underline-not-showing

https://support.swiftkey.com/hc/en-us/community/posts/115000617369-Reduced-English-suggestions-for-incorrect-spellings

https://support.swiftkey.com/hc/en-us/community/posts/360043539472-Red-line-under-spelling-errors-with-SwiftKey-

https://support.swiftkey.com/hc/en-us/community/posts/115000528649-Spell-Check-with-SwiftKey-has-Red-underlined-text

P.S.:

I’m conscious that I might be wrong about a number of things: There could be another workaround that solves the problem in a satisfactory way; There could be a barrier to install system-wide spell-checkers on android; Maybe spell-checking is harder than I think, even without grammar-checking or prediction; etc.

In that case it would be nice if someone could explain the situation in a more in-depth way.

Hello,
I just upgraded from an Android Smartphone to an iPhone SE 2020 iOS 12, but I cannot configure my Swiftkey keyboard to display the special characters above each alphabetical letter like I did on Android. .

I know that special characters are also accessible by pressing the "123" key then the "+ = #" key if I want to use the underscore "_" for example but it's really not practical, whereas on my Android Swiftkey keyboard, I just have to stay and press the "W" key to make the underscore "_"!

Can you help me configure my Swiftkey keyboard on my iPhone SE 2020 iOS 12 as on my Android please.
I'm placing a screenshot of my Android Swiftkey keyboard where the special characters above the letters I want to appear on my iPhone Swiftkey keyboard are outlined in red.
Thank you.

Hi,

My keyboard has started to show up blank, see screenshot below. If I rotate to landscape mode it seems to work though. Any ideas on what to do?

Best regards,
  Tobias.

Hello!

I've always used the Samsung keyboard before, but it lagged a lot on my new phone, so I was told to try another keyboard. Swiftkey has solved my lagging problem, or at least I don't notice it as much, but instead I find that I'd like to customize my backspace button. When I hold down the key, it deletes entire words instead of just letters, which really gets on my nerves when I make a typo in longer words (I type in Finnish too). Additionally, I'd really like to rearrange the "symbols" page (the one that pops up when you press the 123 button), though I suppose I'll grow used to the new order of keys in time if rearranging them isn't possible. But is there a way to change settings for the backspace key?

Thank you!

Hi,
I have data synced with one account, I have changed my primary email address and want to have same data that was backed up/synced with the previous account on the new account. I don't see any option to do that, is there anyway that I maybe missing?

Can someone explain why words that I remove from the dictionary keep coming back automatically after a few minutes or hours?

For example, I am trying to remove the all caps word OK, because no one spells it like that anymore and I personally dislike it. 

Instead, I have the word Ok or ok in my dictionary. 

However, it keeps coming back every time and always defaults back to the obnoxious OK.

How can I stop it from coming back please. I've been trying to get rid of it for months now. Never used to be a problem in my previous account. 

The predictions bar on the bottom is just annoying and not useful. I've gone through the settings a few times but thus far have been unable to figure out how to hide it completely. Is that not an option or am I just a big dummy and keep missing the setting?https://imgur.com/a/FFKC1Kh  https://gbapps.org/fmwhatsapp-apk/

• open swift key support link
•  activate sign in button > sign up 
• Select google link and hit enter
• enter the id ...

One-handed mode on Stable SwiftKey screenshot: https://i.imgur.com/7vpl3WO.jpg  (in ONE-HANDED mode on this screenshot - Toolbar looks nice, contains at least SIX tool icons (!) and you can slide left<>right for other tools easily). SwiftKey version is 7.4.6.6 screenshot About screen https://i.imgur.com/GnwYzfe.png 

Now lets look on Swiftkey BETA from PlayStore last update January 16, 2020 with ABSOLUTELY NEW (very bad!) TOOLBAR in One-handed mode screenshot: https://i.imgur.com/eG6vqAU.jpg  (in ONE-HANDED mode on this screenshot - Toolbar looks terrible, all icons are hide, and in this mode, you can not add more than TWO tools, are u seriously?) If you change layout to Full screen mode you see more toolbar icons, screenshot: https://i.imgur.com/G6E1TtE.jpg  SK Beta 7.4.7.6 About screenshot https://i.imgur.com/WORbAJB.png 

The question is, your developers are tested at least something and any plans to fix? )) I see no one reported about this. I hope this non-scrollable, non-usable New toolbar implementation leave as a joke or just experiment... Because in stable SwiftKey app you can easily slide ALL enabled TOOLS in toolbar and in One-handed mode you see the same tools icons as in full screen mode.

In Beta now - you need to make extra taps on three point menu. And potentially I DO NOT WANT THIS (NEW) TOOLBAR in stable SK in future.

Hi guys,  I just did a software update on my Samsung Galaxy S10 and since then when I use the long press on the period and / or enter keys to access exclamations and emojis, I need to press on the small symbol above the key instead of long pressing anywhere on the key like before.  Please fix as it is very annoying

I am using Samsung Galaxy S6 with Android 7.0, and here is the thing:

• When I use Swiftkey, the red underline is missing.

• When I switch back to Samsung keyboard, the red underline is working again!

So, what is the problem? I remember that red underline is a spell checker feature included in the core Android OS to mark the misspelled words, and previously it was working with Swiftkey.

Can anyone assist me, or if you are a Swiftkey user on Android please tell me if you got the red underline or not?