2026.9.30.1
Pages that survive a dropped connection
A response cut off partway now ends in an error you can retry, not a frozen page, and after a crash a banner explains what happened and offers Reload.
- reliability
- hotfix
The follow-up to 2026.9.30: the remaining ways a page could freeze.
When something goes wrong
- Dropped responses — a server response that breaks off after it started no longer freezes the page. The action shows an error you can retry, and the page keeps working.
- A crash banner — if the app stops responding, a banner explains it and offers Reload.
Under the hood
- One report per crash — a crash sends one error report instead of a flood of follow-on errors, and network failures are filed as connection problems, not server faults.
- A download budget — the build fails if the app’s download grows past a set limit.