`trigger="visible"` behaviour is different on iOS than on Android when navigating screens using react-navigation about hyperview HOT 3 OPEN

I ended up not using the navigation focus event listener because it actually caused the hyperview screen to go blank if you navigate to a hyperview screen and immediately scroll down. I instead explicitly triggered events to update elements with trigger="on-event" and, in my fork, prevented the visibility action from being triggered when navigating screen on Android so that it is consistent with iOS

from hyperview.

@flochtililoch , any insights on desired behavior here or other approaches with the new navigation system (focus/blur events)?

from hyperview.

I would think the visible trigger should only trigger when the element is actually visible on screen. If an event causes an unfocused screen to reload, the elements that are in the unfocused view-pane should not trigger the visible behavior until their screen is focused again.
We can rely on the focus/blur event on the new navigation system, but we could probably amend the visible handler to behave correctly for unfocused screens.

from hyperview.