You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is currently an issue with a offline caching of objects. If an app (web app) reinitializes the SDK, the localId resets. The means any offline cached objects may have the same localId as another object.
iOS and android uses some form of generated long int (~8 bytes) which is then cached to the disk.
I posted a comment here about it.
There is currently an issue with a offline caching of objects. If an app (web app) reinitializes the SDK, the localId resets. The means any offline cached objects may have the same localId as another object.
iOS and android uses some form of generated long int (~8 bytes) which is then cached to the disk.
iOS
Android
I figures we could replace the counter with a UUID for localId or use something similar to it and avoid collision.
What do you think?
The text was updated successfully, but these errors were encountered: