Events were fetched with runCatching{}.getOrDefault(emptyList()), so any
network/deserialization failure looked identical to "no concerts". The
backend + Ticketmaster work (verified), so the failure is client-side.
- EventsClient: expectSuccess + timeouts so a non-2xx (e.g. an SSO/HTML
redirect) becomes a real exception instead of an obscure body() failure.
- ArtistViewModel: capture the failure into eventsError (+ Logcat) rather
than defaulting to empty.
- ConcertsSheet: show "Konzerte konnten nicht geladen werden" + the reason
when the fetch failed, vs. "Keine Konzerte angekündigt" when genuinely none.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
HoneyandClaude Opus 4.8
f27eaf9c82