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

Game becomes unresponsive on iOS after losing game #462

Closed
Marabyte opened this issue May 20, 2019 · 3 comments · Fixed by #463
Closed

Game becomes unresponsive on iOS after losing game #462

Marabyte opened this issue May 20, 2019 · 3 comments · Fixed by #463
Assignees

Comments

@Marabyte
Copy link

Marabyte commented May 20, 2019

Debug info
Version: 1.0.4
Motion: false
Supports WebGL: true
Feature Phone: no
Standalone Mode: no
Screen Width: 375px
Screen Height: 647px
DPR: 2
Device Memory:
Concurrency:
UA: Mozilla/5.0 (iPhone; CPU iPhone OS 12_2 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/12.1 Mobile/15E148 Safari/604.1

Describe the bug
After finishing a match the back button, “try again” and “main menu” become unresponsive. Scrolling the board/tiles still works though.

Closing the app and re-open it doesn’t restart the game. It stays on the same screen still unresponsive. The only solution I found was to restart the phone.

To Reproduce
Steps to reproduce the behaviour:
I haven’t been able to reproduce the issue accurately. But both times that happened was after losing a match.

@iamtherookie
Copy link

I just had the same issue as well. I thought it was my phone. I tried games on both safari and it saved as a web app.

@Mohamedzu
Copy link

It happens when Navigator.vibrate() method is called which is not supported in safari

[Error] Unhandled Promise Rejection: TypeError: navigator.vibrate is not a function. (In 'navigator.vibrate(a.vibrationLength)', 'navigator.vibrate' is undefined)
	componentDidUpdate (lazy-components-8bdb01a1.js:1:21988)
	T (proxx.app:86:7027)
	d (proxx.app:86:501)
	promiseReactionJob

#454

@jakearchibald
Copy link
Contributor

Thanks for catching this. We've deployed a fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants