Support React Native 0.59 #2282

cmelchior · 2019-03-13T09:48:41Z

React Native 0.59 is released: https://facebook.github.io/react-native/blog/2019/03/12/releasing-react-native-059

It, among other things, enables us to support 64 bit binaries on React Native Android, but it also seems there are more internal changes we need to handle.

Some headers appear to be gone or have changed: https://github.com/realm/realm-js/blob/master/react-native/ios/RealmReact/RealmReact.mm#L27. It is unclear exactly what is required to fix this.

64 bit support seems to require changes to https://github.com/realm/realm-js/blob/master/react-native/android/src/main/jni/Application.mk#L3 and https://github.com/realm/realm-js/blob/master/react-native/android/build.gradle#L230, but this does not need to be part of the same PR as 0.59 support

See also: #2281 (comment)

tgoyne · 2019-03-13T21:55:45Z

Arm64 support will require writing a new version of the hook function since that's inherently platform-specific.

tgoyne · 2019-03-13T22:10:04Z

On iOS we seem to build fine with 0.59 with no changes but it crashes on startup.

lodev09 · 2019-03-14T04:20:48Z

Is there a timeline on this? trying to upgrade our app to RN 0.59.
Thanks!

ferrannp · 2019-03-14T12:33:14Z

The issues is with Android 64 bits. If you try to install the 64 bits in your phone the app will crash with:

java.lang.UnsatisfiedLinkError: couldn't find DSO to load: librealmreact.so

Do you have updates on how hard would that be @kneth? I assume people are excited to finally have 64 bits on Android and Google will enforce this soon on the Play Store.

cmelchior · 2019-03-14T12:51:06Z

Realm doesn't support 64 binaries on React Native just yet. This is being tracked separately here #2221 but we plan to address this as soon as possible but I don't have an exact timeframe just yet.

lodev09 · 2019-03-14T12:53:15Z

@cmelchior I see, can you recommend a stable/latest RN version that realm fully supports? I see other issues related to compatibility as well e.g. RN 0.58

ferrannp · 2019-03-14T13:18:02Z

@cmelchior thanks! We should probably unified it in one issue.

@lodev09 the latest react-native 0.59.x works with the latest realm. The only thing is that you should build only 32 bits variants for Android as 64 bits one will crash.

lodev09 · 2019-03-14T13:22:29Z

@ferrannp I'm getting dependency issue during fresh install though e.g. https-proxy-agent. Do you recommend a workaround of adding those in my package.json instead?

They are filed in #2259 and #2281

dkpalmer · 2019-05-24T18:40:33Z

I just tried updating to 0.59.8. Overall things seem OK with Realm on iOS. The only issue I've noticed is Object.assign({}, obj) on a Realm object always returns an empty object. The only way I've been able to create a copy of an object is JSON.parse(JSON.stringify(obj)).

brianinator · 2019-06-03T16:27:35Z

I am still seeing App launch crash with SoLoader load error:

java.lang.UnsatisfiedLinkError: couldn't find DSO to load: librealmreact.so caused by: dlopen failed: "/data/data/.../lib-main/librealmreact.so" is 32-bit instead of 64-bit

react-native: 0.59.8
realm: 2.28.1
device: Samsung Galaxy S8
Android: 8.0.0

I analyzed the apk and see the librealmreact.so in 64 bit and 32 bit folders.

kneth · 2019-06-04T08:07:22Z

@testshallpasswork

I am not able to reproduce it using a simple app using Realm JS v2.28.1 and RN v0.59.8.

Are you upgrading an existing app? Not sure how that should cause the issue, just wondering :-)

brianinator · 2019-06-04T14:22:08Z

@kneth It is existing app. I went from realm v2.0.12 to v2.28.1. It builds and runs on Android emulator fine. Also to note, I went from react-native 0.55.4 to 0.59.8. I was thinking on trying to isolate it by building only for 64-bit and seeing if reproduced it.

brianinator · 2019-06-04T18:53:54Z

@kneth I was able to workaround it. I added to default config:

defaultConfig {
// ....
        packagingOptions {
            pickFirst 'lib/x86_64/librealmreact.so'
            pickFirst 'lib/arm64-v8a/librealmreact.so'
        }
// ...
}

and to proguard-rules.pro

-keep class io.realm.react.**

