Closed
Description
Is this a bug report?
Yes
(write your answer here)
Have you read the Bugs section of the Contributing to React Native Guide?
(Write your answer here.)
Environment
react-native -v
: 0.45.1node -v
: 8.1.3npm -v
: 5.0.4yarn --version
(if you use Yarn): 0.27.5
Then, specify:
- Target Platform (e.g. iOS, Android): Android
- Development Operating System (e.g. macOS Sierra, Windows 10): macOS Sierra 10.12.5
- Build tools (Xcode or Android Studio version, iOS or Android SDK version, if relevant): Android SDK 25, Android Build Tools 25.0.2
Steps to Reproduce
(Write your steps here:)
- react-native init AwesomeProject
- react-native run-android
Expected Behavior
Should work as it did with RN v0.44.0 or RN 0.45.0
(Write what you thought would happen.)
Actual Behavior
undefined is not an object (evaluating 'regeneratorRuntime.mark')
<unknown>
loadModuleImplementation
require.js:174:12
guardedLoadModule
require.js:126:36
_require
require.js:110:24
<unknown>
index.js:2
loadModuleImplementation
require.js:174:12
guardedLoadModule
require.js:126:36
_require
require.js:110:24
<unknown>
configureStore.js:19
loadModuleImplementation
require.js:174:12
guardedLoadModule
require.js:126:36
_require
require.js:110:24
<unknown>
index.js:32
loadModuleImplementation
require.js:174:12
guardedLoadModule
require.js:126:36
_require
require.js:110:24
<unknown>
index.android.js:10
loadModuleImplementation
require.js:174:12
guardedLoadModule
require.js:119:45
_require
require.js:110:24
global code
(Write what happened. Add screenshots!)
Reproducible Demo
(Paste the link to an example project and exact instructions to reproduce the issue.)
Metadata
Metadata
Assignees
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
messense commentedon Jul 6, 2017
+1
messense commentedon Jul 6, 2017
I am getting this on 0.46
Amurmurmur commentedon Jul 6, 2017
Alright seems like I've managed to fix this on RN 0.45.1
Just clean everything:
Worked for me, also unlinking and linking might help.
ernoaapa commentedon Jul 6, 2017
Face same problem when creating new project with Ignite.
react-native -V
0.45.1node -v
v7.10.0npm -v
4.2.0yarn --version
0.27.5react-native run-ios
@Amurmurmur suggestion didn't help.
ernoaapa commentedon Jul 6, 2017
Found the problem what I had (with new project generated with Ignite).
The error were pointing in my project to line
import rootSaga from '../Sagas/'
which contain export like this:After changing it to this started to work:
I'm not yet familiar with the ES6 generator functions and
require
support for them, but at least now I can continue. And have to say that the error were pointing to the place where the invalidexport
were. I hope this helps someone.GantMan commentedon Jul 6, 2017
infinitered/ignite#1098 (comment)
grabbou commentedon Jul 6, 2017
Wasn't this fixed here? e7c1cf5
GantMan commentedon Jul 6, 2017
So this won't roll out till 0.47?
grabbou commentedon Jul 6, 2017
Amurmurmur commentedon Jul 6, 2017
Tried to fix with the suggested Saga solution, its surely something to do with saga because when I comment out saga implementation in my configureStore, the error is gone however trying suggested solution doesnt work for me. :/
Amurmurmur commentedon Jul 6, 2017
@grabbou @GantMan @ernoaapa
Alright guys, figured out the problem
downgraded
babel-preset-react-native
form2.1.0
to2.0.0
all works fine on Android/iOSThough once upgraded to 0.46 the error comes back.
As for RN 0.47-rc.0, most packages I have linked, wont work due to some changes to the api of the react-native I guess because they will throw errors such as:
kcalmes commentedon Jul 7, 2017
@Amurmurmur I am still seeing the issue on 0.45.1 even after downgrading babel. I wonder how much node and npm versions might be affecting which fixes work and which ones don't.
node: v8.1.0
npm: 5.1.0
OS: macOS Sierra 10.12.5
Amurmurmur commentedon Jul 7, 2017
@kcalmes Make sure you reset react-native packager after you've downgraded babel with:
100 remaining items