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

Props validation errors when using polyfills #17790

Closed
Hunsu opened this issue Jan 30, 2018 · 2 comments
Closed

Props validation errors when using polyfills #17790

Hunsu opened this issue Jan 30, 2018 · 2 comments
Labels
Ran Commands One of our bots successfully processed a command. Resolution: Locked This issue was locked by the bot.

Comments

@Hunsu
Copy link

Hunsu commented Jan 30, 2018

Is this a bug report?

Yes

Have you read the Contributing Guidelines?

Yes

Environment

Environment:
OS: Linux 4.13
Node: 8.1.4
Yarn: 1.0.1
npm: 4.6.1
Watchman: 4.9.0
Xcode: N/A
Android Studio: Not Found

Packages: (wanted => installed)
react: 16.2.0 => 16.2.0
react-native: https://github.com/expo/react-native/archive/sdk-25.0.0.tar.gz => 0.52.0

Target Platform: Android

Steps to Reproduce

I created a repo https://github.com/Hunsu/react-native-fetch-mock-issue-5 with the issue.

I wanted to use the package react-native-fetch-mock. I ran into an issue about the es6 Symbol. So I added a polyfill (babel-polyfill and replaced later with es6-symbol/). The issue was resolved but now I got errors about invalid props for the components I use. The errors are always about the children props: Failed prop type: invalid prop 'children' of type object supplied to 'some component', expected a single ReactElement.

Expected Behavior

No props validation errors

Actual Behavior

Props errors

screenshot from 2018-01-30 19-48-07

Reproducible Demo

https://github.com/Hunsu/react-native-fetch-mock-issue-5

Just do yarn install and then start the app on expo.

@react-native-bot
Copy link
Collaborator

Thanks for posting this! It looks like you may not be using the latest version of React Native, v0.53.0, released on January 2018. Can you make sure this issue can still be reproduced in the latest version?

I am going to close this, but please feel free to open a new issue if you are able to confirm that this is still a problem in v0.53.0 or newer.

How to ContributeWhat to Expect from Maintainers

@react-native-bot react-native-bot added Ran Commands One of our bots successfully processed a command. Stale There has been a lack of activity on this issue and it may be closed soon. labels Feb 24, 2018
@stale stale bot removed the Stale There has been a lack of activity on this issue and it may be closed soon. label Feb 24, 2018
@salmanwaheed
Copy link

salmanwaheed commented Feb 24, 2018 via email

@facebook facebook locked as resolved and limited conversation to collaborators Feb 24, 2019
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Feb 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Ran Commands One of our bots successfully processed a command. Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

3 participants