`onHtmlUrlChange` callback is sometimes unreliable

[smithemely]

The onHtmlUrlChange callback in B2CWebViewParams is proving to be unreliable, as it sometimes fails to trigger on URL navigation. This behavior seems to be intermittent and difficult to reproduce consistently.

---

• The issue occurs when navigating between pages in a multi-step flow, such as from a phone input page to the OTP verification page.
• At the moment it has only been observed on real iOS devices in release builds (TestFlight/Production), not during local debugging from VSCode or on simulators.
• Once the callback fails, it remains unresponsive for that webview instance. Attempting to reinitialize with initWebView does not resolve the issue, resulting in the OTP page failing to provide callback after the phone input step.

This inconsistency makes it difficult to reliably manage UI state (e.g., loading indicators), which in turn prevents the user from authenticating.

---

Has anyone else encountered this? As a potential workaround, would onPageStarted be a more robust callback for tracking navigation changes? Or does it rely on the same underlying mechanism and likely suffer from the same issue?