Claus Rørbech

> Is there any update? @Ash-333 There is no fixed date for when the `2.0.0` release will go out, but until that you can use the `2.0.0-SNAPSHOT` following the instructions...

@bamsbamx Which version did you migrate from? And did you also remember to update the version of the realm-depenedencies?

The stacktrace looks like it could be related to #1598. The callback class reference did not create a global reference so the class could potentially be unloaded behind the scene...

@JorisBodin The above fix will be in `1.14.0`. It is already available in `1.14.0-SNAPSHOT` ([using snapshots](https://github.com/realm/realm-kotlin?tab=readme-ov-file#using-snapshots)) if you want to see if it changes anything already.

@JorisBodin This popped up from another user on 1.14.1. Are you still seeing this and have you been able to gather more insights on exactly when it is happening?

Core seems to support this by just not setting a path in the configuration. This is a bit problematic as `Configuration.path` is not nullable. Haven't tracked all the implications of...

Hi @alexmaryin. This looks a bit like if our plugin has not been applied or when of our internal properties have been stripped with Proguard on Android. Can you elaborate...

I guess there is also a ``` Incomplete hierarchy for class BaseRealmObject, unresolved classes [io.realm.kotlin.Deleteable] ``` and some methods related to inner classes. Can you verify that our library is...

@alexmaryin Then I guess you are most probably just missing some proguard rules. For Android there is a convention on how to supply library proguard files to consumers, but I...

@alexmaryin Thanks for the confirmation. I guess it is then a matter of adding the appropriate rules. Please start by adding rules for the immediate unresolvable classes (reported like the...