Now, I get a missing "index.android.bundle" issue and it crashes as a result.

See: * #8366 * realm/realm-js#2282 * facebook/react-native#25060 Signed-off-by: Jakub Sokołowski <jakub@status.im>

tomsjansons · 2019-06-08T19:57:47Z

I just tried updating to 0.59.8. Overall things seem OK with Realm on iOS. The only issue I've noticed is Object.assign({}, obj) on a Realm object always returns an empty object. The only way I've been able to create a copy of an object is JSON.parse(JSON.stringify(obj)).

I came across this specific issue, but for me doing let obj = { ...realmObj } works for some reason. This does not make sense to me as I was under the impression the spread syntax does Object.assign anyways... but somehow works for me...

sreeragk1 · 2019-06-12T10:56:23Z

Hi,

Please reply for the following :

Just wanted to clarify whether realm@2.27.0 supports react-native 0.59 version ?

If not, Any expected date for the release of supported realm version?

Is following error is due to realm version compatibility?
Error during npm install realm@2.27.0

node-pre-gyp ERR! stack Error: Failed to execute 'C:\Program Files\node-v9.11.2-win-x64\node.exe C:\Program Files\node-v9.11.2-win-x64\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js configure --fallback-to-build --module=C:\Program Files\node-v9.11.2-win-x64\node_modules\realm\compiled\node-v59_win32_x64\realm.node --module_name=realm --module_path=C:\Program Files\node-v9.11.2-win-x64\node_modules\realm\compiled\node-v59_win32_x64 --napi_version=3 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v59' (1)
node-pre-gyp ERR! stack at ChildProcess. (C:\Program Files\node-v9.11.2-win-x64\node_modules\realm\node_modules\node-pre-gyp\lib\util\compile.js:83:29)
node-pre-gyp ERR! stack at ChildProcess.emit (events.js:180:13)
node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:936:16)
node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:220:5)
node-pre-gyp ERR! System Windows_NT 10.0.17134
node-pre-gyp ERR! command "C:\Program Files\node-v9.11.2-win-x64\node.exe" "C:\Program Files\node-v9.11.2-win-x64\node_modules\realm\node_modules\node-pre-gyp\bin\node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd C:\Program Files\node-v9.11.2-win-x64\node_modules\realm

ferrannp · 2019-06-13T18:34:52Z

@cmelchior I think this issue can be closed.

kneth · 2019-06-25T12:31:59Z

@sreeragk1 You are using node 9 which is the root of your problems. Please use either 8 or 10.

sinhpn92 · 2019-07-02T07:30:46Z

I just tried updating to 0.59.8. Overall things seem OK with Realm on iOS. The only issue I've noticed is Object.assign({}, obj) on a Realm object always returns an empty object. The only way I've been able to create a copy of an object is JSON.parse(JSON.stringify(obj)).

🤣 Lol. It's really fun. We need two process to copy 1 object :( Have any solution to do it?

tomsjansons · 2019-07-02T08:13:32Z

@sinhpn92 I ended up using

let obj = { ...realmObj }

on my ReactNative project that works for some mysterious reason and writing a shallow copy for my Node project where Babel transpiled the spread operator to Object.assign

function CopyObjShallow(copyFromArray) {
    const objTo = {}
    for (const arrayIndex in copyFromArray) {
        for (const objKey in copyFromArray[arrayIndex]) {
            objTo[objKey] = copyFromArray[arrayIndex][objKey]
        }
    }
    return objTo
}

newObj = CopyObjShallow([realmObj, { key: 123, FieldOne:"value one" }])

cyphire · 2019-07-09T20:03:46Z

Just saw this as all of a sudden my code of

// tmpInfo is a single realm object
tmpBins.push({...tmpInfo})

No longer works.

I had to use:

tmpBins.push({id: tmpInfo.id, key: tmpKey.key})

Does anyone know if it is an issue with Babble or is it a change in realm behavior? I thought that by using the spread operator it would make this an array of anonomous objects, not realm objects but I guess i do need to use a shallow copy or stringify/parse.?

MrScorp · 2019-07-12T13:59:20Z

RN 0.59.9, Node 10.16.0, realm 2.28.1


// myObj is an object retrieved from realm, something like {a:"aa", b:"bb"}

const tmp = {...myObj}; //returns {}

