[Android] Timing of NativeCommands delivery vs. calls of TurboModule methods vs. AppState changes about react-native HOT 2 OPEN

Hi @birdofpreyru, thanks for the issue.

I feel this is a bug/undocumented behavior. My hypothesis is that when you put the app in background, the Component tree is unmounted so the command is not sent, but stored in some kind of queues. As soon as the app comes back to foreground, the component is remounted, the queue flushed and the command executed.

If that the case, it should be easy to create a simple reproducer using this template, where you can add react-native-webview as a dependency. This would help us investigate whether this is the case.
I don't have a clean and quick solution for this problem, it might require us some architectural discussion, but it is definitely something we want to understand and we want to get to the bottom of this!

from react-native.

Sure @cipolleschi , here you are: https://github.com/birdofpreyru/issue-45017

After doing yarn, you probably want to open its android project in Android studio, locate react-native-webview/kotlin+java/com.reactnativecommunity.webview/RNCWebViewManagerImpl.kt, and set a breakpoint at the line number 314 (it reads "stopLoading" -> webView.stopLoading()).

Then run the app from Android studio in debug mode (and with dev server running):

• It opens, loads RN website.
• You hit the home screen button of emulator (or device)
• The app goes into background, an (NOBRIDGE) LOG Entering background! is printed in the dev server console, the breakpoint in native code is not hit.
• Now you press the app icon in emulator to bring it back to the foreground — now the breakpoint for stopLoading() is hit.

from react-native.