Widget not recovering after "Failed to fetch error" appears #3935
Description
Describe the bug
I have already posted a related question on the development forum, please take a look at it first.
While I don't believe the error is produced by the widget per se, the fact it doesn't recover when subsequent successful requests go through is detrimental to the UX, as the user gets blocked from inputting the OTP while the widget is indeed still working (the "Enter a verification code instead" button disappears when the error pops up).
Issue summary:
When logging in through an email OTP, a single polling request fails consistently for a given session (usually between the 4th and 7th request since the first initial "Send me an email" request), showing the "Failed to fetch" error.
No subsequent request fails, but the widget is rendered no longer usable for that session. Logging in through the mailed magic link works as expected.
Just to reiterate, the bug that I believe should be addressed here is not preventing the actual failure (which we are still unsure what could be about as it seems to be oddly specific), but recovering from it if subsequent polling requests are successful.
Reproduction Steps
Replicating from the forum post for convenience.
- Sign in to the client app and select email as authenticator factor.
- Click Send me an Email
- Scan network requests filtering by poll and wait for about 40-60 seconds
However bear in mind these replication steps only apply for a very specific set of conditions:
- Chromium based browsers
- Main/Preview hosts (not trial/integrator-plan ones). This might not even be widespread and only be happening for certain production hosts, I don't have a way to check that, but someone else seemed to be experiencing something similar in the forum.
This same behavior can be reproduced by setting the Throttling to Offline on Dev Tools and then turning it back off after a request fails.
SDK Versions
This information might be irrelevant due to the issue being experienced when getting into the Okta Admin app as well.
The browser experiencing the issue is any chromium based one (tested with ungoogled chromium, chrome and edge). Firefox based ones seem unaffected.
System:
OS: Linux 6.17 Fedora Linux 43 (Workstation Edition)
CPU: (16) x64 AMD Ryzen 7 9700X 8-Core Processor
Memory: 50.84 GB / 60.43 GB
Container: Yes
Shell: 5.3.0 - /bin/bash
Binaries:
Node: 22.14.0 - ~/.nvm/versions/node/v22.14.0/bin/node
Yarn: 1.22.22 - ~/.nvm/versions/node/v22.14.0/bin/yarn
npm: 10.9.2 - ~/.nvm/versions/node/v22.14.0/bin/npm
pnpm: 10.27.0 - ~/.nvm/versions/node/v22.14.0/bin/pnpm
npmPackages:
@okta/okta-auth-js: 7.13.1 => 7.13.1
@okta/okta-react: 6.10.0 => 6.10.0
@okta/okta-signin-widget: 7.28.2 => 7.28.2
Additional Information
No response