Blank screen after failed asset fetch; progress-bar callback throws null play exception

Abierto
  • ¿Algo no está bien?
#733 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
56/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
csharp, docker
Área
frontend, web-dev

Línea de trabajo

Start by locating the slideshow asset loading and progress-bar completion callback in the SvelteKit client; the report does not name source files or tests. Reproduce with Android WebView if possible, then trace the failed /api/Asset request and the null play exception in the captured logs. Done means an asset fetch failure no longer leaves the slideshow, clock, or progress bar blank.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug
Version

v1.0.39.0

Deployment Method

Docker for server, android app to render

Description

Docker server behind Traefik HTTPS reverse proxy, displayed using the official Android app in WebView mode.

Client: generic Frameo/RK312x frame, Android 6.0.1, 1280×800 display, approximately 1 GB RAM.
ImmichFrame Android app: 1.0.51.0 (v51).
Android System WebView: 106.0.5249.126.

After displaying photos normally for some time, the frame intermittently shows a blank/black screen. The clock and progress bar both were missing. Sometimes this is 2 hours, sometimes this is 30 minutes. Maybe this is due to a specific asset from the Immich server. I now just have a continuous webview diagnostics capture running.

An /api/Asset fetch failed with net::ERR_FAILED, immediately followed by:

ProgressBar onDone failed:
TypeError: Cannot read properties of null (reading 'play')
at Object.je [as onDone] (…/_app/immutable/nodes/2.LHyEKK39.js:31:3378)

The DOM subsequently contained the offline/connection-error page, with no image or video elements, while the physical screen appeared black. It recovered automatically after around30 seconds. Earlier blank-screen occurrences persisted until the viewer was refreshed.

Sleep/Active Times is off during diagnostic capturing. No input, manual reload or app restart was performed during recovery.

Potentially related:
https://github.com/immichFrame/ImmichFrame_Android/issues/28

No HTTP response/status was captured for the failed request.

Reproduction
  1. Connect the official Android app to the Docker-hosted ImmichFrame server using HTTPS.
  2. Enable WebView mode and disable Active Times.
  3. Leave the slideshow running normally.
  4. Intermittently, the display becomes blank/black.

The issue is intermittent; I do not yet have a deterministic trigger. The latest recorded occurrence followed a failed asset-list request during slideshow advancement.

Expectations

If an asset fails to load, it should not break the whole slideshow. The clock and progress bar both were missing.

Configuration
Relevant client/display settings:
- Android WebView mode enabled
- Active Times disabled
- Clock and progress bar enabled
Logs
11 November 2026 — approximate CET recorder receipt times:

23:56:41.359  GET /api/Asset failed: net::ERR_FAILED
23:56:41.417  ProgressBar onDone failed:
                 TypeError: Cannot read properties of null (reading 'play')
23:57:04      DOM: offline/error page; zero images or videos
23:57:09.856  Main-page navigation recorded, consistent with automatic error reload
23:57:13.384  GET /api/Asset returned HTTP 200
23:57:34      DOM: loaded foreground image and background thumbnail
Pre-Submission Checklist

  • This is a bug report and not a feature request

  • I have provided all of the required information to reproduce the bug (config, logs, etc.)

  • I have checked for related issues and checked the documentation

Lenguaje dominante
C#
Estrellas
2.4k
Forks
121
Merge medio
18 d 20 h
PR fusionados (30 d)
1

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de immichFrame/ImmichFrame

Todos los issues de immichFrame/ImmichFrame

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.