Ignite: Could not get BatchedBridge, make sure your bundle is packaged correctly

Created on 21 Apr 2017  路  4Comments  路  Source: infinitered/ignite

I ran through the Getting Started instructions, and then after I ran react-native run-android I'm getting an error.


What's going on?
Getting error, can't see the app.
screen shot 2017-04-20 at 3 39 30 pm


Steps to reproduce
Run through "Getting Started" instructions.


ignite doctor results:
chaps 馃懟 TestApp $ ignite doctor
System
platform darwin
arch x64
cpu 8 cores Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz
directory /Users/chapel/Documents/repos/TestApp

JavaScript
node 7.9.0 /usr/local/bin/node
npm 4.2.0 /usr/local/bin/npm
yarn 0.23.2 /usr/local/bin/yarn

React Native
react-native-cli 2.0.1
app rn version 0.42.0

Ignite
ignite 2.0.0-beta.8 /usr/local/bin/ignite

Android
java 1.8.0_121 /usr/bin/java
android home - /Users/chapel/Library/Android/sdk

iOS
xcode 8.3

Most helpful comment

Do you get the same issue if you run ignite new MyDifferentApp -b ir-next ?

All 4 comments

Do you get the same issue if you run ignite new MyDifferentApp -b ir-next ?

That totally worked ... why? Thanks!

Because the default boilerplate for ignite ignite-ir-boilerplate-2016 uses react-native-router-flux. And yesterday RNRF cut a build that blows things up. We rolled back the version, so if you ran your old command again, it might work (hopefully it does!!!).

The ir-next boilerplate uses react-navigation, which is why that works. And where we're heading.

Sorry for the hiccups!

No worries, thanks for the help and the explanation! 馃槂

Was this page helpful?
0 / 5 - 0 ratings

Related issues

tayfunyasar picture tayfunyasar  路  3Comments

TitanKing picture TitanKing  路  3Comments

GantMan picture GantMan  路  3Comments

lichao0817 picture lichao0817  路  3Comments

ta-ssi-lo picture ta-ssi-lo  路  3Comments