"Error: Requiring module "BatchedBridge" which threw an exception" after upgrade to 0.14.1

[javamonn]

Hi all,

Hitting some errors after upgrading from 0.13.0 to 014.1. I followed the upgrade instructions in the docs. This trace is while running in iOS simulator.

[castlesix]

Android is also the same. :(

[kusamakura]

I get exactly this when I try to use react-relay via the Shopify fork. (Also using npm install inside node_modules/react-relay, and deleting node_modules/react-relay/react-native)

[skv-headless]

same for me:(

[sooth-sayer]

+1

[javamonn]

@kusamakura We're using nuclear-js, this stack trace linked to from this issue appears related: #1437.

[TylerK]

Not using nuclear-js on a local project and am running into the following errors as well:

[ide]

Try blowing away your node_modules maybe? Wondering if the issue could be related to dupe copies of React Native somehow.

[TylerK]

Hey @ide! Sadly, I have nuked my node_modules folder a few times, with no success. If it helps, here are my dependencies for this project: https://gist.github.com/TylerK/650eec685ee9a8d6581c

Currently running Node 5.0.0 and NPM 3.3.9

[TylerK]

To add: I've attempted this with react-native 0.14.0, 0.14.1, and the 0.15.0-rc as above. All throw the same error.

[adrianrego]

Same here. Upgraded from 0.13 to 0.14.2. Blew out node_modules and updated assets to get the iOS project to build.

[gudmundurmar]

+1

[wanwanxie]

same issue

[adrianrego]

Trying to narrow down the problem on my setup. Starting with a new project, I imported my dependencies one by one in index.ios.js and reloaded the app each time.

I hit this exact error once I imported the following dependencies:

• redux-persist import { persistStore } from 'redux-persist';
• react-redux import { connect } from 'react-redux';

redux: 3.0.4
react-redux: 3.1.0
redux-persist: 1.0.0

[idibidiart]

is anyone able to run 0.14.2 without errors?

UPDATE:

I managed to get a brand new project working fine in 0.14.2 using the standard process:

react-native init MyProject
react-native start

That works fine. It's when we update a 0.13.x project to 0.14.x (including 0.14..2) that we run into issues. I'll investigate the diff between the settings and all that and circle back here if I manage to arrive at the reason.