[BUG] Client shows auto uploaded image in both "uploaded" and "failed" section
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 4.2k
- Forks
- 3.1k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 7
Description
Actual behaviour
-Tell us what happens
An auto uploaded image was uploaded (shows up in "uploaded" section on android client, and shows up on the server) but also showed up in the " failed (tap to retry)" section with the error "the file was not found in the local filesystem" even though I can still see the image in the photo manager app. Note that "the file was not found in the local filesystem" error is intermittent, but has happened a few times.
Expected behaviour
-Tell us what should happen
The file should upload successfully with no failures
Steps to reproduce
- Take an image
- Wait for error to appear
Can this problem be reproduced with the official owncloud server?
(url: https://demo.owncloud.org, user: test, password: test)
Not tested
Environment data
Android version:
13
Device model:
Samsung A53
Stock or customized system:
Stock
ownCloud app version:
4.1.1
ownCloud server version:
10.10.0.3
Logs
Web server error log
None
ownCloud log (data/owncloud.log)
The only notable log was from when I tapped "retry" on the failed download the server issued:
Integrity constraint violation: 1062 Duplicate entry
which makes sense since the phone had already uploaded this file
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the Android client’s auto-upload flow and the state handling for the “uploaded” and “failed” sections; reproduce the issue by taking an image and waiting for the error. Use the reported filesystem error and duplicate-entry log to trace the intermittent failure. Done means an already uploaded image is not also shown as failed, and retry does not create a duplicate entry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100