You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for your work with this library, very excited to put it in production.
While testing things out almost everything seemed to work smoothly, with the exception of react navigation bottom-tabs. We noticed this specifically on screens with media playing. We have a state update that fires on navigation blur. The media then adjusts play state when that happens. This works as expected when navigating within the same tab.
However when switching tabs, we ran into some issues. The state does not update on time, causing the media to be frozen in a playing state when navigating to a different tab. The blur event seems to fire appropriately, so my guess is that the previous tab is freezing almost immediately, not allowing side effects.
Currently running the latest version of all react-navigation libraries and RN 0.64.1
Would love any feedback on dealing with this scenario.
Thanks,
Tedi
The text was updated successfully, but these errors were encountered:
Thank you for your work with this library, very excited to put it in production.
While testing things out almost everything seemed to work smoothly, with the exception of react navigation bottom-tabs. We noticed this specifically on screens with media playing. We have a state update that fires on navigation blur. The media then adjusts play state when that happens. This works as expected when navigating within the same tab.
However when switching tabs, we ran into some issues. The state does not update on time, causing the media to be frozen in a playing state when navigating to a different tab. The blur event seems to fire appropriately, so my guess is that the previous tab is freezing almost immediately, not allowing side effects.
Currently running the latest version of all react-navigation libraries and RN 0.64.1
Would love any feedback on dealing with this scenario.
Thanks,
Tedi
The text was updated successfully, but these errors were encountered: