Please change nickel dark back to how it was. That look was why I used SwiftKey. I've been using SwiftKey for years, back when it was a paid app on Android, and I always used that theme. I'm very disappointed and would like my theme back.

Hi,

I've been trying to save all my swiftkey data from my old S6 to new S8 and it logs into my google account without any issues, it says it is syncing, but the data does not transfer from my old phone to the new one.

I've got quite a lot of swiftkey data from maybe 2 years of useage, so I'd like to sync it if possible.  Can this be done?  I followed your guide below, but this does not work for me, the new phone still has no predicted words, no words completed, no words flowed etc after syncing.  

My google account is set to sync app data if that makes a difference?

Can anyone guide me in the right direction please?

Thanks :)

https://support.swiftkey.com/hc/en-us/articles/201590701-Why-are-my-predictions-not-working-with-SwiftKey-Keyboard-for-Android-

Android 7.0 galaxy 7 edge t-mobile.

Version 6.5.7.22

Android 7.1.1

Google Pixel XL

When trying to type anything it intermittently crashes with the message below:

"SwiftKey Keyboard has stopped"

Hello, just the title said...
I have some questions,
How to disable fullscreen mode while my phone in landscape mode..

I asked the same question in SwiftKey feedback @playstore but no response yet..

I hope I can get the answers here..

One more thing, I just updated the app from playstore, and I get something (bug maybe) while I write this question, I just get something strange..

Everytime I write letter "i" the AI will convert to capital "I"
That's normal, but in my case the letter "i" is concatenated with "I" and I got "iI". That's strange..

And everytime I try to delete the "iI" to manually capitalize it, the capital "I" shows up from nowhere to the next of cursor location.

And it happened not only for the "i" letter but almost of all words that uses autocorrect function.

I hope you can understand what I mean.
Sorry for my bad English..

Hi. I'm giving SwiftKey a very thorough beta test, and want to provide my feedback.

Literally one thing is driving me nuts, and that is the inability to map the character we desire into each key's long-presses. I see people all over complaining non-stop about where keys are positioned, and yet SwiftKey promotes itself as highly customizable with a target audience of those who are transitioning from default OS keyboard configurations, and have often trained themselves to use those configurations. I don't know about you, but I'm a tech guru and it takes "many months" of continuous work to remap my brain on the position of where the special characters are located.

I believe there should be, first of all, Presets on what Samsung keyboard, Android keyboard, and all the other default OS keyboards have mapped for long-presses. SwiftKey can choose to keep their configuration in their preset and even make that the default configuration, but I'm here to say that the absence of this feature is one of the largest reasons people do not want to transition to SwiftKey.

Second, there needs to be the ability to map long-presses to whatever characters we desire. More prudently, the ability to map even the MAIN keys to what we desire. Imagine no more disgruntled hate speeches on why "this or that is not positioned there"

Everyone cannot agree on the same configuration. Please consider this in your future updates.

Cordially yours,

Matt Winans

When I want to correct something in the middle of a word I place the cursor on the spot (for example if I forgot an 'a' somewhere).

I then get a prediction, and when I press spacebar, only the part before the cursor is getting replaced. Not the part behind the cursor.

I find that really annoying. Samsung Keyboard replaces the whole word in that case. So I can type on.

Now I need to manually erase the part that is being left behind the cursor.

Is there a way to configure it the way Samsung keyboard handles it?

Hi I'm just wondering if there's a way to make the flow line a bit smaller when typing with the flow.

Want to help make SwiftKey for iOS better by testing the latest builds and features?

Follow this link to sign up!!

There is no code, and never has been. If you are getting asked for a code, kill TestFlight or try signing out and signing back in and then click the link above again. 

Best,

Ryan, SwiftKey Community Manager

Android - 7.1.1 - Nexus 5x
Swiftkey - 6.5.5.30

Issue description:
Long pressing/holding delete or swiping to delete will only delete 1 letter/digit at a time within wechat. This is only happening within the wechat application, and no where else.

Information regarding the issue:
There is already a post here with all relevant information:
https://vip.swiftkey.com/index.php?/topic/17156-wechat-long-press-backspace-doesnt-delete-whole-word-in-english-needs-more-info/

Short version is that, in order to fix a minor bug where users had to click 4 times to delete an emoji, this new issue was introduced. This new issue is far worse than the bug they were fixing...

Despite this being a 'known issue' it still hasn't been addressed in any of the recent updates. 

Can this please get fixed, I just got a new nexus 5x and am experiencing this problem, I don't want to have to install an old version of swiftkey so that I can type/delete properly in wechat (which I use all the time).

Cheers,

Hi guys!

Thought about using SwiftKey as my regular keyboard after the new flow update. But there are still some details I have problems with:

- spaces before or after using a hyphen and colon
- quick reply limitations on the lockscreen (I know, never gonna happen)

Best regards

Hello!

Since about two months ago, I keep missing the spacebar with my right thumb and hitting. The full stop key instead.

Hey I had an idea for your keyboard.

A custom emoji tab where we can add a select number of our favorite emoji for quick selection. SwiftKey is the top of the crop and this feature would enhance our typing capabilities even more. Thanks!

