fixes: HocuspocusProviderWebsocket checkConnection ineffective #640
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the v1.1.3,
onMessage
will updatelastMessageReceived
as followIn the v2.2.0, onMessage not update lastMessageReceived.
If the client switch its network from WIFI to LTE or vice versa,
checkConnection
can not able to callwebSocket?.close()
because oflastMessageReceived = 0
in HocuspocusProviderWebsocket constructor.this case can be reproduce in iOS safari or iOS webview(iPhone 15E148 605.1, webkit version:605.1.15), but not easy to find in windows(chrome)、android(chrome/webview)