parse-community / ParseLiveQuery-iOS-OSX

Parse LiveQuery Client for iOS/OS X.
https://parseplatform.org
Other
192 stars 133 forks source link

ParseLiveQuery: Received ping but we don't handle it... #255

Open owais-applligent opened 3 years ago

owais-applligent commented 3 years ago

It continuously printing ParseLiveQuery: Received ping but we don't handle it...

parse-github-assistant[bot] commented 3 years ago

Thanks for opening this issue!

ritteraf commented 2 years ago

I'm receiving this as well. Since OP isn't going to update his post to conform to the template, any info I can provide to help troubleshoot why this is happening?

mtrezza commented 2 years ago

@ritteraf Sure, you can just copy/paste the issue template as post it as a comment, so we get more insight. I'm not really sure what the issue from the existing description.

ULSashido commented 2 years ago

Issue Description

After Initializing Parse, and connecting as Client, I get this in every second: ParseLiveQuery: Received ping but we don't handle it... ParseLiveQuery: Received ping but we don't handle it...

Steps to reproduce

1- Initialize 2- Create Client 3- Subscribe to a classname

Actual Outcome

It doesn't seem to cause any issues, just a print out every second.

Expected Outcome

Don't seem to be a necessary print out. I see it coming from here: https://github.com/parse-community/ParseLiveQuery-iOS-OSX/blob/e8cfb4db6e81e4ce5bb0daa4603739659abf127c/Sources/ParseLiveQuery/Internal/ClientPrivate.swift#L168

Environment

iOS - Parse SDK 2.8.1

Parse LiveQuery ObjC SDK

Server

Database

Logs

ParseLiveQuery: Received ping but we don't handle it... ParseLiveQuery: Received ping but we don't handle it...

proj-sashido commented 2 years ago

i'm getting the same issue. Any updates on this? It prints this every 10 seconds

ChrisCoder9000 commented 2 years ago

I have also the same problem

mtrezza commented 1 year ago

@owais-applligent, @ChrisCoder9000, @project-academy, @ULSashido, @ritteraf 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?