New poster. I hope this is in the correct place. Mods please advise if necessary :)

after the recent update , auto spacing prediction is not working, I have to manually press space button to get the next predicted word. which makes typing slow. and it is really embarrassing.
please bring back the old settings and my keypad freezing frequently.

I'm a beta tester.
You've recently made a change that that reduced the typing efficiency. In the past ,while typing a word, it automatically predicted the next word and entered an automatic space. In order to change the current word, i had to hit the backspace. Now, the keyboard gives me automatic suggestions for the current word and I have to hit the spacebar to get the next suggestion. BTW, it also puts automatically 2 spaces between the words. In addition, It makes the automatic quick period functionality redundant.

I've noticed that my keyboard no longer inserts a space after the word I type using the flow method. It's quite frankly obnoxious since I use a combination of flow and prediction bar; every time I want to place punctuation, I have to type the character, see that there's now a space between the character and the word, then backspace both and retype the character. In addition, the prediction bar is now useless since it no longer predicts, only shows me the word I just typed. I have been through the meager settings to try and fix this, but to no avail.

Hello,

I'm using SwiftKey v6.5.3.35 on a Xiaomi Mi5s with MIUI 8.2.2.0 Global Stable on top of Android 6.0.1. I'm using it with the default font. I also had this issue with various phones and roms like Cyanogenmod, Touchwiz, etc.

This is a message (marked in blue) which I typed in Sinhala using Swiftkey

And this is the message which my friend got (iPhone 7 with iOS 10)

Some letters have errors in iOS. I saw this problem in other iOS versions as well. No matter what Swiftkey version, Android version or iOS version this problem remains with SInhala language.

When I typed the same message with Google Keyboard and Helakuru (another 3rd party keyboard specially for Sinhala typing) it was perfect. 

I think the problem is with the typing method of Swiftkey. Both other keyboards use a different method. Hope you guys can fix this it would be great.

Thanks

The number pad two 4s and two 5s can I upload a screen shot? I have an s7 edge android 6

Hi. SwiftKey was updated today and the way typing and prediction works has changed! Before, I'd swipe a word and it would insert the word and the prediction bar would show suggestions for THE NEXT word. Now, I swipe a word and it gives suggestions for the current word. I much preferred the old way. Any way to go back to the old method??

I used this very usefully on Android, but I could not use Korean after I switched to iPhone.

Why do you support Korean on Android and not on iPhone?

Please please support Korean on iPhone.

While using swiftKey, I sometimes get a very strange auto suggetion, that predicts "davidstockmanscontracorner.com" (see in picture).

I dont know this site nor have i ever visited it before.

I have noticed this problem before, then performed a complete factory reset of the phone but i still get this suggestion which feels very strange (no backup form google used either).

Google did not really provide a solution and it also does not seem like a prominent problem.

What is wrong here ?

For some stupid reason if you try to change the things you're typing via hitting a prediction, like I type thrfe but meant three and hit three in the prediction bar to replace thrfe, it will leave the word thrfe's letters (any letters to the right of the cursor) leftover. So "three" becomes "three rfe". Um what sense does it make to leave letters of a word I want to REPLACE, as in get rid of these word, why would I want any of its letters to remain when I'm trying to get rid of it? Clearly I want to replace the entire word! Why would I ever in 9 million years need to leave ANY letters of a word I'm REPLACING? The chances are 0.00001%! Thrfe becomes three e. I will never need that e, ever. I use swipe typing so that e will get in the way. Swipe typing means I don't type 1 letter at a time, the entire word I swipe gets inputted all at once so that e will never be able to be used. I hate how stupid a rule you guys made to not let us put the cursor in the middle or beginning of the word, it can only go at the very end. Otherwise you'll have a bunch of unnecessary letters stamped in the middle of your sentences. What the heck sense does that make?

Please let us pit the cursor anywhere on the word to be able to use the prediction bar and change the word. Do you have any idea how hard it is to move a cursor to an exact spot (end of word) on a tiny phone? It's so hard that I have to use a keyboard with arrows to move cursors bc touchscreen cursor movement slows you down running it back and firth until it finely lands right where you need it, like using a mouse on super high suited is impossible to land it somewhere precise. I don't care what your reason is, maybe you did this cursor-at-end-of-word system for another feature to work, but that other feature is not nearly as important as this. Your other feature is causing huge probs leaving mismatched letters randomly in sentences. Everyone knows you don't implement a system if it's going to cause malfunctioning somewhere else. This is a malfunction, you can't ask people to place it at the end & suddenly the malfunction stops, no. The cursor goes anywhere in the word to replace that word and that is how all prediction typing works, especially since it's hard to move cursors precisely on phones.Please fix this asap, thanks.

As a user, I would like to be able to use SwiftKey Keyboard to scan a barcode (QR-Code). By clicking a simple button that opens the camera and ready to scan a QR-code.
I think everyone wants to use this essential feature.

SwiftKey does not automatically turn off the capitalization on HTML input tags which feature autocapitalize=off. That is very annoying, many web apps use this to prevent unwanted automatic capitalization on certain inputs. SwiftKey ignores this.

See https://developers.google.com/web/updates/2015/04/autocapitalize for details.