Stuck in Tutorial (Training Droid)
Product: Star Wars: Galaxy of Heroes
Platform:Android Phone
What type of device are you experiencing the issue with? Phone, Tablet, and Android VM
OS Version 7.0, 4.4, 6.x respectively.
Ally Code: (Find it here: http://bit.ly/AllyCode ) Unknown, unable to proceed through menu because of tutorial lockout.
What type of issue do you have? Gameplay
How often does the bug occur? Every time (100%)
Summarize your bug The unskippable tutorial has me locked in a loop. You're supposed to assign the training droid to the Jedi Consular, but the tutorial doesn't account for multiple training droids having been awarded. 1) Assign training droid. 2) Can't assign it because I have more than 1, so I have to choose the amount of droids to assign. 3) Can't tap/click on the right area because the tutorial will not let me.
Steps: How can we find the bug ourselves? Create account, quit in the middle of the tutorial, then come back after a few months and you're "gifted" multiple training droids. Now you can't get through the tutorial because you're not allowed to actually use the GUI that pops up.
Connection Type
Please select your region North America
Country USA
I've uninstalled and reinstalled about a dozen times, to no avail. I've gone through to level 10 on a guest account to attempt to merge accounts with my correct Google Play account, but it defaults back to the account stuck in the tutorial. I've tried it on multiple devices, with varying OS versions, and it's clearly an issue with the game itself. I'm not alone in this problem, but all other topic-starters have had their issues fixed via PM, which is not exactly helpful to others with the same issue.
@Downbylaw638 I did read your original post and the solution I suggested does work in terms of creating a whole new account. However, I did locate your account by the player name you provided and modified the amount of Training Droids you have in your inventory. Can you please login again and let us know if you are able to complete the tutorial now?
Thank you.PS: We've managed to reproduce the issue and flagged it as a bug.