The Realm is already in a write transaction

I’m getting an error when writing to a Realm db. I’ve looked at other solutions for this, and the recommended approach to checking if in a write transaction doesn’t seem to be available in Realm JS. Is there some other mechanism to address this? Thanks!

Here’s the offending code:

addAll: Function = (businessesToAdd): ?Array<Business> => {
    let businesses: Array<Business> = [];

    Realm.write(() => {
      businesses = businessesToAdd.map(business => {
        return Realm.create(ClassName, { ...business }, true);
      });
    });

    return businesses;
  };

ExceptionsManager.js:71 Error: The Realm is already in a write transaction
    at sendRequest (http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false&minify=false:130302:7)
    at Object.callMethod (http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false&minify=false:130220:1784)
    at Realm.<anonymous> (http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false&minify=false:130063:771)
    at BusinessDAO.exports.BusinessDAO.addAll (http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false&minify=false:137351:17)
    at _callee$ (http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false&minify=false:137464:23)
    at tryCatch (http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false&minify=false:26695:29)
    at Generator.invoke [as _invoke] (http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false&minify=false:26969:12)
    at Generator.prototype.(anonymous function) [as next] (http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false&minify=false:26728:13)
    at tryCatch (http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false&minify=false:26695:29)
    at invoke (http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false&minify=false:26771:12)

[bhaskarmurthy]

@blagoev As a followup, we do not have any nested .write blocks, and it doesn’t seem like the issue is fixed as per #127 .

Are there any steps we can take to debug into this a bit more?

[kneth]

We have added manual transactions to help in this situation. I hope we can release it this week.