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
Realm Corruption Following Client Resets Due to Permission/Role Changes on Server #8559
Comments
➤ PM Bot commented: Jira ticket: RCOCOA-2342 |
That's certainly an odd issue. Two questions When you examine the data on the server using the Console, is it also duplicated? Have you examined the data with something other than Realm Studio? e.g. craft up a quick app to read in the local data and output to console? Then compare that to what's shown in Realm Studio. It would eliminate something funky going on with Realm Studio (which I doubt) |
The problem was also synced and could therefore also be seen on the server. We also saw the problems in our Realm Swift App - that's when we realized that something must be wrong. |
Hey @divan84, since this is a sync issue that may require that the team investigates the sync history as well as analyze the server logs, can you please file a support ticket here: http://support.mongodb.com/? The realm-swift repo is primarily used to track bugs with the Realm Swift SDK and engineers working on this project don't have the access necessary to debug server-side problems. |
We will contact the support! Thanks! |
How frequently does the bug occur?
Sometimes
Description
We are experiencing corruptions of Realm databases following client resets triggered by permission/role changes on the server. This issue is not reliably reproducible, and unfortunately, we do not have logs to provide more insight. We only have the incorrect Realm files, which we have examined using Realm Studio.
It is suspected that this issue may arise when the client undergoes multiple client resets in quick succession.
It appears there may be flaws in the client reset logic that need to be addressed!
Stacktrace & log output
No response
Can you reproduce the bug?
No
Reproduction Steps
Roughly speaking, our scenario is as follows
Due to the above workflow, situations may arise where multiple client resets occur in quick succession due to permission/role changes on the server.
However, in some cases, the following issues have been observed:
Version
<= 10.49.1
What Atlas Services are you using?
Atlas Device Sync
Are you using encryption?
No
Platform OS and version(s)
macOS
Build environment
Xcode version: ...
Dependency manager and version: ...
The text was updated successfully, but these errors were encountered: