July 2018
Product: Star Wars: Galaxy of Heroes
Platform:Android Phone
What type of device are you experiencing the issue with? All
OS Version All
Ally Code: (Find it here: http://bit.ly/AllyCode )
What type of issue do you have? Missing Rewards
How often does the bug occur? Every time (100%)
Summarize your bug Prestigious quest Fulcrum Tier 3 not giving credit for Infiltrate
Steps: How can we find the bug ourselves?
Connection Type
Please select your region
Country
I just completed (defeated) the Hoth Rebel Assault Phase 6 (slice 6) Rogue One mission and did not get credit for it in the Fulcrum tier 3 Prestigious quest like I should have.
I have had this quest active since quests were released and just completed the "built on hope" win 5 squad arena battles with only rebels last week.
@EA_HighCommand please help you are my only hope!
Solved! Go to Solution.
July 2018
July 2018
I had the same issue. I also reported a bug. Hopefully we get credit before the next TW starts as phase 4 requires 10 TW wins.
July 2018
Same issue
July 2018
Same issue, I was hoping it would pop up when the TB was complete but nothing happened.
July 2018 - last edited July 2018
Can we expect this to be resolved and receive credit for quest, get our rewards and move to stage 4/4?
July 2018
@EA_HighCommand So since you have tagged this as a bug now, can we expect some sort of response/fix to this issue anytime soon? Never seem to hear anything back
July 2018
July 2018
Hi @Bucknutz22 and thank you for the question.
As @GladOS-013 correctly stated, we report those to the studio but it is not our decision how it is prioritized and when a fix is ready to be deployed. Rest assured, that once it is in the system, we (aka the studio) won't forget about it.
July 2018
On the 7/11/2018 Content Update, it read as a Known Issue: "We are aware of an issue with Prestigious Quest Fulcrum Agent Tier 3 “Infiltrate” not completing. We are working to resolve this quickly and should have it corrected by the next update."
Nothing has been changed on that update page, has this bug been resolved?