Claus Rørbech

@jakobkmar Thanks for the report and temporary workaround. We will investigate how to enforce our minimal required version along with working with other libraries. Do you mind sharing any immediate...

I updated the implementation to use the C-API for creating the custom scheduler in #688, but `realm_clone` is only updating the reference count, so not sufficient to make an actual...

Just for reference. Tried out with `realm_clone`, but it fails with: ``` signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x138 Cause: null pointer dereference rax 0000000000000138 rbx 000072b77f746c00 rcx...

Still some left overs. Ex. getting access to the default scheduler with https://github.com/realm/realm-kotlin/blob/master/packages/jni-swig-stub/src/main/jni/realm_api_helpers.cpp#L281

Closing as outdated as we have now moved on to the new memory model.

I don't think we should add a SDK-wide `@Beta`-annotation unless we see very good reasons for it. I would much rather do feature-based annotations that utilizes Kotlin's [RequiresOptIn](https://kotlinlang.org/docs/opt-in-requirements.html)-mechanism. This will...

The garbage collector for the new memory model should be able to detect those cycles now, so should probably be able to reenable the test.

This is fixed by #1513 available from the `1.12.0` release.

Hi @jhonnyinstacart. Could this somehow be related to testing scenarios of upgrading or downgrading the application? The user metadata is stored in an internal realm-file. The schema of this realm...

Hi @jhonnyinstacart. I have tried replicating your issue by updating and downgrading across 10.16.2 and 10.17.0. Upgrading works, but downgrading is not possible because of an internal check in core...