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
It looks like the SyncSessionImpl.nativePointer is somehow being outdated and crashes the app when being used (e.g. when calling pause/resume).
This is reproducible by having two apps communicating. After Device A sends changes to Device B, Device B will crash when interacting with the SyncSession pointer.
The text was updated successfully, but these errors were encountered:
The root problem was due to a pointer going out of date. The sequence was as follows:
Device A: Open Flexible Sync with initialSubscriptions. This would trigger the creation of the SyncedContext which stored a copy of the current dbPointer.
Device B writes a change
Device A receives this change, integrates it, updates the Realm pointer and closes the old one
Device A access the SyncSession. This tried to lazily create the session pointer using the, now closed, dbPointer.
Device A would crash with a SEGFAULT.
Creating both Subscriptions and SyncSession immediately when accessed the first time fixes the problem.
It looks like the
SyncSessionImpl.nativePointer
is somehow being outdated and crashes the app when being used (e.g. when calling pause/resume).This is reproducible by having two apps communicating. After Device A sends changes to Device B, Device B will crash when interacting with the SyncSession pointer.
The text was updated successfully, but these errors were encountered: