-
Notifications
You must be signed in to change notification settings - Fork 24.3k
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
TouchableOpacity can't call onPress props. #15927
Comments
@facebook-github-bot needs-repro |
Can you reproduce the issue using Snack? This step is necessary for people to be able to see and debug the issue being reported. See "How to Contribute". |
I tumbling a bit around with this as well until I found a solution that might help you. As oppose to the parent component you are not allowed to use
An even cleaner solution
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. If you think this issue should definitely remain open, please let us know why. Thank you for your contributions. |
Is this a bug report?
TouchableOpacity can't call onPress method in iPhone 6sP.
When TouchableOpacity cantains a View ,
The View contains two View(top and bottom)
top can call onPress but bottom can't,in iPhone 6sP
(write your answer here)
Have you read the Contributing Guidelines?
(Write your answer here.)
Environment
react-native -0.48.1
:node -v8.1.4
:npm -5.4.1
:yarn --v0.23.4
:Then, specify:
Steps to Reproduce
(Write your steps here:)
1.A
View
,inside ,top isText
,bottom isView
2.
TouchableOpacity
contains theView
,not definedTouchableOpacity
'sstyle
3.iPhone 6p:touch bottom
View
is normal,but,iPhone 6s P:touch bottom
View
is can't call onPressExpected Behavior
(Write what you thought would happen.)
Actual Behavior
(Write what happened. Add screenshots!)
Reproducible Demo
(Paste the link to an example project and exact instructions to reproduce the issue.)
The text was updated successfully, but these errors were encountered: