Handling back buton behavior on Android

[jjzazuet]

Handling back buton behavior on Android

[niftylettuce]

Thanks for your feedback. I'm not sure what's going on here - I haven't the time to test and I don't even know if my XCode simulator is still installed. I'll gladly accept a PR and another maintainer here! My time with RN is super limited for the next bit of time 😦

[b8ne]

hey @jjzazuet how did you go with this? I just had a quick look, react native does provide a onBack listener, however it will depend on your implementation. ie. if you have multiple listeners or nested scenes/navigation the experience may vary. It would also need to bind to your containers state, and not this package. Because of this I wouldnt recommend implementing a method specific to this package, but rather to your project.
I found https://github.com/fractaltech/react-native-onback to be pretty simply but powerful.

[jjzazuet]

Hey @b8ne, so what I ended up doing was wrapping Spinner under my app specific component (which is connected to the Redux state), and then just intercepting the Android back event with the BackAndroid api offered by Facebook. So yeah I think it makes sense to close this issue report. Thanks for your help!

[urska19]

Hi.

I know this issue is closed for a while now, but maybe following comment will still help someone. When back button on Android is pressed, Spinner disappears, because of the Modal's prop onRequestClose, which is set to close the Modal. Using onRequestClose={() => {}} instead, will prevent from closing the Modal and Spinner will be visible until the visibility is changed.

Best.