View Full Version : Have to restart app in order to see what was raided

08-23-2013, 09:53 PM
If I'm raided while playing and I eventually go back to my base, everything looks normal. I can't see what was raided, even though the news feed is telling me I was raided and lost.

I have to close down the game and start it up again in order to see what was raided. Not a real biggie, but a time waster.

Actually, after seeing the news appear, it seems like I have to first go back to my base before exiting in order to see what was raided when I fire it up again. If I don't, when I fire it up, I'm at my base but everything is still shown as not raided. So I have to restart again.

It would be nice if this were fixed.

I'm running the 3.8.0 build on iOS.

08-24-2013, 12:35 AM
Tell me about it. Have to close and reopen every 5 mins to keep resettin my buildings. Cant take the risk of not doing it as my boost buildings may be hit! This is beyond a joke. Im on android altho dont get me wrong as very recently alot has been fixed but this very very annoying

08-24-2013, 12:45 AM
same here on my LLP, could depends on the mobile that is running the game though on my normal phone i hardly have problems..

08-24-2013, 06:59 AM
Same for me on iOS

08-24-2013, 08:25 AM
I thought i was losing it for a sec, but i see im not the only one with this problem!

08-24-2013, 09:28 AM
My game has always been like this. I assumed it was a feature and not a bug.

08-24-2013, 09:33 AM
Same here. I'm assuming my outdated iPhone 4 is the problem. It's running slow anyway.

08-26-2013, 03:34 AM
Normally if I go to an area on the map and return back to the base I am able to see it

08-26-2013, 04:23 AM
This has always been the case since I started playing

08-26-2013, 06:19 AM
I have an iphone 4 as well, and even the news feed pop up is slow. I typically find out someone raided my boost buildings when I start losing raids.

Agent Orange
08-26-2013, 06:23 AM
Always been that way, if your newsfeed shows a raid restart.

08-26-2013, 06:02 PM
Hey guys,

Our team of engineers are currently investigating this issue.

Please contact our support team and we will gladly assist you with this matter.

We do apologize for the inconvenience.