-
Notifications
You must be signed in to change notification settings - Fork 172
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
Crash Either the encryption key is incorrect or data is corrupted
with reproducible .ream
file
#8055
Comments
Note: Realm-Swift v10.54.0 contains Realm-Core v14.13.0. While I did have (a lot of!) issues with corrupted files in the past, I currently run on core 14.12.1 (iOS) and 14.7.0 (Android) without reports. Might be a regression in v14.13.0. (The 20.1.1, 20.1.0 and 14.13.2 release notes are not included in the CHANGELOG.md btw) |
Hi @BlueCobold Is your crash / error message same as mine after upgrading Realm iOS SDK version?
Thank you! |
@JohnnyTseng I did have this kind of error message ("HMAC check") as well. Among various others or similar ones. The problems were manyfold. If you have the file at hand, did you by chance try using the command line tools to decrypt the file, to use the trawler or to open it via RealmStudio? |
I have tried using RealmStudio to open the DB file; however, it still fails. I guess the DB file is already corrupted 🥲 |
@JohnnyTseng It certainly sounds like if that error is given. Does your app access the realm file in single or in multi-threading? |
There is no changes relevant to this issue from 14.12.1 to 14.13.0. |
@JohnnyTseng In order to progress on this, I would need a realm file together with the encryption key used. You can share that privately with me on [email protected] |
Hello @jedelbo , Thank you for replying, I have sent the key through the mail! |
I have tried to open the received file using the key, I got. It fails the HMAC check as described above. The file itself looks ok, but of course just a single bit wrong will make the check fail. However, I would say that the chance that there is a problem with the encryption key is pretty high. If you can somehow reproduce the error locally, I will be happy to help the investigation. |
Thank you @jedelbo , I'll close this issue! |
What was the final outcome? |
@BlueCobold We did not find the root cause of this issue, became a mystery. |
Hello,
We've upgraded our Realm SDK from
10.45.1
to10.54.0
, after that, we are receiving ~2000 crashes per dayAll crashes points to same error message:
The only thing we did is upgrade Realm SDK version. We've managed to retrieve a db file that is having this issue
(I have sent it to
[email protected]
, title is:Realm file for issue #8055 and #8719
)SDK and version
SDK : Cocoa
Version: 10.54.0
Observations
How frequent do the crash occur?
Affected thousands of our users
Does it happen in production or during dev/test?
Both production and dev/test environment
Can the crash be reproduced by you?
N/A
Can you provide instructions for how we can reproduce it?
Cannot be steadily reproduced, but we do have a
realm
db file that encountered this issueCrash log / stacktrace
Steps & Code to Reproduce
The text was updated successfully, but these errors were encountered: