Welcome to the Candy Crush Saga Community
Do you have a question or need help with your game? Ask the Community.
I was playing Candy crush saga yesterday, on my kindle fire. it was fine. This morning it would not load. The Orange King splash screen comes up for about 20-30 seconds, then it closes and goes back to the carousel. I have followed the instructions. I have also uninstalled and reinstalled. Still the same. What else can I do?
I have the same problem. I got notified that Cady Crush had updated on May 28th & since then it will not load. Orange King screen for for a while & then back to kindle carousel.
I have tried the oprions below in various combinations:-
restarted the Kindle Fire HD8.9
force closed the app
cleared the cache
I haven't tried reinstalling yet as I note that I'm supposed to make sure that I have saved progress to facebook (not an option for me) or the Kingdom which I have no idea if that is happening. I got Candy Crush in October 2013 & can't remember that far back!
Any help gratefully received
I also have the same problem. Candy Crush Saga worked yesterday morning but in the afternoon it stopped working. The first orange screen shows for 20-30 sec and then crashes. I've cleaned out my cookies, reloaded and restarted multiple times and it still doesn't work
I don't actively save my progress when exiting the game. So unless that is something that is done automatically in the game by some setting or other it looks like I don't.
As my King account I'm not sure I have one. I know when I have issues with wi-fi connection then some info is not available in the game until I reconnect so there must be some knowledge of my game outside of my Kindle.
Sorry to be so vague but I do seem to remember having to login to King.com at some point but I can only find 2 emails from King.com (i'm a bit of an email hoarder!) & they are the terms of service & the Privacy policy from 2018 but when I tried just now to login to king.com (on my PC) using that email it wasn't recognised.
However having seen the previous posts with at least 4 of us having the same problem it seems there may be an issue with the latest update through Amazon.