Uploaded image for project: 'Realm JavaScript SDK'
  1. Realm JavaScript SDK
  2. RJS-1349

Encrypted Realm throws error in electron

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None

      How frequently does the bug occur?

      All the time

      Description

      I"m using realm sync and I want the database to be encrypted. So, I'm using encryption as mentioned in the docs. I'm getting this error:
      interprocess sharing is currently unsupported.DB has been opened by pid: 10938. Current pid is 10969

      I think as I'm opening realm it in two processes this error occurring. Can you please tell me how can I fix this?

      My config:
      config = {
      schema: [--schema---],
      path: '--path---',
      encryptionKey: new Int8Array(64),
      schemaVersion: 0, //optional
      sync: {
      user: appRealm.currentUser,
      partitionValue: ------,
      // The behavior to use when this is the first time opening a realm.
      newRealmFileBehavior:

      {type: 'downloadBeforeOpen'}

      ,
      // The behavior to use when a realm file already exists locally,
      // i.e. you have previously opened the realm.
      existingRealmFileBehavior:

      {type: 'openImmediately'}

      ,
      error: (error) =>

      { console.error('new realm error: ', error) }

      }
      }

      Stacktrace & log output

      No response

      Can you reproduce the bug?

      Yes, always

      Reproduction Steps

      No response

      Version

      10.4.0

      What SDK flavour are you using?

      MongoDB Realm (i.e. Sync, auth, functions)

      Are you using encryption?

      Yes, using encryption

      Platform OS and version(s)

      Macos big sur Version: 11.5.2

      Build environment

      Which debugger for React Native: ..

            Assignee:
            Unassigned Unassigned
            Reporter:
            unitosyncbot Unito Sync Bot
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: