Remember: EA designed SimCity BuildIt as a "live service" game. Errors like 1100.7 are usually the result of your phone and the server losing sync during a save operation. By following the authentication refresh steps above, you effectively re-introduce your device to the server.

Do not let a three-digit error code destroy a metropolis you have spent years building. Follow this guide, be methodical, and soon you will hear the sweet sound of your factories producing again.

If you are an avid mayor of a digital metropolis, few things are as frustrating as being locked out of your city. You tap the icon, watch the EA/Tracktwenty logo splash across the screen, and then—instead of the comforting hum of traffic and construction—you are met with a cold, unhelpful pop-up: Error Code 1100.7 .

Word count: ~1,450

In plain English: Your phone and the EA server are speaking different versions of the same language, or your local save file has a timestamp mismatch with the cloud save.

Before you uninstall your game or throw your tablet across the room, understand this: This article will dissect every possible cause—from corrupted caches to server-side conflicts—and provide step-by-step solutions that work on both iOS and Android devices. What Exactly is the 1100.7 Error? Unlike generic "connection failed" errors, the 1100.7 code is specific to SimCity BuildIt’s client-server authentication handshake. When you launch the game, your device sends a "handshake packet" to EA’s servers. Error 1100.7 occurs when the server receives that packet but finds it malformed, expired, or conflicting with a previously saved state.