fix(ios): also call bridge.reset() on webViewWebContentProcessDidTerminate #8143
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jcesarmobile
requested review from
markemer,
EiyuuZack,
Chuckytuh,
theproducer,
benmccarty91,
usernuno,
trevor-lambert and
OS-kepatotorica
markemer
approved these changes
Sep 4, 2025
trevor-lambert
approved these changes
Sep 5, 2025
theproducer
approved these changes
Sep 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
webViewWebContentProcessDidTerminate won't be called when the app is in the background but when you put it back in the foreground, so when it reloads the app and the didStartProvisionalNavigation gets called might be too late for some events
closes #8101