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

Red Screen error on new initialized react-native app #25563

Closed
ho-dor opened this issue Jul 10, 2019 · 11 comments
Closed

Red Screen error on new initialized react-native app #25563

ho-dor opened this issue Jul 10, 2019 · 11 comments
Labels
Bug Stale There has been a lack of activity on this issue and it may be closed soon.

Comments

@ho-dor
Copy link

ho-dor commented Jul 10, 2019

I initialized a new app using react-native and without making any changes, I got a red screen error "Properties must be an object"

Screenshot: - https://drive.google.com/file/d/1-erzk1O-mZy6q-EuFBjE3qjhPgqmaMNA/view?usp=sharing

React Native version:

React Native Environment Info:
System:
OS: Windows 10
CPU: (8) x64 Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
Memory: 3.24 GB / 7.85 GB
Binaries:
Yarn: 1.16.0 - C:\Users\hp\AppData\Roaming\npm\yarn.CMD
npm: 6.4.1 - C:\Program Files\nodejs\npm.CMD
IDEs:
Android Studio: Version 3.4.0.0 AI-183.6156.11.34.5522156

Java version - 8
node - 10.15.3
react-native - 0.57.3

Steps To Reproduce

1.Create a new app with react-native 0.57.3
2. react-native run-android

Describe what you expected to happen:

App to run successfully

Snack, code example, or link to a repository:

https://stackoverflow.com/questions/56958587/property-description-must-be-an-object-red-screen-error-on-new-react-native-app

@ho-dor ho-dor added the Bug label Jul 10, 2019
@sabarinathen
Copy link

sabarinathen commented Jul 10, 2019

I am also having the same issue faced even creating a sample project error shown as property description must be an object on red screen error.

@develgooapps
Copy link

I am also having the same problem, the weirdest thing is that if i turn on debug mode it works fine.

@the-habu
Copy link

I am getting the same error on an already established project, just by running yarn install, having a few minor dependency upgrades. Not sure which one causes the issue yet...

@fdwcomune
Copy link

fdwcomune commented Jul 10, 2019

I'm getting the same issue, only on android and only while the debugger is not open. Seems to be happening in redux.js line 569 for me:

Object.defineProperty(target, key, Object.getOwnPropertyDescriptor(arguments[i], key));

I assume it's something to do with the JS environment on Android. I don't think its specifically a Redux issue.

@develgooapps
Copy link

I'm getting the same issue, only on android and only while the debugger is not open. Seems to be happening in redux.js line 569 for me:

Object.defineProperty(target, key, Object.getOwnPropertyDescriptor(arguments[i], key));

I assume it's something to do with the JS environment on Android. I don't think its specifically a Redux issue.

I tried fixing the redux version to "redux": "4.0.1", and in my project now works fine! Hope your one does too, thank you for everything.

@fdwcomune
Copy link

I tried fixing the redux version to "redux": "4.0.1", and in my project now works fine! Hope your one does too, thank you for everything.

Yes, reverting to v4.0.1 of Redux resolved it for me as well, seems to be some issue with v4.0.2 and/or v4.0.3.

@evandrogrm
Copy link

I think it because Android Q version, i will try Android Pie version to make sure

@fdwcomune
Copy link

fdwcomune commented Jul 11, 2019

Seems like there was an issue with Babel when v4.0.2 and v4.0.3 of Redux was built, causing the issue. A new version of Redux is out (v4.0.4) which should fix this, haven't tested it myself yet.

See Redux issue 3468

@evandrogrm
Copy link

I solved it deleting node_modules and installing it again with npm instead of yarn because my docker project use npm on the executables.
Don't make sense, should do the same, but yeah :)

@stale
Copy link

stale bot commented Oct 10, 2019

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.

@stale stale bot added the Stale There has been a lack of activity on this issue and it may be closed soon. label Oct 10, 2019
@stale
Copy link

stale bot commented Oct 17, 2019

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.

@stale stale bot closed this as completed Oct 17, 2019
@facebook facebook locked as resolved and limited conversation to collaborators Oct 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug Stale There has been a lack of activity on this issue and it may be closed soon.
Projects
None yet
Development

No branches or pull requests

6 participants