-
-
Notifications
You must be signed in to change notification settings - Fork 206
ParseLiveListWidget doesn't work #623
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
@RodrigoSMarques Could you help with this. Thanks in advance. |
It is not a problem in LiveQuery because I am using it in two projects without errors. Is the problem using ParseLiveListWidget? I don't know what this widget does. @fischerscode do you know what it can be? |
It can’t be ParseLiveListWidget I’m using it and it works well for me. I’m using |
@yp19 @yp19 @pastordee |
Okay thanks will check it out tonight |
@fischerscode Thanks for the reply. I tried your suggestion with flutter web. I have enabled CORs. It is working fine with flutter web. But it is not working with flutter android, getting the same log repeatedly in adb log:
Any other ideas? |
@fischerscode Without that permission set, the server was receiving connections, I able to see the log on server, I have posted the server log entries in the description. But I have added the permission now. It's still has the same problem. I am using firebase auth, it is working fine and also it able to load the initial list of items with a query. Only the LiveQuery is not working. Something to do with the Websocket connection. |
@fischerscode I see the server is working from Any ideas? |
@fischerscode Friendly ping |
@yp19 Does the same problem appear on mobile? Stuff, I would try:
|
Closing. No activity in the last 15 days. |
I am using following server and client versions
"parse-server": "^4.5.0" (server)
parse_server_sdk_flutter: ^3.0.0 (client)
Flutter log contains following lines (mostly)
Server log contains following lines (mostly)
Flutter parse init:
Note: The LiveQuery is working with Javascript code.
The text was updated successfully, but these errors were encountered: