-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Sync client assertion failure in unbinded session: Assertion failed: m_initiated #7074
Comments
still happens with an update of baas from #7042:
@danieltabacaru could you guess where to look? |
Did you use Michael's PR? |
➤ Jonathan Reams commented: I've taken a look at this but haven't been able to reproduce it locally. This isn't dependent on baas since it's in the realm-sync-tests which talk to the C++ test server. I think this is happening in one of the client reset tests. I think this may be happening in one of the client reset tests. |
Yes right, i think i forgot to post here back then that this exact assertion also happens with object store test and baas server on linux debug. And you are right, i must be client reset tests. log and detailed stacktrace as of v13.25.1
|
➤ Jonathan Reams commented: The only thing I can think of is that we're racing to read this variable realm-core/src/realm/sync/client.cpp Line 1275 in 822c29d
|
Expected results
Actual Results
src/realm/sync/client.cpp:1324: [realm-core-13.23.1] Assertion failed: m_initiated
stacktrace
Steps & Code to Reproduce
happened during CI run for #6911
Core version
Core version: 13.23.1
The text was updated successfully, but these errors were encountered: