Codewize, I had to change one line of code on iOS and nothing on Android. Except for the initial crash on iOS, both apps seem to run fine!
What performance improvements are we talking about? Do you have any measurements on these?
Can’t wait to test out the freezed objects and to see what you have in store for the public beta of Atlas sync. I am not live with Realm Cloud and have decided to hold off on doing this until the beta.
I believe the best current docs are the release notes. If something there is unclear please let us know. But here is the gist:
As mentioned in this post we have updated all SDK’s (except .NET, which is lacking a little) with a new major version of the database. They all support Realm Cloud and we will continue to make important bug fixes in those, but don’t expect new features.
All SDK’s that supports the new MongoDB Realm Cloud is versioned “10.0.0-beta-*”. They contain both new data types and new features.
As for migration support from Realm Cloud to MongoDB Realm Cloud, we are working on that during this beta phase and will provide this as soon as we can.
Thanks for the prompt response. OK so in theory the 5.1.0 cocoa release should be compatible with an existing 4.x database and we should be able to upgrade to 5.1.0 and continue to sync with the existing Realm Cloud service.
Assuming that is the case is there someone I can contact regarding an error when trying to open a 4.x database with v5.1.0 - I am seeing a “Key already used” error from Realm. Happy to send you a copy of the database itself to test if required.
FYI it seems the RealmSwift 5.2.0 build fixes that previous issue - and you will be pleased to know it all seems work perfectly on Apple Silicon to - I just used Xcode to add the RealmSwift package. Great job guys - it’s blazingly fast too.