-
-
Notifications
You must be signed in to change notification settings - Fork 597
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Live Query websocket error: "additional properties not allowed". Sending installation ID when not needed #1136
Comments
That error is a fall back for older versions of Parse Server. If you update to the latest it won’t give you an error. Thanks for the video, it was really helpful. I would like to see a case when it doesn’t reconnect. |
@dplewis thanks for the response. I'm currently using a hosted Parse server on Sashido. Their latest version is 3.6 so unfortunately I don't have control over that. I'll ask them when they plan to update the the latest. Do you happen to know what version this issue was first resolved in? |
Here is the PR for it #977 As for which version most likely 4+ As a workaround you could get the default live query client and set additionalProperties to false. I still would like to fix the disconnect on reconnect issue. |
@dplewis thanks for the workaround tip. That works for me. I didn't realize you could set that value directly with the LiveQueryClient instance. It isn't totally clear in these LiveQueryClient docs . For anyone who finds this:
|
Issue Description
When trying to establish a LiveQuery websocket, sometimes I get this error:
{op: "error", error: "Additional properties not allowed", code: 1, reconnect: true}
In some cases, it will try to reconnect without sending the installation ID which will allow it to connect successfully. However, sometimes it doesn't retry, in which case it just never establishes the LiveQuery connection.
I'm wondering if there's a way to prevent it from sending the installation ID and just send the applicationId and javascriptKey when creating the connection (which seems to be successful each time).
Please see this recording of what I'm seeing in the browser Network tab: https://www.loom.com/share/9f7b96eeb7f049aa8f66a24413a9d977
Environment Setup
Server
JS SDK
Logs/Trace
{op: "error", error: "Additional properties not allowed", code: 1, reconnect: true}
The text was updated successfully, but these errors were encountered: