At the very beginning of any rapid game against an opponent, I am unable to make the first move with either color; the game start timer runs out, and the server terminates the match. The F12 console shows the following error:
/HlAIj6b7Xqiw - Uncaught TypeError: Cannot read properties of undefined (reading 'sanLongCastling') - (https://lichess1.org/assets/compiled/lib.QQFN6VMJ.js:1:2212)
TypeError: Cannot read properties of undefined (reading 'sanLongCastling')
at L (lib.QQFN6VMJ.js:1:2212)
at $ (lib.QQFN6VMJ.js:1:2317)
at I.sendMove (round.DSXARN7G.js:1:26236)
at I.onUserMove (round.DSXARN7G.js:1:22181)
at lib.HXRBDJNZ.js:1:2870
lib.QQFN6VMJ.js:1 Uncaught TypeError: Cannot read properties of undefined (reading 'sanLongCastling')
at L (lib.QQFN6VMJ.js:1:2212)
at $ (lib.QQFN6VMJ.js:1:2317)
at I.sendMove (round.DSXARN7G.js:1:26236)
at I.onUserMove (round.DSXARN7G.js:1:22181)
at lib.HXRBDJNZ.js:1:2870
At the very beginning of any rapid game against an opponent, I am unable to make the first move with either color; the game start timer runs out, and the server terminates the match. The F12 console shows the following error:
/HlAIj6b7Xqiw - Uncaught TypeError: Cannot read properties of undefined (reading 'sanLongCastling') - (https://lichess1.org/assets/compiled/lib.QQFN6VMJ.js:1:2212)
TypeError: Cannot read properties of undefined (reading 'sanLongCastling')
at L (lib.QQFN6VMJ.js:1:2212)
at $ (lib.QQFN6VMJ.js:1:2317)
at I.sendMove (round.DSXARN7G.js:1:26236)
at I.onUserMove (round.DSXARN7G.js:1:22181)
at lib.HXRBDJNZ.js:1:2870
lib.QQFN6VMJ.js:1 Uncaught TypeError: Cannot read properties of undefined (reading 'sanLongCastling')
at L (lib.QQFN6VMJ.js:1:2212)
at $ (lib.QQFN6VMJ.js:1:2317)
at I.sendMove (round.DSXARN7G.js:1:26236)
at I.onUserMove (round.DSXARN7G.js:1:22181)
at lib.HXRBDJNZ.js:1:2870
hey @anton_gusevv can send logs via https://lichess.org/#debug ?
Clear site data, or toggle speech on/off in the account menu.
Clear site data, or toggle speech on/off in the account menu.
The issue was indeed caused by the audio setting being changed to "Speech." I reverted the audio setting to "Standard", and the error disappeared.
The issue was indeed caused by the audio setting being changed to "Speech." I reverted the audio setting to "Standard", and the error disappeared.