# 04-Sep-2026 — keep the follow-a-route screens working when the browser cache or storage is unavailable [#382](https://github.com/nbarrett/ngx-ramblers/issues/382)

## [build 877](https://github.com/nbarrett/ngx-ramblers/actions/runs/33817828838) — [commit 0c87174](https://github.com/nbarrett/ngx-ramblers/commit/0c871744f0f14abdfde728066b1579cc1a883016)

_____

## What's new

The phone app's route following and editing screens no longer go blank or sit loading forever when the browser's route cache or local storage is blocked, slow or stuck, which is one way they could appear to be missing on a Chromebook or an Android phone. Visitors who can follow a route but are not logged in are now told that editing and recording are for walk leaders and admins, with a link to log in.

## At a glance

- The app home loads routes and walks before it asks the offline cache, so a broken cache no longer empties the page
- The follow screen still loads a route when the offline cache cannot be read, and always finishes loading
- The offline cache times out after five seconds instead of hanging when another tab holds it open
- Blocked local storage no longer stops the follow screen or the app appearance setting from working
- A note with a Log in link explains why Edit and Record are not shown to visitors who are not logged in