Mike Hardy

Original work for OnRenderProcessGone: - #5820 - #5881 - #9086

It appears from repo search that we create WebViewClients in a handful of places, but the PageWebViewClient is the one that all the pages exposed from desktop extend from https://github.com/ankidroid/Anki-Android/blob/main/AnkiDroid/src/main/java/com/ichi2/anki/pages/PageWebViewClient.kt...

Okay - I prefer that myself, I find the extensions to be a little "aspect-oriented-programming-like" where things slice in sometimes in non-obvious ways from non-location-coherent spots and for me that...

Hmmm > When running my Expo dev build on device How exactly was this build made? Note this interesting case: https://github.com/invertase/react-native-firebase/issues/8049#issuecomment-2409087900

🤔 doesn't this *seem* like it's an Expo error? Like, this should not be happening, and there should be an issue in an Expo issue tracker, and they should fix...

> I used my IP from https://whatismyipaddress.com/ with the port 9099 - just double checking am I right in using this IP? @SKempin That is most likely an "externally visible...

> Failed to connect to /192.168.86.24:9099 That slash looks really suspicious 🤔 If I were troubleshooting this I would: 1- make sure I can actually run a simple local connection...

May have to do with large file sizes, from latest build run (which ended in failure status): > Unhandled exception: > Exception: Committing and publishing failed: remote: warning: See https://gh.io/lfs...

The release script is not idempotent, so now after having failed after pushing some artifacts it appears it will fail every time Releases here are stuck until this is resolved...

Interestingly - usable artifacts still appear to have been published - a test integration of 11.10.0 in react-native-firebase appears to be successful: - Related https://github.com/invertase/react-native-firebase/pull/8410