const d2 = {e: "EE", f:"FF"};
const tmp2 = {...myObj, ...d2}; //returns {e: "EE", f:"FF"}, so RN object spread still works

sumyfly · 2019-07-29T08:27:32Z

I use react-native 0.59.10, and when I call Object.values(RealmResults), it returns an empty array. But it works previously with 0.57.5. Does anyone have an idea?

cyphire · 2019-07-29T12:44:55Z

Yes. You can't do that anymore. I just JSON.stringify(JSON.parse(realm array)) to get my array out of realm.

…

On Mon, Jul 29, 2019, 4:27 AM Edward Qian ***@***.***> wrote: I use react-native 0.59.10, and when I call Object.values(RealmResults), it returns an empty array. But it works previously with 0.57.5. Does anyone have an idea? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#2282?email_source=notifications&email_token=AACSPBWGY7PLH6RZ5MFCO6DQB2SXTA5CNFSM4G5TGML2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD277L3Q#issuecomment-515896814>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AACSPBTBPHMAOQKO5JGOB6TQB2SXTANCNFSM4G5TGMLQ> .

cyphire · 2019-07-29T12:45:30Z

Sorry that's backwards

…

On Mon, Jul 29, 2019, 8:44 AM Brian Canin ***@***.***> wrote: Yes. You can't do that anymore. I just JSON.stringify(JSON.parse(realm array)) to get my array out of realm. On Mon, Jul 29, 2019, 4:27 AM Edward Qian ***@***.***> wrote: > I use react-native 0.59.10, and when I call Object.values(RealmResults), > it returns an empty array. But it works previously with 0.57.5. Does anyone > have an idea? > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <#2282?email_source=notifications&email_token=AACSPBWGY7PLH6RZ5MFCO6DQB2SXTA5CNFSM4G5TGML2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD277L3Q#issuecomment-515896814>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AACSPBTBPHMAOQKO5JGOB6TQB2SXTANCNFSM4G5TGMLQ> > . >

sumyfly · 2019-07-30T10:33:27Z

Thanks, but I used Realm Relationships, it will take a long time to parse it to a string. I downgraded the RN to the old version for now, hope there's a better solution.

YaoHuiJi · 2019-08-30T10:25:12Z

I just tried updating to 0.59.8. Overall things seem OK with Realm on iOS. The only issue I've noticed is Object.assign({}, obj) on a Realm object always returns an empty object. The only way I've been able to create a copy of an object is JSON.parse(JSON.stringify(obj)).

🤣💔😢😭It is much more weird in my project(2500)，when react native "Debug JS Remotely" is turned on , Object.assign will copy data from realm object as expect, but if you turn debugger off, Object.assign will copy nothing, return an empty object {}. Is it probably about javascript runtime？

bachphuc · 2020-03-20T06:56:23Z

I'm facing with this issue. Any progress?
I updated current my app to react-native version 0.61 and now it's not working because this issue 🤣💔🤣💔. I'm thinking about other solution like using alternative local database library. Downgrade react-native version is not solution, react-native has a lot of changes and we have to go ahead.

bmunkholm · 2020-03-20T09:43:32Z

@bachphuc and all: We don't really pay attention to closed issues. So please create a new issue with a repro case. Thanks!

cmelchior added the T-Enhancement label Mar 13, 2019

realm-ci added the Thinking Robot label Mar 13, 2019

realm-probot bot removed the Thinking Robot label Mar 13, 2019

cmelchior added this to the 2019-w12 milestone Mar 19, 2019

SounD120 mentioned this issue Mar 27, 2019

Unable to debug a React Native app that uses RealmJS microsoft/vscode-react-native#955

Closed

sercand mentioned this issue Mar 30, 2019

Compile-time Error: control may reach end of non-void function with Xcode 10.2 #2305

Closed

geragray modified the milestones: 2019-w12, 2019-w14 Apr 1, 2019

FunkyLambda mentioned this issue Apr 2, 2019

[React Native] Add 64 bit support for Android #2221

Closed

reime005 mentioned this issue May 7, 2019

Add arm64-v8a build support [WIP] #2364

Closed

brianinator mentioned this issue Jun 3, 2019

/lib/arm64/librealmreact.so Crashes on app launch #2391

Closed

yenda mentioned this issue Jun 5, 2019

