-
-
Notifications
You must be signed in to change notification settings - Fork 132
Emitted Events from WebSocket pings not forwarded to Subscription Handler #264
Comments
Thanks for opening this issue!
|
I had the same issue. IOS Client Side:
Apparently from some version of parse-server the received message from the ParseLiveQuery didn't return with the type on the main object in the string received. for example: So I've added a short code to always add a __type = "Object" into the Json for the first main "object" and I removed the original object, I don't see how original object is supported in the ParseLiveQuery-iOS-OSX library. So the received json would now look like this: So in the function func handleOperationAsync(_ string: String) -> Task in ClientPrivate.swift I've changed the code to look like this: //--------START CHANGED CODE HERE------//
//--------END CHANGED CODE HERE------//
I hope that this will be taken care of by the library itself cause if I update the library I will always have to remember to add this code. Much blessings |
Does anyone want to open a PR and propose a solution? |
@432player, @HackShitUp The LiveQuery feature has been added as a module to the Parse Apple SDK; could you please verify that this issue is fixed there, and if not open a new issue there? |
New Issue Checklist
Issue Description
The
Subscription.handleEvent
protocol never gets called but WebSocket pings are received (logged inClient.shouldPrintWebSocketTrace
)Steps to reproduce
Define the client, and subscribe to a query the standard way:
WebSocket trace logs received ping but does not forward to the protocol.
Actual Outcome
Event not forwarded at the ParseLiveQuery layer
Expected Outcome
All emitted events should be accessible by the Subscription's handler
Environment
Parse LiveQuery ObjC SDK
2.8.1
1.5.0
1.19.0
iOS 16.0
Server
5.4.1
Remote/Local
The text was updated successfully, but these errors were encountered: