Connectivity not stable in 1.11.0
On the self-hosted version, the WebSocket connection keeps toggling between offline and online every second. Additionally, the main pop-up ("Welcome back online") appears every 6 to 7 seconds.
Everything was working fine in version 1.10.1, so I don't think this is a deployment issue.
3 Comments
·23 days agoI'd look at the server side logs, if you don't see any issues, next step would be to download your current client side state under Settings > Data > Download SQLite Database, then clean all client side cache.
Open dev tools > application > storage > clear site data.
Additionally you could look into client side console logs, but I am assuming that the issue is probably in a catch up sync. If you find any errors in the console log please share so I can try and recreate on my end and hopefully patch what would be causing this.
index-DEQmsSvM.js:12 [Runtime][SyncTransport] catch_up_fallback_snapshot
i see error in this class in dev console
index-DEQmsSvM.js:12 [Runtime][SyncTransport] Failed to apply catch-up mutation {mutationId: 'mut_82749228-16cb-4077-a733-2a5a00e05a17', error: 'Report not found after update'}
Ns @ index-DEQmsSvM.js:12
(anonymous) @ index-DEQmsSvM.js:12
handleCatchUp @ index-DEQmsSvM.js:12
await in handleCatchUp
processMessage @ index-DEQmsSvM.js:12
handleRawMessage @ index-DEQmsSvM.js:12
a.onmessage @ index-DEQmsSvM.js:12
index-DEQmsSvM.js:12 [Runtime][SyncTransport] catch_up_fallback_snapshot {reason: 'apply_failed', sinceVersion: 1820, localVersion: 1820, spaceId: 'af2c8618-8e55-4ac9-8919-c47746845580'}
Ns @ index-DEQmsSvM.js:12
(anonymous) @ index-DEQmsSvM.js:12
handleCatchUpUnsafe @ index-DEQmsSvM.js:12
handleCatchUp @ index-DEQmsSvM.js:12
await in handleCatchUp
processMessage @ index-DEQmsSvM.js:12
handleRawMessage @ index-DEQmsSvM.js:12
a.onmessage @ index-DEQmsSvM.js:12
index-DEQmsSvM.js:12 [Runtime][SyncTransport] Failed to apply catch-up mutation {mutationId: 'mut_82749228-16cb-4077-a733-2a5a00e05a17', error: 'Report not found after update'}
Ns @ index-DEQmsSvM.js:12
(anonymous) @ index-DEQmsSvM.js:12
handleCatchUp @ index-DEQmsSvM.js:12
await in handleCatchUp
processMessage @ index-DEQmsSvM.js:12
handleRawMessage @ index-DEQmsSvM.js:12
a.onmessage @ index-DEQmsSvM.js:12
index-DEQmsSvM.js:12 [Runtime][SyncTransport] catch_up_fallback_snapshot {reason: 'apply_failed', sinceVersion: 1820, localVersion: 1820, spaceId: 'af2c8618-8e55-4ac9-8919-c47746845580'}
Ns @ index-DEQmsSvM.js:12
(anonymous) @ index-DEQmsSvM.js:12
handleCatchUpUnsafe @ index-DEQmsSvM.js:12
handleCatchUp @ index-DEQmsSvM.js:12
await in handleCatchUp
processMessage @ index-DEQmsSvM.js:12
handleRawMessage @ index-DEQmsSvM.js:12
a.onmessage @ index-DEQmsSvM.js:12
Let me know if that make any sense or should i dig deeper.
Sorry for a late reply, was away for couple of days, clearing the storage from the browser should fix this, but I also found a bug that was causing this, patch coming in soon.