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
If you get a loading failure, calling didFailLoadWithError on your delegate, the bridge no longer receives or responds to any JS messages passed, as if the bridge connection is severed. In my case, I reload links into the same web view, so after a single failure, no subsequent loads handle JS messages.
The text was updated successfully, but these errors were encountered:
If you instantiate the bridge and reconnect it to the webview on failure, you can get the bridge working again, but of course that's because I reconnect a new bridge.
In addition, if you declare a delegate after the bridge, the bridge does not work.
I use an "initializeBridge" method on init of the view. I then call that method again on my delegate's "didFailLoadWithError". This is a workaround, but does not seem to be intended functionality.
If you get a loading failure, calling didFailLoadWithError on your delegate, the bridge no longer receives or responds to any JS messages passed, as if the bridge connection is severed. In my case, I reload links into the same web view, so after a single failure, no subsequent loads handle JS messages.
The text was updated successfully, but these errors were encountered: