-
Notifications
You must be signed in to change notification settings - Fork 54
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
"Illegal callback invocation from native module." on syncDown #163
Comments
What version of the Mobile SDK are you running on? |
@wmathurin |
I would not call |
How is |
removeAllStores wipes everything, including "system" tables that mobile sync relies on. We call it at logout to make sure nothing that belonged to the user was left behind. |
@wmathurin We are getting the same error after logout and login with different user then logging with first user again in iOS. It seems that the method from native module syncDown is trying to reuse the same callback, which is forbidden by react native doc:
We tried to call removeAllStores on logout but it doesn't help. Would be really good if we could have a guide of which functions are recommended to be called on logout to guarantee any inconsistencies when logging in again. An alternative to callbacks are events which could potentially solve the issue as well. |
When do you intend to fix this bug? |
@wmathurin any updates on this? Still have issue as well, thanks! |
@wmathurin @bhariharan could you please check if you can prioritise this bug into a release? This issue still exists in SDK 10.1.1. Thank you! |
HI GUYZ |
We recommend you stop any running sync before logging out or removing soups or stores. |
Describe the bug
When I try to create a new
syncDown
following registering soup, deleting soup, and registering soup, the app turns into an unrecoverable state (and cannot catch error):To Reproduce
Steps to reproduce the behavior:
This will throw error + prevent to call
syncDown
successfully again. Only way is to stop the application + re-build.Expected behavior
Step 6 would allow to run
syncDown
successfully.Actual behavior
Steps 6 returns:
Versions (please complete the following information):
v8.1.0
Trace
The text was updated successfully, but these errors were encountered: