Realm got error Read-only file system with android 8.1

[lytrunghieu]

How frequently does the bug occur?

All the time

Description

I created new react native project and install realm. When I call open connection then I got error "Read-only file system", it is working on android version less 8.1.
Note: it still working on android 8.1 if I use default path of realm.

my package.json:

{
  "name": "awesomeproject",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "android": "react-native run-android",
    "ios": "react-native run-ios",
    "start": "react-native start",
    "test": "jest",
    "lint": "eslint ."
  },
  "dependencies": {
    "react": "17.0.2",
    "react-native": "0.67.4",
    "realm": "^10.14.0"
  },
  "devDependencies": {
    "@babel/core": "^7.12.9",
    "@babel/runtime": "^7.12.5",
    "@react-native-community/eslint-config": "^2.0.0",
    "babel-jest": "^26.6.3",
    "eslint": "7.14.0",
    "jest": "^26.6.3",
    "metro-react-native-babel-preset": "^0.66.2",
    "react-test-renderer": "17.0.2"
  },
  "jest": {
    "preset": "react-native"
  }
}

Code for open connection realm:

const AppInfoSchema = {
  name: 'AppInfoRealmSave',
  properties: {
    packageName: 'string',
    isPostponeLater: 'bool',
    isUpdateUsingLauncher: 'bool',
  },
  primaryKey:'packageName'
};

 Realm.open({
      path: "/storage/emulated/0/AppUpdate/app_update.realm",
      schema: [AppInfoSchema],
      schemaVersion:42
})

I appreciate any help.

Stacktrace & log output

No response

Can you reproduce the bug?

Yes, always

Reproduction Steps

No response

Version

10.14.0

What SDK flavour are you using?

Local Database only

Are you using encryption?

No, not using encryption

Platform OS and version(s)

Android

Build environment

Which debugger for React Native: ..

Cocoapods version

No response

[kraenhansen]

Would it be a possible solution to copy the realm to the App specific storage? You might be able to use something like https://www.npmjs.com/package/react-native-fs#API to get the path of that directory.

[lytrunghieu]

Hi @kraenhansen

I need to share realm file with other app. If I save file realm for only specific app then other app can not access realm file. It is weird, because this bug is only exist on android version larger than 8.0.

[kraenhansen]

@lytrunghieu I imagine your app has to ask the OS for permission to write to this directory. Are you using any of the Android APIs to request access to the shared storage?

[lytrunghieu]

@kraenhansen

Yes, I have added permission in AndroidManifest.xml

 <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
    <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>

And in app I requested permission as well

   const grantedWrite = await PermissionsAndroid.requestMultiple([
            PermissionsAndroid.PERMISSIONS.READ_EXTERNAL_STORAGE,
          PermissionsAndroid.PERMISSIONS.WRITE_EXTERNAL_STORAGE]);

[kraenhansen]

@lytrunghieu to be honest, I'm clueless on what might be happening here then.

It will require further investigations.
Getting a minimal reproduction (a simple GitHub repository showing this error) would be a great help!

[lytrunghieu]

@kraenhansen Have you try reproduce on android 8.1 ?

[kraenhansen]

Nope. I havn't reproduced this yet. My expectation is that the security model was change / tightened with Android 8.1 which is why Realm core can't open the Realm in write-mode.

[tomduncalf]

Hi @lytrunghieu, were you able to create a minimal repro of this issue?

[kneth]

I am closing the issue due to no reply back. Please comment and reopen the issue if needed.

[thucnguyenpfs]

Hello, I have the same problem but on aws nodejs. There was an error in the log.

    "errorType": "RealmError",
    "errorMessage": "Failed to create directory at '/var/task/mongodb-realm/': Read-only file system",
    "code": "PermissionDenied",
    "name": "RealmError",
    "stack": [
        "RealmError: Failed to create directory at '/var/task/mongodb-realm/': Read-only file system",
        "    at /var/task/src/handler.js:1:1555",
        "    at Generator.next (<anonymous>)",
        "    at /var/task/src/handler.js:1:1234",
        "    at new Promise (<anonymous>)",
        "    at o (/var/task/src/handler.js:1:979)",
        "    at Runtime.t.creditLoyalty [as handler] (/var/task/src/handler.js:1:1464)",
        "    at Runtime.handleOnceNonStreaming (/var/runtime/Runtime.js:74:25)"
    ]

My code

  let creditAvailables, cogintoToken;
  try {
    const appLogged = await app.logIn(
      Realm.Credentials.apiKey(process.env.REALM_API_KEY)
    );

    const creditAvailablePromise = await appLogged.functions.getCreditAvailableByBrand({
        brandShopCode: partnerCode,
      });
   } catch (err) {
    console.error('Failed to log in', err);
  }

Do you have any idea?

[kneth]

@thucnguyenpfs It is unrelated to the original issue, and creating a new issue is the best approach.

Said that, /var/task/ is probably read-only on your server, and you should either make the directory writable or use a directory with fewer restrictions.

[sinhgithub]

why this issue is closed :(

[nirinchev]

Because the author didn't reply with repro case. If you're experiencing a similar problem, file a new issue and fill in the template.