Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RESTART/OK button does not resume the adversary chain or fortress challenge #23

Open
knowoptions opened this issue Sep 28, 2021 · 0 comments

Comments

@knowoptions
Copy link
Contributor

@knowoptions knowoptions commented Sep 28, 2021

Describe the bug

When encountering a bug during an adversary chain or fortress challenge, the error popup requesting you to RESTART (adversary) or asking you to check your connection and click OK (fortress challenge) upon restart do not resume the chain or challenge you were kicked out of.

Instead, if you force close/kill the game and ignore the RESTART or OK button, the adversary chain or challenge can be resumed.

To Reproduce
Steps to reproduce the behavior:

  1. Recreate #6 or another error against adversaries or in a challenge
  2. Click RESTART / OK to the error popup
  3. Game restarts
  4. Most times, you're brought to the map and the adversary / challenge is lost.

Expected behavior
The game should restart and the adversary or challenge you were in should be resumed.

Screenshots

Example of the the potion bug #6 causing the RESTART button:

image0

If you ignore this RESTART button and force kill/close the app and restart, you are prompted to resume:
image1

For challenges, this is one of the errors that also can be resumed if you force kill/close the app and restart INSTEAD of clicking the OK button:
image2

The RESTART/OK buttons should resume the adversary/challenge just like force killing/closing the app does.

Versions

  • App: 2.18.1
  • Device: iPhone11
  • OS: iOS 14.8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants