-
-
Notifications
You must be signed in to change notification settings - Fork 70
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
Inox Bodyguard: Freeze on iOS #564
Comments
Update: just adding the Inox Bodyguard monster to an empty game triggers this behavior. I changed the issue title accordingly. |
Can you send me a data dump via email to [email protected] please? I cannot reproduce in a quick test, might be related to some other circumstances, so will be easier to investigate with your exact state. |
I have reproduce the issue on Gloomhaven-secretariat.de with game code „github-issue-564“. I cleared all Website data and reset all data in the Data Management menu. Trying to show the ability card lets the game freeze. |
This is all working fine for me. So must be a client issue. Do you have access to a non-Apple device to check? Or if you have the issue on mac, can you open developer tools (F12 or something else, don't have Mac here) and see if there is an error in the console view. |
Just had a this issue occur to our party during mission 4b of Frosthaven. all Apple devices were not able to interact with the menus or buttons, but could see card draws. Android and Desktop was unaffected. |
Describe the bug
Trying to view the ability cards of the boss in scenario 49 of Crimson Scales results in an unresponsive state I can’t recover from. The main window works, but any menu won’t open.
On the desktop in Safari or Chrome this doesn’t happen.
Game Enviroment
Latest version used: 0.96.0
Crimson Scales, scenario 49, section 55A
Tested on iOS 17.4.1 on iPads and iPhones, and Safari on a Mac.
To Reproduce
Expected behavior
Unexpected to see the list of abilities of the boss
Gloomhaven Secretariat Version
0.96.0
Used Browser
Safari
OS
iOS 17.4.1
Additional
No response
The text was updated successfully, but these errors were encountered: