Yes it did
Awesome, glad to hear that!
Did a restart fix it for you? If not, PM me your ally code, with that I can have a look. Thanks!
Will it be added to the Trello bug tracker anytime soon? I would like to follow the status on it as it progresses towards a solution.
FYI: Not every bug is being added to the Trello bug tracker. Rest assured that we've pushed the priority because of the impact and that the team is already looking into it.
Thank you. I checked Trello and it was not listed with a status. The ticket response I got made it sound like it wasn't being explored
No worries, that's what I am here for =) Glad we clarified it.
We have already flagged this as a bug.
Hi all,
We have flagged this for review now.
That did work. Thanks! I was hesitant to try that since I’ve had other games delete my data, but I had no issues once I re-downloaded it
Glad to hear and good to have you back!
Hi,
This can have several reasons and is one of the more generic error codes. Can you try to reinstall as a first step, please? Make sure you have a strong and stable internet connection when doing so.
It has nothing to do with SWGoH, so I would strongly recommend denying access.
Have you checked your in-game sound settings as well?
PM me your ally-code and the date and time this happened, so I can have a look.
Did you have either of those toons in leader rolls? I have no clue why it seems to work for some people (folks in my guild have reported no problems), but not others?
Yeah, I was running Maul lead.
The shard drop chance is always the same and doesn't change at all.
Brothers in Arms requires win a “GA battle with team containing Darth Maul and Savage Opress.” And yes, I’ve restart the game several times.
Weird....I just completed that feat without any issue.
We have already flagged this for further investigation.
Did you already try to restart the game? What feat are you referring to exactly?
We have already flagged this as a bug.
Did you get a chance to take a look for me?
You should be sorted now.
We are aware of this rare issue and have flagged it as a bug already.
We are working with Apple to get this resolved as soon as possible. It is an issue with the Apple AppStore.