Comments
-
Yeah that can happen if the time gets changed on the phone and doesn't correlate with your current location. I think reinstalling the app should do the trick!
-
The option to connect to Facebook or Kingdom enables you to save your game to server. If you don't, it will only gets stored locally on the device so if anything happens to it or you change to a new one, there is no back up to load.
-
What happens to the ingredients, do they get stuck at he bottom the left hand board or do they drop off?
-
You do it from the booster selection outside of a level, that's the only place where you can use the coins and not within a level.
-
Try following these steps Linda to get them synced again. - Open the game app and disconnect from Facebook. Close the app. -Next uninstall the Facebook app from your device. - Turn your device off and on. - Install Facebook, log in and find a game notification, select it. - This will either take you straight to the app or…
-
If you're connecting with Facebook and have the Facebook app on your phone you should follow these steps, it should reset the connection to FB from the game. - Delete the Facebook app. - Go to Settings, scroll down to Facebook, open and select where it says your name, then delete account (Ignore the disclaimer it is not…
-
It's a mixture of bad luck and the nature of it, the treasure chest always appear ahead of your current location on the map so for anyone sitting on level 1475 the challenge is unplayable.
-
You can, you can send individual requests to people instead of using the bulk send option. To be honest Facebook is a bit of a nightmare for playing games and keeping your friends that don't play... that's why I ended up with connecting with a Kingdom account instead personally.
-
An update was pushed out yesterday which fixed this problem, check in the store if you haven't installed it already. Should be good to go after that!
-
Have download the update that was released earlier today Mary? If not you should go into the store and double check as this update addressed this issue.