Can't launch mobile app after realm upgrade: Unfortunately, Status has stopped (Android 6.0.1, Galaxy S6 and S7) status-im/status-mobile#8366

Closed

jakubgs added a commit to status-im/status-mobile that referenced this issue Jun 5, 2019

temporary for for realm issues

04c0c68

See: * #8366 * realm/realm-js#2282 * facebook/react-native#25060 Signed-off-by: Jakub Sokołowski <jakub@status.im>

jakubgs mentioned this issue Jun 5, 2019

temporary fix for realm issues status-im/status-mobile#8367

Closed

bmunkholm assigned kneth Jun 12, 2019

kneth closed this as completed Jun 25, 2019

YaoHuiJi mentioned this issue Aug 30, 2019

Realm returns blank when not using React Native Debugger #2500

Closed

realm locked as off-topic and limited conversation to collaborators Mar 20, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Support React Native 0.59 #2282

Support React Native 0.59 #2282

cmelchior commented Mar 13, 2019 •

edited

Loading

tgoyne commented Mar 13, 2019

tgoyne commented Mar 13, 2019

lodev09 commented Mar 14, 2019

ferrannp commented Mar 14, 2019 •

edited

Loading

cmelchior commented Mar 14, 2019

lodev09 commented Mar 14, 2019

ferrannp commented Mar 14, 2019

lodev09 commented Mar 14, 2019

dkpalmer commented May 24, 2019 •

edited

Loading

brianinator commented Jun 3, 2019 •

edited

Loading

kneth commented Jun 4, 2019

brianinator commented Jun 4, 2019

brianinator commented Jun 4, 2019

tomsjansons commented Jun 8, 2019

sreeragk1 commented Jun 12, 2019

ferrannp commented Jun 13, 2019

kneth commented Jun 25, 2019

sinhpn92 commented Jul 2, 2019

tomsjansons commented Jul 2, 2019 •

edited

Loading

cyphire commented Jul 9, 2019

MrScorp commented Jul 12, 2019 •

edited

Loading

sumyfly commented Jul 29, 2019

cyphire commented Jul 29, 2019 via email

cyphire commented Jul 29, 2019 via email

sumyfly commented Jul 30, 2019

YaoHuiJi commented Aug 30, 2019 •

edited

Loading

bachphuc commented Mar 20, 2020

bmunkholm commented Mar 20, 2020

Support React Native 0.59 #2282

Support React Native 0.59 #2282

Comments

cmelchior commented Mar 13, 2019 • edited Loading

tgoyne commented Mar 13, 2019

tgoyne commented Mar 13, 2019

lodev09 commented Mar 14, 2019

ferrannp commented Mar 14, 2019 • edited Loading

cmelchior commented Mar 14, 2019

lodev09 commented Mar 14, 2019

ferrannp commented Mar 14, 2019

lodev09 commented Mar 14, 2019

dkpalmer commented May 24, 2019 • edited Loading

brianinator commented Jun 3, 2019 • edited Loading

kneth commented Jun 4, 2019

brianinator commented Jun 4, 2019

brianinator commented Jun 4, 2019

tomsjansons commented Jun 8, 2019

sreeragk1 commented Jun 12, 2019

ferrannp commented Jun 13, 2019

kneth commented Jun 25, 2019

sinhpn92 commented Jul 2, 2019

tomsjansons commented Jul 2, 2019 • edited Loading

cyphire commented Jul 9, 2019

MrScorp commented Jul 12, 2019 • edited Loading

sumyfly commented Jul 29, 2019

cyphire commented Jul 29, 2019 via email

cyphire commented Jul 29, 2019 via email

sumyfly commented Jul 30, 2019

YaoHuiJi commented Aug 30, 2019 • edited Loading

bachphuc commented Mar 20, 2020

bmunkholm commented Mar 20, 2020

cmelchior commented Mar 13, 2019 •

edited

Loading

ferrannp commented Mar 14, 2019 •

edited

Loading

dkpalmer commented May 24, 2019 •

edited

Loading

brianinator commented Jun 3, 2019 •

edited

Loading

tomsjansons commented Jul 2, 2019 •

edited

Loading

MrScorp commented Jul 12, 2019 •

edited

Loading

YaoHuiJi commented Aug 30, 2019 •

edited

Loading