Marvel Jump In stuck on pack select screen
I am experiencing a bug that several other players have reported in the Marvel Jump In event. I picked my two packs and then the event kicked me to the home screen. Upon returning to the Jump In event screen I see 'Choose Packets' again, and when I click the button I am greeted with my previously selected first pack and no other packs or way to back up or resign the event. I am out 1000 gold and unable to progress or play the Marvel Jump In event now.
-
MiraFishy#05514
commented
got redirected here from my support ticket, they gave me my gold back but i still cant play the event.
its bs since we are missing out big time, jump in is the cheapest way to fill out a collection and the event is limited time only. they should compensate everyone affected by this issue with additional packs or gems. complain
-
Demon0taku#73022
commented
Same Issue. Both PC and Android. Log file attached.
-
segismundit#42418
commented
Same issue. In my experience restarting the game never sesolved it, no packs appearing, i had to close the game, wait a bit(an hour to be sure), reenter and select a sifferent second pack(same pack still generates the error).
that has resolved always the issue, it happened at least 4 times to me(i played a lot of marvel jumpstart im the late days)
-
peekaloo#83874
commented
I have the exact same bug. But when I log out and come back, it asked me to pick my second pack again. If I select the original second pack I chose, the bug remained. But this time I selected a different second pack and the game let me through.
-
CHT
commented
Same bug. If this helps, my first pack was Mayhem, and the second was Lethal.
The entry fee may be negligible, but I'm totally blocked from the Marvel Jump In now.
How can I finish the achievement like this? -
kilonova#35441
commented
same thing is happening to me. tried choosing a diff. pack with the first one already chosen and it will just go back to the main screen and then wont do anything on the jump in.
-
LunarT3mp3st#65913
commented
Same issue.
-
dsyuzon#41695
commented
Same issue. Added log file in case it helps.
-
Buckeye57#16492
commented
same issue