_Bastler/partey_workadventure
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixing reconnect issue

Browse Source 
In the case the reconnect event was triggered on "wake-up", the disconnect event was not sent. But because of a bug in the way we handle the setTimeout, the reconnection to the GameScene never happened after we forced the disconnect scene.
This fixes the issue.
This commit is contained in:
David Négrier 2020-06-17 16:06:02 +02:00
parent b8f9e25b26
commit 817b25b0be
2 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
front/src/Connection.ts
View File

@ -325,6 +325,7 @@ export class Connection implements ConnectionInterface {
});
this.getSocket().on(EventMessage.RECONNECT, () => {
console.log('Reconnect event triggered');
this.connectSocketServer();
if (this.lastPositionShared === null) {
throw new Error('No last position shared found while reconnecting');

2
front/src/Phaser/Game/GameManager.ts
View File

@ -204,8 +204,8 @@ export class GameManager {
// Wait a bit for scene to load. Otherwise, starting ReconnectingSceneName and then starting GameScene one after the other fails for some reason.
this.timeoutCallback = setTimeout(() => {
console.log('Reconnecting to game scene from setTimeout');
this.reconnectToGameScene(lastPositionShared);
this.timeoutCallback = null;
this.reconnectToGameScene(lastPositionShared);
}, 500);
return;
}