Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when start without debug #12477

Closed
IgorZh opened this issue Feb 20, 2017 · 9 comments
Closed

Error when start without debug #12477

IgorZh opened this issue Feb 20, 2017 · 9 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@IgorZh
Copy link

IgorZh commented Feb 20, 2017

Hello, I have a bug just after application started by command react-native run-android. Error appears when I switch off remote debug. With debugger all works correct.

Description

Objects are not valid as a React child (found: object with keys {$$typeof, type, key, ref, props, _owner, _store}). If you meant to render a collection of children, use an array instead or wrap the object using createFragment(object) from the React add-ons. Check the render method of `View`.
traverseAllChildrenImpl
    traverseAllChildren.js:183
traverseAllChildrenImpl
    traverseAllChildren.js:102
traverseAllChildren
    traverseAllChildren.js:218
instantiateChildren
    ReactChildReconciler.js:86
_reconcilerInstantiateChildren
    ReactMultiChild.js:179
mountChildren
    ReactMultiChild.js:249
initializeChildren
    ReactNativeBaseComponent.js:74
mountComponent
    ReactNativeBaseComponent.js:211
mountComponent
    ReactReconciler.js:61
performInitialMount
    ReactCompositeComponent.js:495
mountComponent
    ReactCompositeComponent.js:346
mountComponent
    ReactReconciler.js:61
performInitialMount
    ReactCompositeComponent.js:495
mountComponent
    ReactCompositeComponent.js:346
mountComponent
    ReactReconciler.js:61
performInitialMount
    ReactCompositeComponent.js:495
mountComponent
    ReactCompositeComponent.js:346
mountComponent
    ReactReconciler.js:61
mountComponentIntoNode
    ReactNativeMount.js:54
perform
    Transaction.js:149
batchedMountComponentIntoNode
    ReactNativeMount.js:77
perform
    Transaction.js:149
batchedUpdates
    ReactDefaultBatchingStrategy.js:65
batchedUpdates
    ReactUpdates.js:111
renderComponent
    ReactNativeMount.js:141
render
    ReactNative.js:31
renderApplication
    renderApplication.js:33
run
    AppRegistry.js:76
runApplication
    AppRegistry.js:105
__callFunction
    MessageQueue.js:236
<unknown>
    MessageQueue.js:108
guard
    MessageQueue.js:46
callFunctionReturnFlushedQueue
    MessageQueue.js:107

versions of libs

    "react-dom": "~15.3.2",
    "react-native": "^0.39.2",
@hramos
Copy link
Contributor

hramos commented Feb 21, 2017

Did you address this warning?:

Objects are not valid as a React child (found: object with keys {$$typeof, type, key, ref, props, _owner, _store}). If you meant to render a collection of children, use an array instead or wrap the object using createFragment(object) from the React add-ons. Check the render method of View.

Also, see if this still happens on the most recent version.

@IgorZh
Copy link
Author

IgorZh commented Feb 22, 2017

I think that error happend somewhere in library redux-store, because if I replace my root component in index.android.js by simple View, error still happend. By when I commet using of redux-loop, error disappears.

@hramos
Copy link
Contributor

hramos commented Feb 22, 2017

Can you go back and make sure all the fields in the template are filled out? Right now, there is not sufficient information here for someone to reproduce what you're encountering, which greatly reduces the chances you will be able to get some help here.

Ideally, a GitHub issue would clearly outline a problem in React Native. Are you certain this is something that needs to be addressed in RN as opposed to another library you may be using in your project?

@brentvatne
Copy link
Collaborator

As per @hramos' comment I think this is a problem with one of those libraries. If you can share the code it would be possible to verify that.

@hramos
Copy link
Contributor

hramos commented Feb 22, 2017

I am going to close this, but feel free to open a new issue with the additional information provided. Thanks!

@hramos hramos closed this as completed Feb 22, 2017
@hugomosh
Copy link

@IgorZh did you manage to solve it?
I have the same error and just identify that it is indeed in the store or in the reducers.

@IgorZh
Copy link
Author

IgorZh commented Aug 22, 2017

@hugomosh. Sorry, I can't help you. As I remember I found out that the error depends on some third-party lib, but I didn't solve it.

@hugomosh
Copy link

hugomosh commented Aug 27, 2017 via email

@hugows
Copy link

hugows commented Apr 26, 2018

In my case turns out it was this import in my reducers file:

import { Promise } from 'core-js';

App only ran on debugging mode.

@facebook facebook locked as resolved and limited conversation to collaborators May 24, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

6 participants