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
Does it happen in production or during dev/test? dev/test
Can the crash be reproduced by you? yes
Can you provide instructions for how we can reproduce it?
Crash log / stacktrace
/Users/runner/work/realm-dart/realm-dart/src/realm-core/src/realm/util/encrypted_file_mapping.cpp:1028: [realm-core-13.24.0] Assertion failed: new_size % (1ULL << m_page_shift) == 0
<backtrace not supported on this platform>
!!! IMPORTANT: Please report this at https://github.com/realm/realm-core/issues/new/choose2024-01-11 18:32:26.934833+0900 Runner[7905:2699530] /Users/runner/work/realm-dart/realm-dart/src/realm-core/src/realm/util/encrypted_file_mapping.cpp:1028: [realm-core-13.24.0] Assertion failed: new_size % (1ULL << m_page_shift) == 0
<backtrace not supported on this platform>
!!! IMPORTANT: Please report this at https://github.com/realm/realm-core/issues/new/choose
* thread #10, name = 'io.flutter.1.ui', stop reason = signal SIGABRT
frame #0: 0x00000001bb367bbc libsystem_kernel.dylib`__pthread_kill + 8
libsystem_kernel.dylib`:
-> 0x1bb367bbc <+8>: b.lo 0x1bb367bd8 ; <+36>
0x1bb367bc0 <+12>: stp x29, x30, [sp, #-0x10]!
0x1bb367bc4 <+16>: mov x29, sp
0x1bb367bc8 <+20>: bl 0x1bb36360c ; cerror_nocancel
Target 0: (Runner) stopped.#### Steps & Code to Reproduce
It didn't crash until last week. Since I updated the realm bundled yesterday, it crashes only on ios device. android, ios simulator does not have the problem.
if we are not using encryption, there is no problem.
file size is 48603136 byte
The text was updated successfully, but these errors were encountered:
SDK and version
SDK: �flutter
Version: 1.6.1
Observations
Crash log / stacktrace
It didn't crash until last week. Since I updated the realm bundled yesterday, it crashes only on ios device. android, ios simulator does not have the problem.
The text was updated successfully, but these errors were encountered: