Problem After Recently Updating Realm JS

[s1tony]

I have been successfully developing a React Native application using Realm and specifically Flexible Sync. Things were working until recently, after updating to Realm JavaScript v10.19.1.

I am receiving the following message back when attempting to call subscriptions.update:

TypeError: undefined is not an object (evaluating '_$$_REQUIRE(_dependencyMap[0], "@realm.io/common").symbols.PROXY_TARGET')

I am developing on a Windows 10 box for the Android platform.

Any ideas?

[hachther]

The issue here is the version of @realm.io/common.
The version installed by realm is "0.1.1" but the needed version is "0.1.2".

See below I fixed my issue:

yarn add @realm.io/common
rm -rf node_modules/realm/node_modules/@realm.io

[tomduncalf]

Hi @s1tony @hachther, thanks for the report.

It looks like we missed updating the dependency in the package.json, sorry for the trouble. @hachther's workaround should help temporarily.

I will look to get a fixed version published as soon as possible and will update this issue when I have done so. I will also look into why our automated tests didn't catch this issue!

[tomduncalf]

Based on my testing, a clean install of realm should pull in the right version of @realm.io/common (0.1.2), as it is published on npm and our package.json specifies ^0.1.1... but it seems that if you already have common 0.1.1 installed, npm won't upgrade it, so if you are upgrading Realm you can hit this.

Therefore @s1tony a workaround for now should be just to delete your node_modules and re-install, which should pull in @realm.io/common@0.1.2 – no need to manually install it.

Regardless we should fix this in our package.json, which I'm doing now.

[tomduncalf]

@s1tony @hachther I just released realm@10.19.2 which should fix this issue, apologies for the inconvenience.

Because it relates to the published version of the package (which is not published at the time of running tests) and only occurs on upgrades, this is actually quite tricky to catch in an automated test, but we are going to look to add an automated check to make sure that our packages reference the latest versions of each other which should prevent this happening in future. For now, I've added an item to our PR merge checklist to verify that we have updated the package version when necessary.

[s1tony]

Thank you so much.

…

On Mon, Jun 20, 2022 at 10:26 AM Tom Duncalf ***@***.***> wrote: @s1tony <https://github.com/s1tony> @hachther <https://github.com/hachther> I just released ***@***.*** which should fix this issue, apologies for the inconvenience. Because it relates to the published version of the package (which is not published at the time of running tests) and only occurs on upgrades, this is actually quite tricky to catch in an automated test, but we are going to look to add an automated check to make sure that our packages reference the latest versions of each other which should prevent this happening in future. — Reply to this email directly, view it on GitHub <#4657 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AP57MNK3BECCUC2OSEPN3B3VQCERRANCNFSM5ZDDNC3A> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[s1tony]

Before your post, I had actually worked around this issue by editing mutable-subscription-set.js:

const instanceMethods = {
add(query, options) {
return this._add(query, options);
},

remove(query) {
return this._remove(query);
},
};

This alleviating the issue ;)

Thanks again.