-
-
Notifications
You must be signed in to change notification settings - Fork 32
Subscription Failing Without Error #103
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
Comments
Sample Activity here:
|
Anything on this? |
This is what i did. Important Important
Still working good for me.. You can try this: |
Hello @bstillitano thank you for trying live query
Thanks |
@rommansabbir please stop. As many people have said, your solution only works for back4app and not the common setup of self hosted parse instances. @mmimeault thanks for taking the time to look at this. I truly do appreciate it. I am not seeing any client side errors or server side errors or logs. The strange thing is though that this works fine when run in a Java project which leads me to believe that there may be something wrong with the Kotlin implementation/migration of this library. When I say
I mean that none of the subscription events are being fired including errors, subscriptions and object updates Any help is appreciated. |
Thanks, but you should mentioned first that you are not using Back4App.
Best of luck
…On Tue, Apr 23, 2019, 8:08 PM bstillitano ***@***.***> wrote:
@rommansabbir <https://github.com/rommansabbir> please stop. As many
people have said, your solution only works for back4app and not the common
setup of self hosted parse instances.
@mmimeault <https://github.com/mmimeault> thanks for taking the time to
look at this. I truly do appreciate it. I am not seeing any client side
errors or server side errors or logs.
The strange thing is though that this works fine when run in a Java
project which leads me to believe that there may be something wrong with
the Kotlin implementation/migration of this library.
Any help is appreciated.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#103 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGF7PA4VIJTNKKCS4TWBZVTPR4J7HANCNFSM4HFERK3A>
.
|
@mmimeault are you able to assist with this? |
Wondering if this is of any help to you @mmimeault. Really need to get this issue resolved as over on StackOverflow, multiple people are having the same issue. |
Hello, It is really to debug that kind of issue remotely. If you put some breakpoint into the OkHttp3WebSocketClient, do you any of the callback methods called? Maybe there is an error not thrown back to the live query client. There is 5 callback to the okhttp3 websocket client (WebSocketListener). onOpen, onMessage(2), onClosed and onFailure. Maybe putting some breakpoints there will help us debug the issue. Any of those method are called when starting the subscription? Thanks |
@mmimeault you're right. I'm getting the following stacktrace when subscribing to any queries: Do you have any guidance on where to from here? LiveQuery is definitely running. |
Just before digging into the error itself, you should add this callback after getting the client from the factory
You would get the error you see in your debugger in that onSocketError callback. |
I am not an expert about sockets nor the parse server implementation. Maybe you can try just simply opening a connection to the port in the terminal. You can use But if it failed at this point with that kind of error, I'm 99.99% sure it is one of the issue I mentioned above. |
@bstillitano Can you explain why you closed the ticket. Thanks |
@mmimeault I closed it because I resolved the issue. Using your tip of debugging the socket, I found that I was getting a 403. I thought this may have been a setup issue on my end so changed a few things around but this did not help. After restoring my server to its original setup, I found that by specifying the port directly in the parse server URL in the SDK it connects properly and subscriptions work fine. Tried with a back4app and heroku setup along with my google cloud setup and all to the same result so this looks like a limit of the SDK or OkHttp |
It is not a limit of the SDK or OkHttp to have to specify the port, if you are using a non-standard port, it makes sense that you would have to specify it. |
I don’t have a special configuration....I tried with multiple ports and the
default configurations recommended in the Parse Docs. Happened across
multiple servers, providers and configurations also.
This is quite obviously a limitation of the SDK and it would not go astray
to mention that if you are seeing no callbacks to make sure that you are
specifying the port in your server URL.
…On Sun, 5 May 2019 at 2:05 am, John Carlson ***@***.***> wrote:
It is not a limit of the SDK or OkHttp to have to specify the port, if you
are using a non-standard port, it makes sense that you would have to
specify it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#103 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJVMONX6VJER5UDX3YXGJ7TPTWX4RANCNFSM4HFERK3A>
.
|
I've set up quite a few Parse server instances on many different providers with the standard setup and have never had to specify the port in the Android SDK. Feel free to open a PR on the docs if you would like. |
I am subscribing to a query on a table that has liveQuery enabled however the subscription seems to just be failing completely. The code is below:
Any help with this is highly appreciated. I have looked at @rommansabbir project and it does nothing that the example project doesn't show us. Really stuck on this one.
The text was updated successfully, but these errors were encountered: