Peace
Peace
That is surprising. `onChange` should be called every time a `TouchableOpacity` is pressed. In the case that it doesn't call `onChange`, are you selecting an item or pressing "cancel"? Please...
Is it closing after you select an option, or immediately after the modal opens? If you don't want the modal to close upon a selection, use the prop `closeOnChange={false}`. Your...
@dx-pranta-bot This modal is designed to close when an option is selected. Since `closeOnChange={false}` doesn't do what you need it to, what different behavior would you like?
@justincrow I re-read your notes and think I understand what I missed earlier. It sounds like you use `` to open another dialog (e.g. Document picker) and want that second...
Thanks for the updated notes. Does your Document picker live inside or outside of the modal? It's surprising that the modal state change would cause the picker to close. Perhaps...
@justincrow A race condition could be contributing to your corner case. As the modal is closing, it calls `onChange` (or `onModalClose`). However if the modal hasn't fully completed closing, and...
Some historical context related to this issue: #114
Thanks @AlexeyKhmelev for reporting this. Would you mind opening a new issue? It helps with tracking bug fixes.
Apologies for the late response. Android and iOS native modals behave differently, and changing it for iOS could break Android. However it looks like @AlexeyKhmelev 's check for the empty...
Fix has been published in 2.0.5. Please test this on both iOS and Android.