-
-
Notifications
You must be signed in to change notification settings - Fork 595
Exception in ParseLiveQuery in react-native #232
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
@peterdotjs @wangmengyan95 is it possible for you to make the method in question, and whatever's calling it async? All current user fetching internally should be using the async methods, to support async storage systems. |
@andrewimm I'll make the change to use |
Okay, my concern is that the caller functions might be synchronous, and APIs would need to change to adjust for this. |
Currently we're using |
Thanks for fast response guys. I found one more bug with WebSockets implementation in react-native. Look like live queries are not very popular in RN :) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
getSessionToken()
inParseLiveQuery
calls synccurrentUser()
and throw exception in react-native (with async storage)The text was updated successfully, but these errors were encountered: