Update dependency realm to v12 #6

renovate-bot · 2023-10-25T05:26:48Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
realm (source)	`^6.1.5` -> `^12.0.0`

Release Notes

realm/realm-js (realm)

`v12.13.2`

Compare Source

Fixed

Fixed build error on React Native Android when used with React Native 0.76, due to the merge of dynamic libraries. (#6908 since React Native v0.76.0).
Filtering notifications with backlink columns as last element could sometimes give wrong results (realm/realm-core#7530, since Realm JS v10.6.2-beta.1)
Fix crash during client app shutdown when Logger log level is set higher than Info. (realm/realm-core#7969, since Realm JS v12.3.1)
If File::rw_lock() fails to open a file the exception message does not contain the filename (realm/realm-core#7999, since Realm JS v6.1.0)
Fallback to hashed filename will fail if length of basename is between 240 and 250 (realm/realm-core#8007, since Realm JS v10.0.0)
Having a query with a number of predicates ORed together may result in a crash on some platforms (strict weak ordering check failing on iphone) (realm/realm-core#8028, since Realm JS v12.8.0)
The events library would attempt to upload backup files created as part of file format upgrades, causing backup copies of those backups to be made, looping until the maximum file name size was reached (realm/realm-core#8040, since Realm JS v10.18.0).

Compatibility

React Native >= v0.71.4
Realm Studio v15.0.0.
File format: generates Realms with format v24 (reads and upgrades file format v10).

Internal

Upgraded Realm Core from v14.12.0 to v14.13.1.

`v12.13.1`

Compare Source

Fixed

Fixed a build error on React Native iOS and Android from a change in the CallInvoker's invokeAsync call signature. (#6851 since v12.12.0 in combination with React Native >= v0.75.0).

Compatibility

React Native >= v0.71.4
Realm Studio v15.0.0.
File format: generates Realms with format v24 (reads and upgrades file format v10).

Internal

`v12.13.0`

Compare Source

Enhancements

Improved sync bootstrap performance. (realm/realm-core#7945 and realm/realm-core#7946)
Client reset cycle detection now checks if the previous recovery attempt was made by the same core version, and if not attempts recovery again. (realm/realm-core#7944)
Updated bundled OpenSSL version to 3.3.1. (realm/realm-core#7947)
Sync log statements now include the app services connection ID in their prefix (e.g Connection[1:<connection id>] Session[1]: log message). (realm/realm-core#7849)

Fixed

Fixed an Invalid column key exception when using an RQL "BETWEEN" query on an int or timestamp property across links. (realm/realm-core#7935, since v12.12.0)
Fixed conflict resolution bug which could sometimes cause an Invalid prior_size exception to prevent synchronization (realm/realm-core#7893, since v12.10.0)
Fixed bug which would prevent eventual consistency during conflict resolution. Affected clients would experience data divergence and potentially consistency errors as a result. (realm/realm-core#7955, since v12.10.0)
Fixed issues loading the native Realm libraries on Linux ARMv7 systems when they linked against our bundled OpenSSL resulting in errors like unexpected reloc type 0x03. (realm/realm-core#7947, since v12.7.0)
Sync client may report duplicate compensating write errors. (realm/realm-core#7708, since v12.10.0)
String serialization of timestamps with a sufficiently large timestamp value could overflow an int causing undefined behavior, causing potentially bad values for the month/day/year values in stringified dates. (realm/realm-core#7934)
App subscription callback was getting fired before the user profile was retrieved on login, leading to an empty user profile when using the callback. (realm/realm-core#7889, since v12.9.0)

Compatibility

React Native >= v0.71.4
Realm Studio v15.0.0.
File format: generates Realms with format v24 (reads and upgrades file format v10).

Internal

Upgraded Realm Core from v14.11.0 to v14.12.0.

`v12.12.1`

Compare Source

Fixed

Fixed compiler error when building binding for React Native iOS: "'React-featureflags/react/featureflags/ReactNativeFeatureFlags.h' file not found" (#6808, since v12.12.0)

Compatibility

React Native >= v0.71.4
Realm Studio v15.0.0.
File format: generates Realms with format v24 (reads and upgrades file format v10).

Internal

Removed an unused import in the binding for React Native Android. (#6808, since v12.12.0)

`v12.12.0`

Compare Source

Deprecations

The callback for SyncSession.addProgressNotification taking transferred and transferable arguments is deprecated and will be removed. See Enhancements below for the new callback supporting both Flexible Sync and Partition-Based Sync. (#6743)
AppConfiguration.app is no longer used by Atlas Device Sync. It will be removed in future SDK releases and should not be used. (#6785)

Enhancements

Added support for "bridgeless" React Native on iOS and Android, a part of the "new architecture". (#6737)
Added progress notifications support for Flexible Sync using an estimate as the new callback argument. The estimate is roughly equivalent to an estimated value of transferred / transferable in the deprecated Partition-Based Sync callback. (#6743)

realm.syncSession?.addProgressNotification(
  ProgressDirection.Upload,
  ProgressMode.ReportIndefinitely,
  (estimate) => console.log(`progress: ${estimate}/1.0`)
);

It is no longer an error to set a base url for an App with a trailing slash - for example, https://services.cloud.mongodb.com/ instead of https://services.cloud.mongodb.com - before this change that would result in a 404 error from the server. (realm/realm-core#7791)
Performance has been improved for range queries on integers and timestamps when using the BETWEEN operator. (realm/realm-core#7785)
On Windows devices Device Sync will additionally look up SSL certificates in the Windows Trusted Root Certification Authorities certificate store when establishing a connection. (realm/realm-core#7882)
Role and permissions changes no longer require a client reset to update the Realm on-device. (realm/realm-core#7440)

Fixed

Opening an Flexible Sync Realm asynchronously may not wait to download all data. (realm/realm-core#7720, since v10.12.0)
Clearing a list of mixed in an upgraded file would lead to an assertion failing. (realm/realm-core#7771, since 12.7.0-rc.0)
Sync client can crash if a session is resumed while the session is being suspended. (realm/realm-core#7860, since v10.18.0)
If a sync session is interrupted by a disconnect or restart while downloading a bootstrap, stale data from the previous bootstrap may be included when the session reconnects and downloads the bootstrap. This can lead to objects stored in the database that do not match the actual state of the server and potentially leading to compensating writes. (realm/realm-core#7827, since v10.18.0)
Fixed unnecessary server roundtrips when there is no download to acknowledge. (realm/realm-core#2129, since v12.10.0)
Realm.App.Sync.SyncSession#uploadAllLocalChanges() was inconsistent in how it handled commits which did not produce any changesets to upload. Previously it would sometimes complete immediately if all commits waiting to be uploaded were empty, and at other times it would wait for a server roundtrip. It will now always complete immediately. (realm/realm-core#7796)
Realm#writeCopyTo() on an encrypted Realm without explicitly specifying a new encryption key would only work if the old key happened to be a valid nul-terminated string. (realm/realm-core#7842, since v12.10.0).
You could get unexpected merge results when assigning to a nested collection. (realm/realm-core#7809, since v12.7.0-rc.0)
When mapTo is used to have an alias for a property name, Realm.Results#sorted() doesn't recognize the alias leading to errors like Cannot sort on key path 'NAME': property 'PersonObject.NAME' does not exist. (#6779, since v11.2.0)
A mixed property with a collection could sometimes end up with a combination of values assigned by different clients. (realm/realm-core#7809, since v12.9.0)
Fixed removing backlinks from the wrong objects if the link came from a nested list, nested dictionary, top-level dictionary, or list of mixed, and the source table had more than 256 objects. This could manifest as array_backlink.cpp:112: Assertion failed: int64_t(value >> 1) == key.value when removing an object. (realm/realm-core#7594, since v10.6.0)
Fixed a bug when removing an object from a nested collection could lead to an assert with the message array.cpp:319: Array::move() Assertion failed: begin <= end [2, 1]. (realm/realm-core#7839, since v12.9.0)

Compatibility

React Native >= v0.71.4
Realm Studio v15.0.0.
File format: generates Realms with format v24 (reads and upgrades file format v10).

Internal

Adding a CallInvoker-based scheduler for Core on React Native and removing the "flush ui queue" workaround. (#6791)
Refactors throwing uncaught exceptions from callbacks dispatched onto the event loop from C++ on React Native. (#6772)
Upgraded Realm Core from v14.10.0 to v14.11.0. (#6744)

`v12.11.1`

Compare Source

Fixed

path option in the Realm configuration not being set when using a synced Realm. (#6754, since v12.8.0). Note: if you have been using a custom path configuration with your synced Realm, this fix will lead to a re-download of its data in the custom path.

Compatibility

React Native >= v0.71.4
Realm Studio v15.0.0.
File format: generates Realms with format v24 (reads and upgrades file format v10).

`v12.11.0`

Compare Source

Enhancements

Building for iOS and Android has been optimized for compatibility with future React Native versions, by deferring compilation of JSI dependent code to the dependent app's build. (#6650)

Compatibility

React Native >= v0.71.4
Realm Studio v15.0.0.
File format: generates Realms with format v24 (reads and upgrades file format v10).

`v12.10.0`

Compare Source

Enhancements

Report the originating error that caused a client reset to occur. (realm/realm-core#6154)
Reduce the size of the local transaction log produced by creating objects, improving the performance of insertion-heavy transactions. (realm/realm-core#7734)
A counter presentation data type has been introduced. The int data type can now be used as a logical counter for performing numeric updates that need to be synchronized as sequentially consistent events rather than individual reassignments of the number. (#6694)
- See the API docs for more information about the usage, or get a high-level introduction about counters in the documentation.

class MyObject extends Realm.Object {
  _id!: BSON.ObjectId;
  counter!: Realm.Types.Counter;

  static schema: ObjectSchema = {
    name: "MyObject",
    primaryKey: "_id",
    properties: {
      _id: { type: "objectId", default: () => new BSON.ObjectId() },
      counter: "counter",
      // or: counter: { type: "int", presentation: "counter" },
    },
  };
}

const realm = await Realm.open({ schema: [MyObject] });
const object = realm.write(() => {
  return realm.create(MyObject, { counter: 0 });
});

realm.write(() => {
  object.counter.increment();
  object.counter.value; // 1
  object.counter.decrement(2);
  object.counter.value; // -1
});

Fixed

After compacting, a file upgrade would be triggered. This could cause loss of data for synced Realms. (realm/realm-core#7747, since 12.7.0-rc.0)
The function immediatelyRunFileActions was not added to the bindgen's opt-list. This could lead to the error TypeError: app.internal.immediatelyRunFileActions is not a function. (#6708, since v12.8.0)
Encrypted files on Windows had a maximum size of 2 GB even on x64 due to internal usage of off_t, which is a 32-bit type on 64-bit Windows. (realm/realm-core#7698, since the introduction of encryption support on Windows - likely in v1.11.0)
Tokenizing strings for full-text search could lead to undefined behavior. (realm/realm-core#7698, since v11.3.0-rc.0)
A non-streaming progress notifier would not immediately call its callback after registration. Instead you would have to wait for a download message to be received to get your first update - if you were already caught up when you registered the notifier you could end up waiting a long time for the server to deliver a download that would call/expire your notifier. (#7627, since v12.8.0)

Compatibility

React Native >= v0.71.4
Realm Studio v15.0.0.
File format: generates Realms with format v24 (reads and upgrades file format v10).

Internal

Upgraded Realm Core from v14.7.0 to v14.10.0. (#6701)
Added privacy manifest for Apple App Store. First released in v12.8.1-alpha.0 only. (#6638)

`v12.9.0`

Compare Source

Enhancements

A mixed value can now hold a Realm.List and Realm.Dictionary with nested collections. Note that Realm.Set is not supported as a mixed value. (#6613)

class CustomObject extends Realm.Object {
  value!: Realm.Types.Mixed;

  static schema: ObjectSchema = {
    name: "CustomObject",
    properties: {
      value: "mixed",
    },
  };
}

const realm = await Realm.open({ schema: [CustomObject] });

// Create an object with a dictionary value as the Mixed
// property, containing primitives and a list.
const realmObject = realm.write(() => {
  return realm.create(CustomObject, {
    value: {
      num: 1,
      string: "hello",
      bool: true,
      list: [
        {
          string: "world",
        },
      ],
    },
  });
});

// Accessing the collection value returns the managed collection.
const dictionary = realmObject.value;
expectDictionary(dictionary);
const list = dictionary.list;
expectList(list);
const leafDictionary = list[0];
expectDictionary(leafDictionary);
console.log(leafDictionary.string); // "world"

// Update the Mixed property to a list.
realm.write(() => {
  realmObject.value = [1, "hello", { newKey: "new value" }];
});

// Useful custom helper functions. (Will be provided in a future release.)
function expectList(value: unknown): asserts value is Realm.List {
  if (!(value instanceof Realm.List)) {
    throw new Error("Expected a 'Realm.List'.");
  }
}
function expectDictionary(value: unknown): asserts value is Realm.Dictionary {
  if (!(value instanceof Realm.Dictionary)) {
    throw new Error("Expected a 'Realm.Dictionary'.");
  }
}

Fixed

Inserting the same typed link to the same key in a dictionary more than once would incorrectly create multiple backlinks to the object. This did not appear to cause any crashes later, but would have affecting explicit backlink count queries (eg: ...@links.@count) and possibly notifications (realm/realm-core#7676 since v12.7.1).
Having links in a nested collections would leave the file inconsistent if the top object is removed. (realm/realm-core#7657, since v12.7.0)
Automatic client reset recovery would crash when recovering AddInteger instructions on a Mixed property if its type was changed to non-integer (realm/realm-core#7683, since v10.18.0).

Compatibility

React Native >= v0.71.4
Realm Studio v15.0.0.
File format: generates Realms with format v24 (reads and upgrades file format v10).

Internal

Upgraded Realm Core from v14.6.2 to v14.7.0.
Upgraded @trunk/launcher from v1.3.0 to v1.3.1 to support Apple's versioning scheme for macOS.

`v12.8.1`

Compare Source

Fixed

Fixed a crash experienced on React Native when accessing Realm.deleteFile, Realm.exists, Realm.schemaVersion, Realm.determinePath, Realm.transformConfig and User#isLoggedIn. (#6662, since v12.8.0)
Accessing Realm.App#currentUser from within a notification produced by Realm.App.switchUser (which includes notifications for a newly logged in user) would deadlock. (realm/realm-core#7670, since v12.8.0)
Fixed a bug when running an IN query on a string/int/uuid/objectId property that was indexed. (realm/realm-core#7642 since v12.8.0)
Fixed a bug when running an IN query on an int property where double/float parameters were ignored. (realm/realm-core#7642 since v12.8.0)

Compatibility

React Native >= v0.71.4
Realm Studio v15.0.0.
File format: generates Realms with format v24 (reads and upgrades file format v10).

Internal

Upgraded Realm Core from v14.6.1 to v14.6.2 + commits 5ba02142131efa3d97eda770ce33a85a2a085202 and 5462d47998b86459d328648c8057790a7b92af20.

`v12.8.0`

Compare Source

Deprecations

MetadataMode.NoMetadata is deprecated and will be removed. The new name is MetadataMode.InMemory.

Enhancements

Experimental feature: The new instance members App.baseUrl and App.updateBaseUrl() allow for retrieving and updating the base URL currently used for requests sent to Atlas App Services. These APIs are only available after importing "realm/experimental/base-url". (#6518)
Improved performance of "chained OR equality" queries for uuid/objectId types and RQL parsed IN queries on string/int/uuid/objectId types. (realm/realm-dotnet#3566, since the introduction of these types)

Fixed

Fixed a bug when running an IN query (or a query of the pattern x == 1 OR x == 2 OR x == 3) when evaluating on a string property with an empty string in the search condition. Matches with an empty string would have been evaluated as if searching for a null string instead. (realm/realm-core#7628, since v10.0.0)
App.allUsers() included logged out users only if they were logged out while the App instance existed. It now always includes all logged out users. (realm/realm-core#7300)
Deleting the active user left the active user unset rather than selecting another logged-in user as the active user like logging out and removing users did. (realm/realm-core#7300)
Fixed several issues around encrypted file portability (copying a "bundled" encrypted Realm from one device to another):
- Fixed Assertion failed: new_size % (1ULL << m_page_shift) == 0 when opening an encrypted Realm less than 64Mb that was generated on a platform with a different page size than the current platform. (#realm/realm-core#7322, since v12.0.0-rc.3)
- Fixed an exception thrown when opening a small (<4k of data) Realm generated on a device with a page size of 4k if it was bundled and opened on a device with a larger page size. (since v1.0.0)
- Fixed an issue during a subsequent open of an encrypted Realm for some rare allocation patterns when the top ref was within ~50 bytes of the end of a page. This could manifest as an exception or as an assertion encrypted_file_mapping.hpp:183: Assertion failed: local_ndx < m_page_state.size(). (realm/realm-core#7319)
Schema initialization could hit an assertion failure if the sync client applied a downloaded changeset while the Realm file was in the process of being opened. (realm/realm-core#7041, since v10.8.0)
Queries using query paths on mixed values returns inconsistent results. (realm/realm-core#7587, since v12.7.0-rc.0)

Known issues

Missing initial download progress notification when there is no active downloads. (realm/realm-core#7627)

Compatibility

React Native >= v0.71.4
Realm Studio v15.0.0.
File format: generates Realms with format v24 (reads and upgrades file format v10.

Internal

Upgraded Realm Core from v14.5.1 to v14.6.1.
The metadata disabled mode (MetadataMode.NoMetadata) has been replaced with an in-memory metadata mode (MetadataMode.InMemory) which performs similarly and doesn't work weirdly differently from the normal mode. The new mode is intended for testing purposes, but should be suitable for production usage if there is a scenario where metadata persistence is not needed. (realm/realm-core#7300)

`v12.7.1`

Compare Source

Fixed

Fixed a crash when integrating removal of already removed dictionary key. (realm/realm-core#7488, since v10.0.0)
Removed incorrect privacy manifest for iOS. (#6624, since v12.7.0)

Compatibility

React Native >= v0.71.4
Realm Studio v15.0.0.
File format: generates Realms with format v24 (reads and upgrades file format v10 or later).

Internal

Upgraded Realm Core from v14.5.1 to v14.5.2. (#6628)
Update URLs to documentation.

`v12.7.0`

Compare Source

[!NOTE]
This version bumps the Realm file format to version 24. It is not possible to downgrade to earlier versions. Older files will automatically be upgraded to the new file format. Files created by Realm JavaScript prior to v6.0.0, might not be upgradeable. Only Realm Studio 15.0.0 or later will be able to open the new file format.

[!NOTE]
This version communicates with Atlas Device Services through a different URL (https://services.cloud.mongodb.com). While we consider this an internal detail of the SDK, you might need to update rules in firewalls or other configuration that you've used to limit connections made by your app.

Enhancements

Added iOS Privacy Manifest. (#6547
Updated bundled OpenSSL version to 3.2.0. (realm/realm-core#7303)
Improved performance of object notifiers with complex schemas by ~20%. (realm/realm-core#7424)
Improved performance with very large number of notifiers by ~75%. (realm/realm-core#7424)
Improved performance of aggregate operations on Dictionaries of objects, particularly when the dictionaries are empty. (realm/realm-core#7418
Property keypath in RQL can be substituted with value given as argument. Use $P<i> in query string. (realm/realm-core#7033)
You can now use query substitution for the @type argument. (realm/realm-core#7289)
Storage of Decimal128 properties has been optimized so that the individual values will take up 0 bits (if all nulls), 32 bits, 64 bits or 128 bits depending on what is needed. ([realm/realm-core#6111]https://github.com/realm/realm-core/pull/6111))
Querying a specific entry in a collection (in particular 'first and 'last') is supported. (realm/realm-core#4269)
Index on list of strings property now supported (realm/realm-core#7142)
You can set the threshold levels for trace output on individual categories. (realm/realm-core#7004)
Improved performance of RQL queries on a non-linked string property using >, >=, <, <= operators and fixed behavior that a null string should be evaluated as less than everything, previously nulls were not matched. (realm/realm-core#3939)
Added support for using aggregate operations on Mixed properties in queries. (realm/realm-core#7398)
Improved file compaction performance on platforms with page sizes greater than 4k (for example arm64 Apple platforms) for files less than 256 pages in size. (realm/realm-core#7492)
Added the ability to set the log level for one or more categories via Realm.setLogLevel. (#6560)
Added detection and better instructions when imported from the Expo Go app. (#6523)

Fixed

Aligned Dictionaries to Lists and Sets when they get cleared. (#6205, since v10.3.0-rc.1)
Fixed equality queries on a Mixed property with an index possibly returning the wrong result if values of different types happened to have the same StringIndex hash. (realm/realm-core#6407, since v10.5.0-beta.1)
@count/@size is now supported for Mixed properties. (realm/realm-core#7280, since v10.0.0)
Fixed queries like indexed_property == NONE {x} which mistakenly matched on only x instead of not x. This only applies when an indexed property with equality (==, or IN) matches with NONE on a list of one item. If the constant list contained more than one value then it was working correctly. (realm/realm-java#7862, since v10.20.0)
Uploading the changesets recovered during an automatic client reset recovery may lead to Bad server version errors and a new client reset. (realm/realm-core#7279, since v12.5.0)
Fixed crash in full text index using prefix search with no matches (realm/realm-core#7309, since v12.2.0)
Fixed a race condition when backing up Realm files before a client reset which could have lead to overwriting an existing file. (realm/realm-core#7341)
Fixed a bug when removing items from a list that could result in invalidated links becoming visible which could cause crashes or exceptions when accessing those list items later on. This affects synced Realms where another client had previously removed a list with over 1000 items in it, and then further local removals from the same list caused the list to have fewer than 1000 items. (#7414, since v10.0.0)
Fixed opening a Realm with cached user while offline results in fatal error and session does not retry connection. (#6554 and #6558, since v12.6.0)
Fixed sorting order of strings to use standard unicode codepoint order instead of grouping similar English letters together. A noticeable change will be from "aAbBzZ" to "ABZabz". (realm/realm-core#2573)
data and string are now strongly typed for comparisons and queries. This change is especially relevant when querying for a string constant on a Mixed property, as now only strings will be returned. If searching for data is desired, then that type must be specified by the constant. In RQL the new way to specify a binary constant is to use mixed = bin('xyz') or mixed = binary('xyz'). (realm/realm-core#6407)
Fixed diverging history due to a bug in the replication code when setting default null values (embedded objects included). (realm/realm-core#7536)
Null pointer exception may be triggered when logging out and async commits callbacks not executed. (realm/realm-core#7434, since v12.6.0)
Fixed a bug which caused crashes when reloading React Native apps. (#6579, since v12.0.0)

Compatibility

React Native >= v0.71.4
Realm Studio v15.0.0.
File format: generates Realms with format v24 (reads and upgrades file format v10 or later).

Internal

The base URL used to communicate with the Atlas App Services was changed from "https://realm.mongodb.com" to "https://services.cloud.mongodb.com". (realm/realm-core#7534).
Upgraded Realm Core from v13.26.0 to v14.5.1. (#6499, #6541, #6568, #6572, #6599, and #6610)
Publish releases with provenance statements.
Use CMake v3.29.2 and Node v20.11.1 on Github Actions.

`v12.6.2`

Compare Source

Fixed

Fixed binding abstraction to allow access of certain properties ($$typeof for now) prior to its injection. (#6522, since v12.6.1)
Added a missing dependency on path-browserify. (#6522, since v12.6.1)

Internal

Using Realm Core v13.26.0.

`v12.6.1`

Compare Source

Fixed

Fixed User#callFunction to correctly pass arguments to the server. Previously they would be sent as an array, so if your server-side function used to handle the unwrapping of arguments, it would need an update too. The "functions factory" pattern of calling user.functions.sum(1, 2, 3) wasn't affected by this bug. Thanks to @deckyfx for finding this and suggesting the fix! (#6447, since v12.0.0)

Compatibility

React Native >= v0.71.4
Realm Studio v14.0.0.
File format: generates Realms with format v23 (reads and upgrades file format v5 or later for non-synced Realm, upgrades file format v10 or later for synced Realms).

Internal

Fix Cocoapods to version 1.14.3 on Github Actions.
Migrated bingen from util::Optional to std::optional.
Upgrading @realm/fetch to the newly released v0.1.1 and no longer bundling it into the SDK package.
SDK package is no longer using Rollup, but instead using bare tsc utilizing TypeScript project references. (#6492)

`v12.6.0`

Compare Source

Enhancements

Added an optional fetch parameter to the AppConfiguration. Use this to specify a custom implementation of the fetch function used by the app to perform network requests.

Fixed

Handle EOPNOTSUPP when using posix_fallocate() and fallback to manually consume space. This should enable android users to open a Realm on restrictive file systems. (#6349, since v12.2.0)
Application may crash with incoming_changesets.size() != 0 when a download message is mistaken for a bootstrap message. This can happen if the synchronization session is paused and resumed at a specific time. (realm/realm-core#7238, since v10.12.0)
Fixed errors complaining about missing symbols such as __atomic_is_lock_free on ARMv7 Linux. (realm/realm-core#7257)

Compatibility

React Native >= v0.71.4
Realm Studio v14.0.0.
File format: generates Realms with format v23 (reads and upgrades file format v5 or later for non-synced Realm, upgrades file format v10 or later for synced Realms).

Internal

Upgraded Realm Core from v13.25.1 to v13.26.0. (#6403)
Bumping the required MacOS version to 10.13.

`v12.5.1`

Compare Source

Fixed

Accessing the providerType on a UserIdentity via User.identities always yielded undefined. Thanks to @joelowry96 for pinpointing the fix.
Bad performance of initial Sync download involving many backlinks. (realm/realm-core#7217, since v10.0.0)

Compatibility

React Native >= v0.71.4
Realm Studio v14.0.0.
File format: generates Realms with format v23 (reads and upgrades file format v5 or later for non-synced Realm, upgrades file format v10 or later for synced Realms).

Internal

Upgraded Realm Core from v13.25.0 to v13.25.1. (#6335)

`v12.5.0`

Compare Source

Enhancements

Added an optional third keyPaths argument to the addListener methods of Collection and Object. Use this to indicate a lower bound on the changes relevant for the listener. This is a lower bound, since if multiple listeners are added (each with their own "key paths") the union of these key-paths will determine the changes that are considered relevant for all listeners registered on the object or collection. In other words: A listener might fire more than the key-paths specify, if other listeners with different key-paths are present. (#6285)
```
// Adding a listener that will fire only on changes to the `location` property (if no other key-path listeners are added to the collection).
cars.addListener((collection, changes) => {
  console.log("A car location changed");
}, ["location"]);
```
Exceptions thrown during bootstrap application will now be surfaced to the user via the sync error handler rather than terminating the program with an unhandled exception. (realm/realm-core#7197)

Fixed

Exceptions thrown during bootstrap application could crash the sync client with an !m_sess assertion. (realm/realm-core#7196, since v10.18.0)
If a SyncSession was explicitly resumed via reconnect() while it was waiting to auto-resume after a non-fatal error and then another non-fatal error was received, the sync client could crash with a !m_try_again_activation_timer assertion. (realm/realm-core#6961, since device sync was introduced)
Adding the same callback function as a listener on a Collection or Object used to be undefined behavior. Now it throws, which results in runtime errors that can be resolved by ensuring that the callback is only added once per object. (#6310)

Compatibility

React Native >= v0.71.4
Realm Studio v14.0.0.
File format: generates Realms with format v23 (reads and upgrades file format v5 or later for non-synced Realm, upgrades file format v10 or later for synced Realms).

Internal

Upgraded Realm Core from v13.24.1 to v13.25.0. (#6324)

`v12.4.0`

Compare Source

Enhancements

Exporting a RealmEventName type. (#6300)
Automatic client reset recovery now preserves the original division of changesets, rather than combining all unsynchronized changes into a single changeset. (realm/realm-core#7161)
Automatic client reset recovery now does a better job of recovering changes when changesets were downloaded from the server after the unuploaded local changes were committed. If the local Realm happened to be fully up to date with the server prior to the client reset, automatic recovery should now always produce exactly the same state as if no client reset was involved. (realm/realm-core#7161)
Improved the experience of logging Realm.Object and Realm.Collection objects on Node.js, by providing a custom "inspect" symbol. (#2758)

Fixed

When mapTo is used on a property of type List, an error like Property 'test_list' does not exist on 'Task' objects occurs when trying to access the property. (#6268, since v12.0.0)
Fixed bug where apps running under JavaScriptCore on Android will terminate with the error message No identifiers allowed directly after numeric literal. (#6194, since v12.2.0)
When an object had an embedded object as one of its properties, updating that property to null or undefined did not update the property in the database. (#6280, since v12.0.0)
Fixed download of platform + arch specific prebuilt binaries when building an Electron app using electron-builder. (#3828)
Notification listeners on a Dictionary would only fire when the dictionary itself changed (via inserts or deletions) but not when changes were made to the underlying objects. (#6310, since v12.0.0)
Fixed deadlock which occurred when accessing the current user from the App from within a callback from the User listener. (realm/realm-core#7183, since v12.2.1)
Errors encountered while reapplying local changes for client reset recovery on partition-based sync Realms would result in the client reset attempt not being recorded, possibly resulting in an endless loop of attempting and failing to automatically recover the client reset. Flexible sync and errors from the server after completing the local recovery were handled correctly. (realm/realm-core#7149, since v10.3.0-rc.1)
During a client reset with recovery when recovering a move or set operation on a List<Object> or List<Mixed> that operated on indices that were not also added in the recovery, links to an object which had been deleted by another client while offline would be recreated by the recovering client. But the objects of these links would only have the primary key populated and all other fields would be default values. Now, instead of creating these zombie objects, the lists being recovered skip such deleted links. (realm/realm-core#7112 since the beginning of client reset with recovery in v10.18.0)
During a client reset recovery a Set of links could be missing items, or an exception could be thrown that prevents recovery e.g., Requested index 1 calling get() on set 'source.collection' when max is 0. (realm/realm-core#7112, since the beginning of client reset with recovery in v10.18.0)
Calling sort() or distinct() on a LnkSet that had unresolved links in it would produce duplicate indices. (realm/realm-core#7112, since the beginning of client reset with recovery in v10.18.0)
Automatic client reset recovery would duplicate insertions in a list when recovering a write which made an unrecoverable change to a list (i.e. modifying or deleting a pre-existing entry), followed by a subscription change, followed by a write which added an entry to the list. (realm/realm-core#7155, since v10.19.4)
Fixed several causes of "decryption failed" exceptions that could happen when opening multiple encrypted Realm files in the same process while using Apple/linux and storing the Realms on an exFAT file system. (realm/realm-core#7156, since v1.0.0)
If the very first open of a flexible sync Realm triggered a client reset, the configuration had an initial subscriptions callback, both before and after reset callbacks, and the initial subscription callback began a read transaction without ending it (which is normally going to be the case), opening the frozen Realm for the after reset callback would trigger a BadVersion exception. (realm/realm-core#7161, since v10.19.4)

Compatibility

React Native >= v0.71.4
Realm Studio v14.0.0.
File format: generates Realms with format v23 (reads and upgrades file format v5 or later for non-synced Realm, upgrades file format v10 or later for synced Realms).

Internal

Upgraded Realm Core from v13.23.4 to v13.24.1. (#6311)

`v12.3.1`

Compare Source

Fixed

Fixed FLX subscriptions not being sent to the server if the session was interrupted during bootstrapping. (realm/realm-core#7077, since v10.12.0)
Fixed FLX subscriptions not being sent to the server if an upload message was sent immediately after a subscription was committed. (realm/realm-core#7076, since v12.3.0)
Fixed application crash with KeyNotFound exception when subscriptions are marked complete after a client reset. (realm/realm-core#7090, since v10.19.0)
Fixed a crash at a very specific time during a DiscardLocal client reset on a FLX Realm could leave subscriptions in an invalid state. (realm/realm-core#7110, since v10.19.4)
Fixed an error "Invalid schema change (UPLOAD): cannot process AddColumn instruction for non-existent table" when using automatic client reset with recovery in dev mode to recover schema changes made locally while offline. (realm/realm-core#7042)
When place an embedded object would create a new object and keep the original object too. (#6239, since v12.0.0)
When setting an embedded object in a Realm.List by index, the new object would be inserted at the end rather than replacing the existing object at the given index. (#6239, since v12.0.0)
When SyncConfiguration.clientReset was undefined, no client reset mode was set which could lead to an app crash with the message m_mode != ClientResyncMode::Manual. The default mode is now RecoverUnsyncedChanges and no callbacks are defined. (#6260, since v12.0.0)
Fixed writing the realm-constants.json file used for analytics / telemetry, which used to cause errors such as Unable to resolve module ../realm-constants.json for users installing the package into a mono-repo. We're now storing this information in the realm/package.json file instead. (#6144, since v12.0.0-rc.2)

Compatibility

React Native >= v0.71.4
Realm Studio v14.0.0.
File format: generates Realms with format v23 (reads and upgrades file format v5 or later for non-synced Realm, upgrades file format v10 or later for synced Realms).

Internal

Upgraded Realm Core from v13.23.2 to v13.23.4. (#6234 and #6253)

`v12.3.0`

Compare Source

Enhancements

Allow asymmetric objects to contain fields with non-embedded (top-level) links (rather than only embedded links). (realm/realm-core#7003)

Fixed

The onBefore, onAfter, and onFallback client reset callbacks were not called. (#6201, since v12.0.0)
Symbol.unscopables has been implemented on the base class of Realm.Results, Realm.List, and Realm.Set. (#6215)
Deleting an object in an asymmetric table would cause a crash. (realm/realm-kotlin#1537, since v10.19.0)
Updating subscriptions did not trigger Realm auto-refreshes, sometimes resulting in async refresh hanging until another write was performed by something else. (realm/realm-core#7031)
Fix inter-process locking for concurrent Realm file access resulting in an inter-process deadlock on FAT32/exFAT file systems. (realm/realm-core#6959)

Compatibility

React Native >= v0.71.4
Realm Studio v14.0.0.
File format: generates Realms with format v23 (reads and upgrades file format v5 or later for non-synced Realm, upgrades file format v10 or later for synced Realms).

Internal

Some disabled tests for client reset (partition based sync) have been enabled. (#6201
Upgraded Realm Core from v13.22.0 to v13.23.2. (#6220)

`v12.2.1`

Compare Source

Deprecations

Realm.User.providerType is deprecated, and will be remove in next major version. Use Realm.User.identities instead.

Fixed

Outside migration functions, it is not possible to change the value of a primary key. (#6161, since v12.0.0)
Receiving a write_not_allowed error from the server would have led to a crash. (realm/realm-core#6978, since v11.5.0)
If querying over a geospatial dataset that had some objects with a type property set to something other than Point (case insensitive) an exception would have been thrown. Instead of disrupting the query, those objects are now just ignored. (realm/realm-core#6989, since v12.0.0)
If a user was logged out while an access token refresh was in progress, the refresh completing would mark the user as logged in again and the user would be in an inconsistent state. (realm/realm-core#6837, since v10.0.0)
Logging in a single user using multiple auth providers created a separate Realm.User per auth provider. This mostly worked, but had some quirks:
- Sync sessions would not necessarily be associated with the specific Realm.User used to create them. As a result, querying a user for its sessions could give incorrect results, and logging one user out could close the wrong sessions.
- Existing local synchronized Realm files created using version of Realm from August - November 2020 would sometimes not be opened correctly and would instead be redownloaded.
- Removing one of the Realm.Users would delete all local Realm files for all Realm.Users for that user.
- Deleting the server-side user via one of the Realm.Users left the other Realm.Users in an invalid state.
- A Realm.User which was originally created via anonymous login and then linked to an identity would still be treated as an anonymous users and removed entirely on logout.
- realm/realm-core#6837, since v10.0.0

Compatibility

React Native >= v0.71.4
Realm Studio v14.0.0.
File format: generates Realms with format v23 (reads and upgrades file format v5 or later for non-synced Realm, upgrades file format v10 or later for synced Realms).

Internal

Upgraded Realm Core from v13.20.1 to v13.22.0. (#6158)

`v12.2.0`

Compare Source

Deprecations

Realm.App.Sync.reconnect(app) has been deprecated and will be removed in the next major version. You can use Realm.App.Sync.Session.reconnect() instead.

Enhancements

Added Realm.Sync.Session.reconnect() to help force a reconnection to Atlas Device Sync. (#6123)
Added Realm.App.AppConfiguration.metaData which

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Update dependency realm to v12

d30d6a3

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update dependency realm to v12 #6

Update dependency realm to v12 #6

renovate-bot commented Oct 25, 2023 •

edited

Loading

Update dependency realm to v12 #6

Are you sure you want to change the base?

Update dependency realm to v12 #6

Conversation

renovate-bot commented Oct 25, 2023 • edited Loading

Release Notes

Fixed

Compatibility

Internal

Fixed

Compatibility

Internal

Enhancements

Fixed

Compatibility

Internal

Fixed

Compatibility

Internal

Deprecations

Enhancements

Fixed

Compatibility

Internal

Fixed

Compatibility

Enhancements

Compatibility

Enhancements

Fixed

Compatibility

Internal

Enhancements

Fixed

Compatibility

Internal

Fixed

Compatibility

Internal

Deprecations

Enhancements

Fixed

Known issues

Compatibility

Internal

Fixed

Compatibility

Internal

Enhancements

Fixed

Compatibility

Internal

Fixed

Internal

Fixed

Compatibility

Internal

Enhancements

Fixed

Compatibility

Internal

Fixed

Compatibility

Internal

Enhancements

Fixed

Compatibility

Internal

Enhancements

Fixed

Compatibility

Internal

Fixed

Compatibility

Internal

Enhancements

Fixed

Compatibility

Internal

Deprecations

renovate-bot commented Oct 25, 2023 •

edited

Loading