fix(inventory): recover from a stuck loading spinner
The inventory stream subscription had no onError handler, so a transient failure at startup (e.g. the encrypted DB not yet ready) went unhandled and left loading=true forever — the spinner that only a restart cleared. Handle stream errors: drop out of loading, surface an error state, and offer a retry that re-opens the stream. Add a _LoadError view (i18n en/ es/ast/pt) and cover both the failure and the retry-recovers paths.
This commit is contained in:
parent
bb4ee2fd89
commit
f45c452615
12 changed files with 158 additions and 17 deletions
|
|
@ -132,7 +132,9 @@
|
|||
"noMatches": "Ninguna semilla coincide con los filtros.",
|
||||
"clearFilters": "Quitar filtros",
|
||||
"uncategorized": "Sin categoría",
|
||||
"needsReproductionFilter": "Por reproducir"
|
||||
"needsReproductionFilter": "Por reproducir",
|
||||
"loadError": "No se pudo abrir tu banco de semillas. Quizá estaba ocupado: inténtalo de nuevo.",
|
||||
"retry": "Reintentar"
|
||||
},
|
||||
"draft": {
|
||||
"capture": "Capturar fotos",
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue