devtrackers.gg
Hi all, thanks for the report. We have flagged this as a bug which can occur in very specific circumstances. Thank you and apologies for the inconvenience meanwhile.
Hi all, thanks for the report. We have flagged this as a bug which can occur in very specific circumstances. Thank you and apologies for the inconvenience meanwhile.
Hi all, thanks for the report. We have flagged this as a visual bug. As stated below as well, it has no impact on purchases. Thank you and apologies for the inconvenience.
Hi all, thanks for the report. We have flagged this as a bug that can occur in very specific circumstances. Apologies for the inconvenience meanwhile.
Have you tried reinstalling the game? It would probably fix the issue but if you are still encountering the same problem after reinstalling please send me a private message with your Ally Code, Device Model and OS. Thank you!
CongrAATulations!
Is there a phone number to contact customer support that works or a way to get them to call you since comprehension over email seems to be failing?
If you feel comfortable doing so, please DM your ally code to me and I can help escalate on Monday morning.
Are you still experiencing this error?
Please submit a ticket to customer service. Someone should be able to manually unlink your account via an internal tool.
Hotfix worked. Woke up this morning and was able to get in on both devices.
Seriously, thanks for the quick weekend fix. I really wasn't expecting a response that fast.
Woot! Happy to hear that the hotfix worked for you. Thanks so much for confirming! :-)
Thanks to everyone who provided information regarding this issue. We investigated and have a potential fix. We're working right now to deploy a hotfix to address this issue.
Hotfix should be fully rolled out by 12:01 AM PT on 6/23. If anyone is still hitting Error Code 3.0 issues on sign-in after that time, please direct message me.
Thanks to everyone who provided information regarding this issue. We investigated and have a potential fix. We're working right now to deploy a hotfix to address this issue.
If you feel comfortable doing so, please direct message your ally code to me and I can look into this further.
If you feel comfortable doing so, please direct message your ally code to me and I can look into this further.
Did anyone proceed to the attack mode? A few of us devs progressed into attack instead of review.
Sorry for any confusion my tongue-in-cheek title may have caused. I was trying to give mildly cheeky nod to that we’d found a small issue only a couple hours into the Exhibition.
When we first release new game modes, it’s customary to run an exhibition season where we work out any experiential or operational kinks that aren’t uncovered during internal or beta testing, ensure everything is stable as we scale from hundreds to many thousands of players, etc before we move over to prime time.
Thankfully this issue was pretty minor and only resulted in a quick client restart. Good luck this weekend and keep the feedback coming!