`onOpen` doesn't trigger when the user tap on the text - but does when tapping on icon (android)
See original GitHub issueDescribe the bug
onOpen
doesn’t trigger when the user tap on the text.
Expected behavior
onOpen
should trigger when you tap anywhere inside the select area.
Screenshots
“n/a”
Additional details
- Device: Mororola One Zoom
- OS: Android 9 - July 1, 2020
- react-native-picker-select version: 7.0.0
- react-native version: 0.62.1
- expo sdk version: n/a
Reproduction and/or code sample
https://snack.expo.io/@marioteik/brave-cashew
If you click in the arrow you can see that the log works (android emulator). The same thing doesn’t happen when you click the text.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:15
- Comments:8
Top Results From Across the Web
The activity lifecycle | Android Developers
This is where the lifecycle components can stop any functionality that does not need to run while the component is not visible on...
Read more >how to open particular screen on clicking on push notification ...
First, add "click_action": "FLUTTER_NOTIFICATION_CLICK", in data block in push notification payload. Second, define below callbacks in ...
Read more >Interaction | Notifee
This opens in a new window. Quick Action buttons allow users to perform tasks quickly, and can either trigger your application to open...
Read more >audible app not working android
Tap "Help & Support". Restart Audible App and Device Solution 3. Windows 98 users (or later) can drag and drop this Icon into...
Read more >Use real-time text (RTT) with calls - Android Accessibility Help
Real-time text (RTT) lets you use text to communicate during a phone call. RTT works with TTY and doesn't require any additional accessories....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Is there any solution? I am facing the same issue
Just wanted to drop that this is caused by the position:‘absolute’ attribute under the headlessAndroidPicker class (I’m not sure if this affect IOS). Im still trying to find a way to fix this without messing the component style.