You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
The text was updated successfully, but these errors were encountered: