Coming back to the app after a few minutes in the background replaced the
Frasier series page with "Failed to load item". Android cuts a backgrounded
app's network, the app declares the server offline, and on resume the
reconnect and offline-filter reloads refresh the page. Every backend call in
that refresh answered from the cache, yet something in it threw, and:
- any throw replaced the whole page with an error, although it was a
refresh of content already on screen;
- no later successful reload of the same item cleared that error, so it
stayed until the viewer navigated away;
- the catch logged nothing and turned every non-Error value (backend
errors arrive as plain strings) into the generic text, so neither logcat
nor the screen said what failed.
A failed refresh now keeps the page and logs the value actually thrown;
every successful load clears the error; failing to open an item still shows
one, with the backend's own message. The decision lives in
detailLoadError.ts so it is unit-tested.
The throw itself is not yet identified - the next occurrence names itself
in the log.
DR-297, UT-267.
