Most Commonly Asked Questions about: Performance
The fastest way to get an answer to your question is to check and see if the issue you are having is answered in our common questions. All our FAQs have detailed information about the best solutions available.
Please report this to the Support Team by clicking the “Contact Support” button to the right. In your description please be sure to include:
- Your SwiftKey version which can be found in the ‘About SwiftKey’ of the Settings menu
- Your current Android OS version
- The make and model of your device
- Detailed steps as to what exactly you did / do to experience this crash
- The exact text of any error you see
If you feel that your predictions are poor, please see the steps below. Please not you should have Cloud with Backup & Sync enabled otherwise you will lose your language data.
- Open your device System Settings
- Tap App Manager (or similar)
- Find and tap ‘SwiftKey Keyboard’
- Tap ‘Clear cache and data’
- Open SwiftKey Keyboard and make sure that all of your settings are how you like them
This is often a problem with older phones or those with many high memory usage apps running. Try closing other large apps, restarting the keyboard, using only one language, disabling Flow, or as a last resort clearing your cache.
For more information, please read the full article.
Please make sure you update to the newest version of SwiftKey as versions 4.4 or 4.5 had bugs that were occasionally causing excess battery drain. If you are on the newest version of SwiftKey, there is a rare bug with Google Play Services that causes Location Services to drain battery while in the SwiftKey Store. Google should be releasing a bug fix to this soon.
This is a bug that we are currently working on. The newest release has put in place several bug fixes around this issue. However, it is not a retroactive fix, so you may need to retrain SwiftKey Keyboard.
- Long press the word in the prediction bar
- Select ‘do not predict again
- Tap on the correct lowercase version
SwiftKey has a feature that allows you to toggle a completed between Title Case, CAPS CASE, and lower case by tapping the shift key while the cursor is somewhere touching that word. Unfortunately this has caused an error that occasionally shows up with words with strange capitalization schemes such as 9GBish where user will not see the direct verbatim text in the candidate bar.
By clicking through this “shift” cycle, you should get to your desired outcome, even if it is not showing up initially in the candidate bar.
This is a rare occurrence that can almost always be resolved by closing the application you are typing in and re-opening. If the Flow Trail disappears, you should still be able to type normally using Flow or tapping without affecting your predictions until you are able to reset the messaging application.
We’re aware of this issue, and are really sorry for the inconvenience.
We’ve worked with Google to determine the cause of the issue. After researching this in depth, Google has told us this is a regression in the Android framework. They’ve also assured us that this will be resolved in a future update to the Android operating system.
If you are unable to answer your question through these articles you have two alternatives:
- You can take your question to the Support Community of SwiftKey veterans in the VIP Community. Often they provide the fastest and most creative solutions.
- You can contact our Support Team by clicking the “Contact Support” button and putting in all your pertinent information.