Graphics recovery across map workspaces
Watchtower’s shared MapLibre renderer has been updated, with handling for graphics-context loss, hidden and off-screen maps, and maps whose canvas dimensions are not ready. GPU-context accounting now includes first-party frames and globe viewers, and inactive globe graphics are released while their selections are retained.
Workspace scripts load independently while preserving each workspace’s declared dependency order, reducing the chance that an unrelated slow script blocks a map from opening.
Why text sometimes appeared instead of a map
Some map providers return a picture saying ‘Map data not yet available’ with a successful HTTP status. Watchtower now requests explicit missing-tile responses for the affected Esri services and respects published terrain detail limits. Provider coverage gaps can still occur, but they are distinguished from graphics failures rather than treated as valid map imagery.
More useful App Health evidence
Repeated reports now retain their first evidence while updating the latest diagnostics and reporter information. Repeated failures cannot lower an existing severity. Renderer exceptions carry structured, redacted stacks, public runtime versions and map/context counts, with visible maps prioritized within the bounded diagnostic payload.
The admin dashboard labels map-provider and renderer issues separately and keeps expanded diagnostics open during same-account refreshes. Private data is loaded only after admin-session verification.
Load the update
Reload Watchtower to load the updated map code. Older open browser sessions can continue running the previous renderer until refreshed. Map-provider availability and browser graphics capabilities still affect what can be displayed.