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
Fix more encryption issues on exFAT filesystem (#7162)
* refactor file operations
* fix an issue on exFAT systems where the file unique id was not correct for new Realms leading to corruption for encrypted Realms
* fix the remaining callsites where a unique id could be reused
* add changelog note
* fix an error in the tests that would cause spawned processes to not have the same fallback tmp path which could cause issues if running on a filesystem that doesn't support mkfifo such as exFAT
* return none in an interprocess race on creating a lock file and getting its unique id
* Throw an exception on unique id failure instead of
asserting in consideration of external processes.
Use prealloc to size the file instead of a separate resize operation.
Add the file path to help debug exceptions.
* better error handling and cache a File unique id to catch more errors
Copy file name to clipboardexpand all lines: CHANGELOG.md
+1
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,7 @@
7
7
8
8
### Fixed
9
9
* <How do the end-user experience this issue? what was the impact?> ([#????](https://github.com/realm/realm-core/issues/????), since v?.?.?)
10
+
* Fixed several causes of "decryption failed" exceptions that could happen when opening multiple encrypted Realm files in the same process while using Apple/linux and storing the Realms on an exFAT file system. ([#7156](https://github.com/realm/realm-core/issues/7156), since the beginning)
10
11
* Update existing std exceptions thrown by the Sync Client to use Realm exceptions. ([#6255](https://github.com/realm/realm-core/issues/6255), since v10.2.0)
11
12
* Having a class name of length 57 would make client reset crash as a limit of 56 was wrongly enforced (57 is the correct limit) ([#7176](https://github.com/realm/realm-core/issues/7176), since v10.0.0)
12
13
* Automatic client reset recovery on flexible sync Realms would apply recovered changes in multiple write transactions, releasing the write lock in between. This had several observable negative effects:
0 commit comments