Donation bug 0/0

Kellett

Approved user
Joined
Mar 8, 2017
Messages
3
0/0 donation request bug

TinSoldier Any news about when this bug will be fixed? A couple of people in my alliance request and it says 0/0 for available troop spaces instead of, for example, 0/27 or 0/30. No one can donate to them. Other people can request normally- its just a couple people so far. They’ve tried restarting their games many times. One has tried leaving and rejoining the group. Doesnt fix it.

Any info would be appreciated. Cheers.
 

Enelessar

Approved user
Joined
Nov 10, 2017
Messages
14
Wow 😮 This trumps all the other bugs or after- bugs or aftermath- bugs I have heard here so far. Its like leaking guts syndrome.
 

TinSoldier

New member
Joined
Jun 4, 2017
Messages
1,568
We are working on fixing all of the residual parts of this chat bugs.
It currently looks like we will have a fix ready on Monday (5/14) at the earliest.

Again, I apologize for the delay.
 

No Angel

Approved user
Joined
May 1, 2017
Messages
1,386
I think it's fixed. At least for me (couldn't view chat messages), and a few team members (request says 0/0).
When it first happened to me few days ago (was after update) I couldn't view alliance chat neither request troops. I was using my wifi router with 3G connection. I was curious, if it was related to connection speed/mode. So I turned off my wifi then started using my mobile date with LTE connection. It surprisingly worked RIGHT AWAY, without restarting the game. So every time I wanted to request troops or talked to others in alliance, I turned off my wifi 😂. I made a conclusion that it had to be working better with LTE network rather than different connection type/speed. Just my own conclusion.
Then yesterday, when I used my wifi, alliance chat became normal again. Glad for that.

While for the 0/0 bug, some members who were facing that problem were advancing age atm, so I figured it was related to town center upgrade also.
They tried to request a few times, lasted for a while, maybe for a day or so, and it finally fixed, so I concluded that this issue was resolved.

Anyone still facing that issue?
 
Top