Open vatsal-gadhiya-searce opened 4 weeks ago
➤ PM Bot commented:
Jira ticket: RJS-2808
The error message Sync session became inactive
indicates that the device is offline, and the sync client is waiting for the connection to be established before trying to sync data.
I suggest that you add a connection listener to monitor the connectivity.
Thanks @kneth
We have observed few more bugs here in bugsnag with below error:
SIGABRT: Abort program
0 libc.so +0x830f0 abort 1 libc++_shared.so +0xd1cbc 0x73966d8cc0 2 libc++_shared.so +0xd1e70 0x73966d8e74 3 libc++_shared.so +0xe6b70 0x73966edb74 4 libc++_shared.so +0xe6528 cxa_rethrow 5 librealm.so +0x5e7b24 0x72bad28b28 6 librealm.so +0x5f1d5c 0x72bad32d60 7 librealm.so +0x5e71dc 0x72bad281e0 8 librealm.so +0x5e82c0 0x72bad292c4 9 libc.so +0xe689c __pthread_start(void*) 10 libc.so +0x84b68 start_thread
error {"weakInternal":{}} SyncError: error
@vatsal-gadhiya-searce Do you know under which conditions, you observe the above crashes? Do you call reconnect()
in your app?
@kneth The above scenario happens when the app is minimized via hardware backpress and when the user opens the app again it will crash after 2-3 seconds.
we are not calling reconnect() in our app
FYI: I work in @vatsal-gadhiya-searce's team
How frequently does the bug occur?
Sometimes
Description
We have a react native version 0.73.1 app We are using realm version 12.5.0
we are getting below error sometimes and some of the records aren't updated in realm. We have bugsnag added to the app so added all the logs we got from the bugsnag console.
{ “reason”: “Sync session became inactive”, “code”: 1027, “isOk”: false }
InvalidError Counter promise rejection tracking received a non-error. See “promise rejection tracking” tab for more detail.
Stacktrace & log output
Can you reproduce the bug?
Sometimes
Reproduction Steps
Steps:
Version
12.5.0
What services are you using?
Atlas Device Sync
Are you using encryption?
No
Platform OS and version(s)
Android - All versions
Build environment
All versions
Cocoapods version
No response