App crash! when used Realm.copyBundledRealmFiles().

Goals

I have a test.realm file. I want import and open this database file in react-native.

Code Sample

After searching about it.I found Realm.copyBundledRealmFiles() method in realm…

So I did something like this…

• create a fresh new react-native app
• install realm. (with manual linking)
• paste test.realm file into android/app/src/main/assets/test.realm
• App.js code as fellow

import React from 'react';
import { Text } from 'react-native';
import Realm from 'realm';

Realm.copyBundledRealmFiles(); // with out this line every thing work fine also realm working perfectly!

// let realm = new Realm({path: 'test.realm'});
// console.log(realm.objects('Test'));

export default () => <Text children="Hello World"/>

I create new react-native app for testing this Realm.copyBundledRealmFiles() method. Those are all step I did. (not more nor less)

Note : I found out that by using Realm.copyBundledRealmFiles(); Only crash App if there is any realm database file in android/app/src/main/assets/ directory.

So did I something wrong? If so How to import realm file and open in react-native?

Actual Results

Android app automatically exit with message ‘unfortunately stop…’ or something. React-native did not report any error stack track.

Version of Realm and Tooling

• Realm JS SDK Version: 6.15
• Node or React Native: React Native
• Client OS & Version: Only Android

[aliasad106]

@kraenhansen Yes, Here’s my realm file. https://drive.google.com/file/d/1EvHNpMAgl8r0Cr8ZMfI8LBBj4vm2SwtG/view?usp=sharing And I have pre-loaded it with data. The crash doesn’t happen on Android version 10 but it happens with Android version 6.0.1

PS: It happens on opening first, It crashes then second time I open it doesn’t crash, And when I kill the app again and reopen, it crashes again.

[no-response[bot]]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don’t have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.