Immediate respring when app launches and connect to server

Abierto
#4,438 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
22/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
docker, ios, swift
Área
mobile

Línea de trabajo

The payload names no source files, so start by reproducing: build the iOS app in Xcode, run it against a test Nextcloud server, and capture the crash from the device or simulator console, since the reporter saw nothing in the server logs. Find where the app connects to the server on launch and what reads the local cache at that point. Done means the crash is reproduced, its cause is identified, and the launch no longer crashes when the server is reachable.

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

Descripción

bug

Having trouble nailing this one down, but was working fine on Oct 27/29, so possibly just the last update?

iOS App v35.2.2 launches, connects to docker server 35.0.2

Immediate crash to springboard no matter which folder is open.

If I pause the server docker container, the app does not crash. I can then clear the nextcloud cache and restart the docker container which allows the app to run for a few seconds, before again crashing to springboard.

Thereafter if re-launched, immediate crash on launch if the docker is accessible until the cache is cleared again, or the docker is paused so it can't connect.

Nothing in the logs, assume it crashes before logging anything.

iPhone 16 Pro max, v 27.2 (same version that was working fine earlier in the week).

Please let me know if there's a procedure for more thorough testing/logging.

Lenguaje dominante
Swift
Estrellas
2.5k
Forks
1k
Merge medio
2 d 1 h
PR fusionados (30 d)
21

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 nextcloud/ios

Todos los issues de nextcloud/ios

Issues similares

Más issues de Swift

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.