Kenneth Geisshirt
Kenneth Geisshirt
It looks like you didn't do `git submodule update --init --recursive` to pull in our dependencies (e.g., Realm Object Store).
We are going to add some kind of unique id in the near future, so we should wait until it has been introduced in core/sync.
It might be out of the scope of Realm as a library to make the decision to swallow exceptions. Other options exist within the React Native framework: * `ErrorUtils.setGlobalHandler()` -...
I agree that the correct behaviour is that a JS exception is thrown: a raw C++ exception is definitely not adding any value for the app developer.
After 6 months I still don't consider it a bug. Throwing an exception inside a callback is not best practise. Moreover, callbacks should have a `try`/`catch` and handle errors gracefully....
We will document the behaviour until we have a clear idea of how to solve it.
@somebody32 Thank you for your suggestion. I agree, that the current error message is a bit cryptic, and we should improve it.
When running your script, I can reproduce it using v2.29.1.
As we have a test of `uploadAllLocalChanges()`, we need to be able to reproduce it. Moreover, I routinely use the method (and its twin `downloadAllServerChanges()`) in small scripts and apps.
> I Tried with the latest "realm": "^12.8.0", and after login screen freezes I believe it is related to https://github.com/realm/realm-core/issues/7670. We have a fix, and we plan to release it...