File Upload Conflict on Every Modification/Upload

未关闭
#17,883 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
android, kotlin
领域
mobile

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
Kotlin
星标
5.7k
派生
2.1k
平均合并
1 天 22 小时
30 天内合并 PR
135

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

nextcloud/android 的其他 Issue

查看 nextcloud/android 的全部 Issue

相似的 Issue

更多 Kotlin Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。