File Upload Conflict on Every Modification/Upload

Abierto
#17,883 1 comentario 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
45/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
android, kotlin
Área
mobile

Línea de trabajo

Start by tracing the Android app's auto upload and internal two way sync flows, then inspect how they detect and resolve conflicts for modified files. The report provides reproduction steps and expected behavior, but names no code entry point or test. Done means local modifications synchronize to the server without prompting for a conflict each time.

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

Descripción

0. Needs triage bug
⚠️ Before posting ⚠️
  • This is a bug, not a question or an enhancement.
  • I've searched for similar issues and didn't find a duplicate.
  • I've written a clear and descriptive title for this issue, not just "Bug" or "Crash".
  • I agree to follow Nextcloud's Code of Conduct.
Steps to reproduce
  1. Setup "Auto upload" and "Internal two way sync" for a folder (not sure if both is necessary but this is nevertheless my setting because of bug #16996 …)
  2. Modify an existing file
  3. Get the "file upload conflict" message: Click on "Resolve" and choose the local version.

This message appears every single time I modify a file.

Expected behaviour

It should just synchronize the local changes to the server.

Actual behaviour

The warning message appears on every local modification. It even correctly shows the respective timestamps, but still asks me every single time if it should keep the freshly updated version or the old version from the server. That's ridiculous.

Android version

17

Device brand and model

Google Pixel 8 Pro

Stock or custom OS?

Custom (explain in "additional information")

Nextcloud android app version

35.0.1

Nextcloud server version

34.0.5

Using a reverse proxy?

Yes

Android logs

No response

Server error logs

Additional information

GrapheneOS but shouldn't matter.

Lenguaje dominante
Kotlin
Estrellas
5.7k
Forks
2.1k
Merge medio
1 d 22 h
PR fusionados (30 d)
135

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

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/android

Todos los issues de nextcloud/android

Issues similares

Más issues de Kotlin

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.