File Upload Conflict on Every Modification/Upload
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
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 内容生成。
描述
⚠️ 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
- 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 …)
- Modify an existing file
- 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
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
nextcloud/android 的其他 Issue
-
0. Needs triage bug
难度 2/5 1-3 小时 新手友好度 64/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 86/100
nextcloud/android#17845 · 2 条评论 ·
维护者通常 1 天内回复
-
[Bug] Lock owned by another client (e.g. Text app) cannot be unlocked from the app可能已有人在做 @falkloewert 于 28 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
nextcloud/android#17837 · 2 个 reaction ·
维护者通常 1 天内回复
-
0. Needs triage
难度 2/5 1-3 小时 新手友好度 84/100
nextcloud/android#17533 · 1 条评论 ·
维护者通常 1 天内回复
-
RC 34.1.0-01: Duplicated wording in creation menu — "New" prefix + creator name produces "New New document" ("Neu Neues Dokument")可能已有人在做 @ChristianTannheimer 于 118 天前认领。 未关闭0. Needs triage bug
难度 2/5 1-3 小时 新手友好度 85/100
维护者通常 1 天内回复
查看 nextcloud/android 的全部 Issue
相似的 Issue
-
Failures in nested test classes (Outer$Inner) are not annotated on their source file可能已有人在做 @NopeCharon 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
mikepenz/action-junit-report#1661 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
Kotlin/kotlin-lsp#309 ·
-
area:data-quality importer size:S
难度 2/5 1-3 小时 新手友好度 72/100
enorm-labs/event-junkie#5136 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 1 天内回复
-
Type: Possible bug
难度 2/5 1-3 小时 新手友好度 68/100
spacecowboy/Feeder#1318 ·
维护者通常 1 天内回复