lemonlab
commented
2 years ago Same here.
It works on a simulator, but not on a real device.
Everything works well with 10.32.0.
The bug appears on 10.32.1 and above.
Closed CoderHJZhao closed 1 year ago
lemonlab
commented
2 years ago Same here.
It works on a simulator, but not on a real device.
Everything works well with 10.32.0.
The bug appears on 10.32.1 and above.
dianaafanador3
commented
2 years ago Hi @CoderHJZhao and @lemonlab are you able to reproduce this?, Can you attach a project where we can take a look and test this against a real device.
lemonlab
commented
2 years ago Yes, i can reproduce the bug every time i try to open an encrypted local Realm database on a real device (iOS 16.1.1).
Here is a test project, with a demo encrypted database : RealmTest.zip
The key used to encrypt the database is 0000000000000000000000000000000000000000000000000000000000000000
Log on the simulator (iPhone 14, iOS 16.1) :
Realm is readyLog on a real device (iPhone 8, iOS 16.1.1) :
Error Domain=io.realm Code=2 "Unable to open a realm at path '/var/mobile/Containers/Data/Application/9B0C5D6F-674A-483F-B98C-ED54107BAB64/Library/Caches/default.realm': Realm file decryption failed Path:Exception backtrace:
0 Realm 0x0000000103ee1994 _ZN5realm15InvalidDatabaseC2ERKNSt3__112basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEES9_ + 60
1 Realm 0x0000000103e885f8 _ZN5realm9SlabAlloc11attach_fileERKNSt3__112basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEERNS0_6ConfigE + 2832
2 Realm 0x0000000103ebeb28 _ZN5realm2DB7do_openERKNSt3__112basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEEbbNS_9DBOptionsE + 1852
3 Realm 0x0000000103ec1e2c _ZN5realm2DB4openERNS_11ReplicationENS_9DBOptionsE + 148
4 Realm 0x0000000103ec7328 _ZN5realm2DB6createENSt3__110unique_ptrINS_11ReplicationENS1_14default_deleteIS3_EEEENS_9DBOptionsE + 336
5 Realm 0x00000001040ed3c8 _ZN5realm5_impl16RealmCoordinator7open_dbEv + 1084
6 Realm 0x00000001040ee344 _ZN5realm5_impl16RealmCoordinator12do_get_realmENS_5Realm6ConfigERNSt3__110shared_ptrIS2_EENS_4util8OptionalINS_9VersionIDEEERNS8_17CheckedUniqueLockE + 72
7 Realm 0x00000001040ee168 _ZN5realm5_impl16RealmCoordinator9get_realmENS_5Realm6ConfigENS_4util8OptionalINS_9VersionIDEEE + 400
8 Realm 0x000000010417d150 _ZN5realm5Realm16get_shared_realmENS0_6ConfigE + 120
9 Realm 0x0000000103e0eca0 +[RLMRealm realmWithConfiguration:queue:error:] + 1744
10 RealmSwift 0x0000000102cc21dc $sSo8RLMRealmC13configuration5queueABSo0A13ConfigurationC_So012OS_dispatch_C0CSgtKcfCTO + 128
11 RealmSwift 0x0000000102d43db4 $s10RealmSwift0A0V13configuration5queueA2C13ConfigurationV_So012OS_dispatch_D0CSgtKcfC + 188
12 RealmTest 0x00000001025536a0 $s9RealmTest0aB3AppVACycfC + 612
13 RealmTest 0x00000001025554cc $s9RealmTest0aB3AppV7SwiftUI0C0AadEPxycfCTW + 12
14 SwiftUI 0x00000001ba7d3f6c 579229A0-9ABB-35A3-8104-3F567C142DD8 + 1007468
15 RealmTest 0x00000001025554a0 $s9RealmTest0aB3AppV5$mainyyFZ + 40
16 RealmTest 0x00000001025559cc main + 12
17 dyld 0x00000001d3b30df0 A2AA3A68-07F7-3D52-A49E-D29D136813F3 + 81392." UserInfo={Error Code=2, NSFilePath=/var/mobile/Containers/Data/Application/9B0C5D6F-674A-483F-B98C-ED54107BAB64/Library/Caches/default.realm, Underlying=Realm file decryption failed Path: /var/mobile/Containers/Data/Application/9B0C5D6F-674A-483F-B98C-ED54107BAB64/Library/Caches/default.realm
Exception backtrace:
0 Realm 0x0000000103ee1994 _ZN5realm15InvalidDatabaseC2ERKNSt3__112basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEES9_ + 60
1 Realm 0x0000000103e885f8 _ZN5realm9SlabAlloc11attach_fileERKNSt3__112basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEERNS0_6ConfigE + 2832
2 Realm 0x0000000103ebeb28 _ZN5realm2DB7do_openERKNSt3__112basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEEbbNS_9DBOptionsE + 1852
3 Realm 0x0000000103ec1e2c _ZN5realm2DB4openERNS_11ReplicationENS_9DBOptionsE + 148
4 Realm 0x0000000103ec7328 _ZN5realm2DB6createENSt3__110unique_ptrINS_11ReplicationENS1_14default_deleteIS3_EEEENS_9DBOptionsE + 336
5 Realm 0x00000001040ed3c8 _ZN5realm5_impl16RealmCoordinator7open_dbEv + 1084
6 Realm 0x00000001040ee344 _ZN5realm5_impl16RealmCoordinator12do_get_realmENS_5Realm6ConfigERNSt3__110shared_ptrIS2_EENS_4util8OptionalINS_9VersionIDEEERNS8_17CheckedUniqueLockE + 72
7 Realm 0x00000001040ee168 _ZN5realm5_impl16RealmCoordinator9get_realmENS_5Realm6ConfigENS_4util8OptionalINS_9VersionIDEEE + 400
8 Realm 0x000000010417d150 _ZN5realm5Realm16get_shared_realmENS0_6ConfigE + 120
9 Realm 0x0000000103e0eca0 +[RLMRealm realmWithConfiguration:queue:error:] + 1744
10 RealmSwift 0x0000000102cc21dc $sSo8RLMRealmC13configuration5queueABSo0A13ConfigurationC_So012OS_dispatch_C0CSgtKcfCTO + 128
11 RealmSwift 0x0000000102d43db4 $s10RealmSwift0A0V13configuration5queueA2C13ConfigurationV_So012OS_dispatch_D0CSgtKcfC + 188
12 RealmTest 0x00000001025536a0 $s9RealmTest0aB3AppVACycfC + 612
13 RealmTest 0x00000001025554cc $s9RealmTest0aB3AppV7SwiftUI0C0AadEPxycfCTW + 12
14 SwiftUI 0x00000001ba7d3f6c 579229A0-9ABB-35A3-8104-3F567C142DD8 + 1007468
15 RealmTest 0x00000001025554a0 $s9RealmTest0aB3AppV5$mainyyFZ + 40
16 RealmTest 0x00000001025559cc main + 12
17 dyld 0x00000001d3b30df0 A2AA3A68-07F7-3D52-A49E-D29D136813F3 + 81392, NSLocalizedDescription=Unable to open a realm at path '/var/mobile/Containers/Data/Application/9B0C5D6F-674A-483F-B98C-ED54107BAB64/Library/Caches/default.realm': Realm file decryption failed Path:Exception backtrace:
0 Realm 0x0000000103ee1994 _ZN5realm15InvalidDatabaseC2ERKNSt3__112basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEES9_ + 60
1 Realm 0x0000000103e885f8 _ZN5realm9SlabAlloc11attach_fileERKNSt3__112basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEERNS0_6ConfigE + 2832
2 Realm 0x0000000103ebeb28 _ZN5realm2DB7do_openERKNSt3__112basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEEbbNS_9DBOptionsE + 1852
3 Realm 0x0000000103ec1e2c _ZN5realm2DB4openERNS_11ReplicationENS_9DBOptionsE + 148
4 Realm 0x0000000103ec7328 _ZN5realm2DB6createENSt3__110unique_ptrINS_11ReplicationENS1_14default_deleteIS3_EEEENS_9DBOptionsE + 336
5 Realm 0x00000001040ed3c8 _ZN5realm5_impl16RealmCoordinator7open_dbEv + 1084
6 Realm 0x00000001040ee344 _ZN5realm5_impl16RealmCoordinator12do_get_realmENS_5Realm6ConfigERNSt3__110shared_ptrIS2_EENS_4util8OptionalINS_9VersionIDEEERNS8_17CheckedUniqueLockE + 72
7 Realm 0x00000001040ee168 _ZN5realm5_impl16RealmCoordinator9get_realmENS_5Realm6ConfigENS_4util8OptionalINS_9VersionIDEEE + 400
8 Realm 0x000000010417d150 _ZN5realm5Realm16get_shared_realmENS0_6ConfigE + 120
9 Realm 0x0000000103e0eca0 +[RLMRealm realmWithConfiguration:queue:error:] + 1744
10 RealmSwift 0x0000000102cc21dc $sSo8RLMRealmC13configuration5queueABSo0A13ConfigurationC_So012OS_dispatch_C0CSgtKcfCTO + 128
11 RealmSwift 0x0000000102d43db4 $s10RealmSwift0A0V13configuration5queueA2C13ConfigurationV_So012OS_dispatch_D0CSgtKcfC + 188
12 RealmTest 0x00000001025536a0 $s9RealmTest0aB3AppVACycfC + 612
13 RealmTest 0x00000001025554cc $s9RealmTest0aB3AppV7SwiftUI0C0AadEPxycfCTW + 12
14 SwiftUI 0x00000001ba7d3f6c 579229A0-9ABB-35A3-8104-3F567C142DD8 + 1007468
15 RealmTest 0x00000001025554a0 $s9RealmTest0aB3AppV5$mainyyFZ + 40
16 RealmTest 0x00000001025559cc main + 12
17 dyld 0x00000001d3b30df0 A2AA3A68-07F7-3D52-A49E-D29D136813F3 + 81392.}
CoderHJZhao
commented
2 years ago Yes, i can reproduce the bug every time i try to open an encrypted local Realm database on a real device (iOS 16.1.1).
Here is a test project, with a demo encrypted database : RealmTest.zip The key used to encrypt the database is
0000000000000000000000000000000000000000000000000000000000000000Log on the simulator (iPhone 14, iOS 16.1) :
Realm is readyLog on a real device (iPhone 8, iOS 16.1.1) :
Error Domain=io.realm Code=2 "Unable to open a realm at path '/var/mobile/Containers/Data/Application/9B0C5D6F-674A-483F-B98C-ED54107BAB64/Library/Caches/default.realm': Realm file decryption failed Path:Exception backtrace: 0 Realm 0x0000000103ee1994 _ZN5realm15InvalidDatabaseC2ERKNSt3__112basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEES9_ + 60 1 Realm 0x0000000103e885f8 _ZN5realm9SlabAlloc11attach_fileERKNSt3__112basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEERNS0_6ConfigE + 2832 2 Realm 0x0000000103ebeb28 _ZN5realm2DB7do_openERKNSt3__112basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEEbbNS_9DBOptionsE + 1852 3 Realm 0x0000000103ec1e2c _ZN5realm2DB4openERNS_11ReplicationENS_9DBOptionsE + 148 4 Realm 0x0000000103ec7328 _ZN5realm2DB6createENSt3__110unique_ptrINS_11ReplicationENS1_14default_deleteIS3_EEEENS_9DBOptionsE + 336 5 Realm 0x00000001040ed3c8 _ZN5realm5_impl16RealmCoordinator7open_dbEv + 1084 6 Realm 0x00000001040ee344 _ZN5realm5_impl16RealmCoordinator12do_get_realmENS_5Realm6ConfigERNSt3__110shared_ptrIS2_EENS_4util8OptionalINS_9VersionIDEEERNS8_17CheckedUniqueLockE + 72 7 Realm 0x00000001040ee168 _ZN5realm5_impl16RealmCoordinator9get_realmENS_5Realm6ConfigENS_4util8OptionalINS_9VersionIDEEE + 400 8 Realm 0x000000010417d150 _ZN5realm5Realm16get_shared_realmENS0_6ConfigE + 120 9 Realm 0x0000000103e0eca0 +[RLMRealm realmWithConfiguration:queue:error:] + 1744 10 RealmSwift 0x0000000102cc21dc $sSo8RLMRealmC13configuration5queueABSo0A13ConfigurationC_So012OS_dispatch_C0CSgtKcfCTO + 128 11 RealmSwift 0x0000000102d43db4 $s10RealmSwift0A0V13configuration5queueA2C13ConfigurationV_So012OS_dispatch_D0CSgtKcfC + 188 12 RealmTest 0x00000001025536a0 $s9RealmTest0aB3AppVACycfC + 612 13 RealmTest 0x00000001025554cc $s9RealmTest0aB3AppV7SwiftUI0C0AadEPxycfCTW + 12 14 SwiftUI 0x00000001ba7d3f6c 579229A0-9ABB-35A3-8104-3F567C142DD8 + 1007468 15 RealmTest 0x00000001025554a0 $s9RealmTest0aB3AppV5$mainyyFZ + 40 16 RealmTest 0x00000001025559cc main + 12 17 dyld 0x00000001d3b30df0 A2AA3A68-07F7-3D52-A49E-D29D136813F3 + 81392." UserInfo={Error Code=2, NSFilePath=/var/mobile/Containers/Data/Application/9B0C5D6F-674A-483F-B98C-ED54107BAB64/Library/Caches/default.realm, Underlying=Realm file decryption failed Path: /var/mobile/Containers/Data/Application/9B0C5D6F-674A-483F-B98C-ED54107BAB64/Library/Caches/default.realm Exception backtrace: 0 Realm 0x0000000103ee1994 _ZN5realm15InvalidDatabaseC2ERKNSt3__112basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEES9_ + 60 1 Realm 0x0000000103e885f8 _ZN5realm9SlabAlloc11attach_fileERKNSt3__112basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEERNS0_6ConfigE + 2832 2 Realm 0x0000000103ebeb28 _ZN5realm2DB7do_openERKNSt3__112basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEEbbNS_9DBOptionsE + 1852 3 Realm 0x0000000103ec1e2c _ZN5realm2DB4openERNS_11ReplicationENS_9DBOptionsE + 148 4 Realm 0x0000000103ec7328 _ZN5realm2DB6createENSt3__110unique_ptrINS_11ReplicationENS1_14default_deleteIS3_EEEENS_9DBOptionsE + 336 5 Realm 0x00000001040ed3c8 _ZN5realm5_impl16RealmCoordinator7open_dbEv + 1084 6 Realm 0x00000001040ee344 _ZN5realm5_impl16RealmCoordinator12do_get_realmENS_5Realm6ConfigERNSt3__110shared_ptrIS2_EENS_4util8OptionalINS_9VersionIDEEERNS8_17CheckedUniqueLockE + 72 7 Realm 0x00000001040ee168 _ZN5realm5_impl16RealmCoordinator9get_realmENS_5Realm6ConfigENS_4util8OptionalINS_9VersionIDEEE + 400 8 Realm 0x000000010417d150 _ZN5realm5Realm16get_shared_realmENS0_6ConfigE + 120 9 Realm 0x0000000103e0eca0 +[RLMRealm realmWithConfiguration:queue:error:] + 1744 10 RealmSwift 0x0000000102cc21dc $sSo8RLMRealmC13configuration5queueABSo0A13ConfigurationC_So012OS_dispatch_C0CSgtKcfCTO + 128 11 RealmSwift 0x0000000102d43db4 $s10RealmSwift0A0V13configuration5queueA2C13ConfigurationV_So012OS_dispatch_D0CSgtKcfC + 188 12 RealmTest 0x00000001025536a0 $s9RealmTest0aB3AppVACycfC + 612 13 RealmTest 0x00000001025554cc $s9RealmTest0aB3AppV7SwiftUI0C0AadEPxycfCTW + 12 14 SwiftUI 0x00000001ba7d3f6c 579229A0-9ABB-35A3-8104-3F567C142DD8 + 1007468 15 RealmTest 0x00000001025554a0 $s9RealmTest0aB3AppV5$mainyyFZ + 40 16 RealmTest 0x00000001025559cc main + 12 17 dyld 0x00000001d3b30df0 A2AA3A68-07F7-3D52-A49E-D29D136813F3 + 81392, NSLocalizedDescription=Unable to open a realm at path '/var/mobile/Containers/Data/Application/9B0C5D6F-674A-483F-B98C-ED54107BAB64/Library/Caches/default.realm': Realm file decryption failed Path:Exception backtrace: 0 Realm 0x0000000103ee1994 _ZN5realm15InvalidDatabaseC2ERKNSt3__112basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEES9_ + 60 1 Realm 0x0000000103e885f8 _ZN5realm9SlabAlloc11attach_fileERKNSt3__112basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEERNS0_6ConfigE + 2832 2 Realm 0x0000000103ebeb28 _ZN5realm2DB7do_openERKNSt3__112basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEEbbNS_9DBOptionsE + 1852 3 Realm 0x0000000103ec1e2c _ZN5realm2DB4openERNS_11ReplicationENS_9DBOptionsE + 148 4 Realm 0x0000000103ec7328 _ZN5realm2DB6createENSt3__110unique_ptrINS_11ReplicationENS1_14default_deleteIS3_EEEENS_9DBOptionsE + 336 5 Realm 0x00000001040ed3c8 _ZN5realm5_impl16RealmCoordinator7open_dbEv + 1084 6 Realm 0x00000001040ee344 _ZN5realm5_impl16RealmCoordinator12do_get_realmENS_5Realm6ConfigERNSt3__110shared_ptrIS2_EENS_4util8OptionalINS_9VersionIDEEERNS8_17CheckedUniqueLockE + 72 7 Realm 0x00000001040ee168 _ZN5realm5_impl16RealmCoordinator9get_realmENS_5Realm6ConfigENS_4util8OptionalINS_9VersionIDEEE + 400 8 Realm 0x000000010417d150 _ZN5realm5Realm16get_shared_realmENS0_6ConfigE + 120 9 Realm 0x0000000103e0eca0 +[RLMRealm realmWithConfiguration:queue:error:] + 1744 10 RealmSwift 0x0000000102cc21dc $sSo8RLMRealmC13configuration5queueABSo0A13ConfigurationC_So012OS_dispatch_C0CSgtKcfCTO + 128 11 RealmSwift 0x0000000102d43db4 $s10RealmSwift0A0V13configuration5queueA2C13ConfigurationV_So012OS_dispatch_D0CSgtKcfC + 188 12 RealmTest 0x00000001025536a0 $s9RealmTest0aB3AppVACycfC + 612 13 RealmTest 0x00000001025554cc $s9RealmTest0aB3AppV7SwiftUI0C0AadEPxycfCTW + 12 14 SwiftUI 0x00000001ba7d3f6c 579229A0-9ABB-35A3-8104-3F567C142DD8 + 1007468 15 RealmTest 0x00000001025554a0 $s9RealmTest0aB3AppV5$mainyyFZ + 40 16 RealmTest 0x00000001025559cc main + 12 17 dyld 0x00000001d3b30df0 A2AA3A68-07F7-3D52-A49E-D29D136813F3 + 81392.}
Steps to reproduce:
I hope to solve it as soon as possible, at present, as long as the DB is encrypted, you will encounter such an error, the emulator is normal, and the real machine has been reporting an error.
CoderHJZhao
commented
2 years ago @dianaafanador3 Steps to reproduce:
I hope to solve it as soon as possible, at present, as long as the DB is encrypted, you will encounter such an error, the emulator is normal, and the real machine has been reporting an error.
sipersso
commented
2 years ago Same issue here. If App Store review hadn't caught this error I would have tanked my app ratings. I hope this will be fixed as soon as possible as my app won't function if this is still there.
dianaafanador3
commented
2 years ago @sipersso from which version are coming and what is your actual version of RealmSwift?, Do you have an encrypted realm as well?
sipersso
commented
2 years ago @dianaafanador3 Yes, I have an encrypted realm I ship with the app for providing default data. By the reproduction steps in the sample projects here it sounds like it is the same issue. I was using 10.32.0 before this, but I did not use this version when creating the realm file for that I use for default data. The error message I get is just that it failed to decrypt. Reverting back to 10.32.0 fixes the issue.
jedelbo
commented
2 years ago @dianaafanador3 I have no problem opening the file provided above using Core only. Could the problem be in the SDK?
dianaafanador3
commented
2 years ago @lemonlab I'm not able to open the bundle realm from the simulator or a device, and I tested with our latest release and with 10.32.0. I'm able to access it only using Realm Studio. What did you use to create this realm file?
lemonlab
commented
2 years ago I've used the Realm JS SDK (https://github.com/realm/realm-js), in it's latest version (v11.2.0).
dianaafanador3
commented
2 years ago @sipersso do you remember which version you used to create this file?
sipersso
commented
2 years ago I used the iOS SDK, but I don’t remember which version. I don’t want to post it here, but can send it via email if you like.
dianaafanador3
commented
2 years ago @lemonlab encrypted realm files aren't fully portable and only work on machines with the same page size as the one which created them, that's probably why are you getting the error. @sipersso and @CoderHJZhao probably in your cases the realm file was created with a different machine (with a different page size, notably arm64 (including m1) has a 16k page size while nearly everything else has 4k) that the one used to open the realm. @sipersso if you could send us the realm file to help@realm.io, I want to know why downgrading to 10.32.0 fixed the issue in your side.
lemonlab
commented
2 years ago I've used a mac with intel processor, my page size is 4k. I think an iPhone has a page size of 4k as well. Downgrading to 10.32.0 fix the issue for me as well on a real phone, with an encrypted database.
sipersso
commented
1 year ago @lemonlab encrypted realm files aren't fully portable and only work on machines with the same page size as the one which created them, that's probably why are you getting the error. @sipersso and @CoderHJZhao probably in your cases the realm file was created with a different machine (with a different page size, notably arm64 (including m1) has a 16k page size while nearly everything else has 4k) that the one used to open the realm. @sipersso if you could send us the realm file to help@realm.io, I want to know why downgrading to 10.32.0 fixed the issue in your side.
I sent the realm via help@realm.io.
Wow, I had no idea that encrypted Realm are not portable. Just checked the documentation and could not find this info anywhere. This could potentially be a big issue for me. Hope you'll find the issue!
CoderHJZhao
commented
1 year ago @dianaafanador3 Downgrading to 10.32.0 fix the issue for me as well on a real phone, with an encrypted database too.If I don't use encryption, realmDB can be opened normally, as long as encryption is used, the real machine cannot be opened normally, the emulator is normal, the current problem causes me to be unable to update my appstore application, I hope it can be solved as soon as possible, thank you!
dianaafanador3
commented
1 year ago I was able to repro the issues and identify which check is causing the error. We'll take a look at this and inform you as soon as we know more.
sipersso
commented
1 year ago @dianaafanador3 do you know when a new version containing the realm core upgrade will be released? I want to upgrade as soon as possible so I also can get all the crash/corruption fixes you did recently. Until it is released I have to do a lot of manual support work to restore data for customers that has had their data corrupted :/
sipersso
commented
1 year ago @jedelbo I noticed that this has been merged to core, but that Realm-Swift is several versions behind. Do you know when we can expect an update?
dianaafanador3
commented
1 year ago @sipersso We are preparing a release with Core 13.1.1, but because there are some major changes this may take a while. I'll update when we have a release ready
sipersso
commented
1 year ago Ok @dianaafanador3 thanks for the update.
sipersso
commented
1 year ago Version 10.34.0 was released a couple of days ago. Does that fix include the new core version (13.1.1) @dianaafanador3 ? This issue is a blocker for me to upgrade realm versions :/ And until I do, I'll keep getting the random crashes you have already fixed :(
sipersso
commented
1 year ago Looks like this is still an issue in 10.34.0 :(
dianaafanador3
commented
1 year ago @sipersso In our most recent release we didn't update core, but this is something we are currently working for our next release, given that it is a big release on the core side.
sipersso
commented
1 year ago Currently this issue causes me not being able to build my app alone since I am seeing Xcode build issues with the version I am currently using and can't upgrade to the latest realm version since it causes the app to crash on startup. Any ideas on when this will be released? I am currently blocked from releasing my app to the AppStore because of this.
dianaafanador3
commented
1 year ago @sipersso we are working on this release at the moment, you can follow this PR https://github.com/realm/realm-swift/pull/8058 to check the progress of the core update
sipersso
commented
1 year ago Thanks @dianaafanador3. I'll follow along there. In the meantime, I managed to work around the build issues by downgrading Xcode to 14.0
sipersso
commented
1 year ago Unfortunately I see that now the file format is different between iOS and Android. iOS is running file format version 23, but these are not readable on Android/Java that is still on version 22. So unfortunately I am still blocked by this issue. Will there be a file format version 23 shortly for Android/Java? Realm kotlin has has been using the new format for a month.
I do want to switch the android app to use the Kotlin SDK eventually, but I think it might be a lot of work. At the same time, it is killing me still not being able to upgrade the iOS version (and get the dirty sync fixes that prevents corruption)
dianaafanador3
commented
1 year ago Hi @sipersso the Java team is working on an update with Core >= 13, a week or two at most they will probably have a release.
sipersso
commented
1 year ago Hi @sipersso the Java team is working on an update with Core >= 13, a week or two at most they will probably have a release.
Good news. Thanks for the reply.
How frequently does the bug occur?
All the time
Description
After updating the version, the xcode 14.1 bug was solved, but a new problem came out. ps. The real machine reports an error, but the emulator is normal.
Stacktrace & log output
Can you reproduce the bug?
Yes, always
Reproduction Steps
No response
Version
10.32.3
What SDK flavour are you using?
MongoDB Realm (i.e. Sync, auth, functions)
Are you using encryption?
Yes, using encryption
Platform OS and version(s)
iOS
Build environment
Xcode version: ... Dependency manager and version: ...