2017-06-27 16:25:07 +00:00
<!--
PLEASE DON'T DELETE THIS TEMPLATE UNTIL YOU HAVE READ THE FIRST SECTION.
-->
2016-02-18 18:53:41 +00:00
2017-06-27 16:25:07 +00:00
### Is this a bug report?
2016-02-17 23:57:27 +00:00
2017-06-27 16:25:07 +00:00
(write your answer here)
2017-03-09 00:08:32 +00:00
2017-06-27 16:25:07 +00:00
<!--
If you answered "Yes":
2017-06-01 22:01:00 +00:00
2017-06-27 16:25:07 +00:00
We expect that it will take you about 30 minutes to produce a high-quality bug report.
While this may seem like a lot, putting care into issues helps us fix them faster.
For bug reports, it is REQUIRED to fill the rest of this template, or the issue will be closed.
2016-02-18 23:10:14 +00:00
2017-06-27 16:25:07 +00:00
If you answered "No":
2016-02-18 23:10:14 +00:00
2017-06-27 16:25:07 +00:00
We use GitHub Issues exclusively for tracking bugs in React Native. If you're looking for help,
check out the How to Get In Touch section of the following guide:
https://github.com/facebook/react-native/blob/master/CONTRIBUTING.md#how-to-get-in-touch
2016-02-17 23:57:27 +00:00
2017-06-27 16:25:07 +00:00
Now scroll below!
-->
2016-02-17 23:57:27 +00:00
2017-04-07 18:05:28 +00:00
2017-06-27 16:25:07 +00:00
### Have you read the Bugs section of the Contributing to React Native Guide?
2017-04-07 18:05:28 +00:00
2017-06-27 16:25:07 +00:00
(Write your answer here.)
2016-08-29 17:41:59 +00:00
2017-06-27 16:25:07 +00:00
<!--
Please read through the bug reporting guidelines thoroughly:
https://github.com/facebook/react-native/blob/master/CONTRIBUTING.md#bugs
-->
2016-11-11 17:32:35 +00:00
2017-06-27 16:25:07 +00:00
### Environment
2016-11-11 17:32:35 +00:00
2017-06-27 16:25:07 +00:00
<!--
Please fill in all the relevant fields by running these commands in terminal.
-->
2016-08-29 17:41:59 +00:00
2017-06-27 16:25:07 +00:00
1. `react-native -v` :
2. `node -v` :
3. `npm -v` :
4. `yarn --version` (if you use Yarn):
Then, specify:
2017-07-12 23:47:46 +00:00
<!-- (What platform are you building for? Choose any from iOS, Android, AppleTV.) -->
- Target Platform:
2017-06-27 16:25:07 +00:00
2017-07-12 23:47:46 +00:00
<!-- Which operating system are you using? Specify macOS, Windows, or Linux, along with specific release versions -->
- Development Operating System:
<!-- Include any additional relevant information. Are you using Xcode or Android Studio to build native code? Is the issue specific to a particular iOS or Android SDK? -->
- Build tools:
2017-06-27 16:25:07 +00:00
### Steps to Reproduce
<!--
How would you describe your issue to someone who doesn’ t know you or your project?
Try to write a sequence of steps that anybody can repeat to see the issue.
2017-07-12 23:47:46 +00:00
Be specific! If the bug cannot be reproduced, your issue may be closed.
2017-06-27 16:25:07 +00:00
-->
(Write your steps here:)
1.
2.
3.
### Expected Behavior
<!--
How did you expect your project to behave?
It’ s fine if you’ re not sure your understanding is correct.
Just write down what you thought would happen.
-->
(Write what you thought would happen.)
### Actual Behavior
<!--
Did something go wrong?
Is something broken, or not behaving as you expected?
Describe this section in detail, and attach screenshots if possible.
2017-07-12 23:47:46 +00:00
Don't just say "it doesn't work"!
2017-06-27 16:25:07 +00:00
-->
(Write what happened. Add screenshots!)
### Reproducible Demo
<!--
Please share a project that reproduces the issue.
There are two ways to do it:
* Create a new app using https://snack.expo.io/ and try to reproduce the issue in it.
This is useful if you roughly know where the problem is, or can’ t share the real code.
* Or, copy your app and remove things until you’ re left with the minimal reproducible demo.
This is useful for finding the root cause. You may then optionally create a Snack.
This is a good guide to creating bug demos: https://stackoverflow.com/help/mcve
Once you’ re done, copy and paste the link to the Snack or a public GitHub repository below:
-->
(Paste the link to an example project and exact instructions to reproduce the issue.)
<!--
What happens if you skip this step?
Someone will read your bug report, and maybe will be able to help you,
but it’ s unlikely that it will get much attention from the team. Eventually,
the issue will likely get closed in favor of issues that have reproducible demos.
Please remember that:
* Issues without reproducible demos have a very low priority.
* The person fixing the bug would have to do that anyway. Please be respectful of their time.
* You might figure out the issues yourself as you work on extracting it.
Thanks for helping us help you!
-->