My theme is getting reset to default one each time I restart my device.
Hi,
Many days ago I started to face a problem with themes. Each time I restart my device the theme seems to be reset to default one and when I first use Swiftkey I get this message:
When I click on CHANGE button I see my usual theme (Forest) is still selected:
But in fact it's not. The only way I can make Forest theme active again is to select another one (usually Pulse Yellow) and then select Forest again. When done, Forest remains the active theme until I restart my device to face the same problem again.
Any idea?? This is getting very annoying now...
Thanks!
Bonjour,
J'ai le exactement le même problème. Merci à Swiftkey de nous donner la solution.
I have the same problem since a couple of weeks. I wrote an email to the help center, hoping to get some more information
Thanks Toni for laying out the problem perfectly. I am having the same exact problem. C'mon SwiftKey, can we get some help here? Like NOW!
Well, the problem somehow has been fixed after last update, even if there's no reference to it in the release notes. Thanks!
Anyway, I think some comment here from SwiftKey support stuff would have been very appreciate. Silence is never the best practice in terms of image. And this forum is full of silence...
Yours,
Toni
Hello,
It should be fixed in our beta 7.0.8.363, can you please try it and confirm?
Sorry for the late reply
Alpert
Thanks Albert but the fix I came up with a day earlier was to uninstall the SwiftKey app and then reinstall it without having also deleting the account because the account info and all your history and settings are kept in the cloud. Therefore once you reinstall the latest version to your device from your appropriate app store and sign in as you did originally everything fills back in and you can go ahead and choose your keyboard and it's locked in as before, sound as a pound. Hope this helps.
Bonjour,
Oui, la dernière mise à jour a solutionné le problème.
Dommage que nous n'ayons eu aucune information de Swiftkey, pas très sérieux.
Hi Alpert.
As I already said, the problem was fixed for me with latest regular update (version 7.0.7.28), so no need to try beta versions.
And thanks for your answer, it's alway better late than never ;)
Have a nice day.