Auto-upload conflicts, yet again -- this is a never ending problem
- Dominant language
- Kotlin
- Stars
- 5.6k
- Forks
- 2k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 92
Description
### ⚠️ Before posting ⚠️
- [x] This is a **bug**, not a question or an enhancement.
- [x] I've [searched for similar issues](https://github.com/nextcloud/android/issues) and didn't find a duplicate.
- [x] I've written a clear and descriptive title for this issue, not just "Bug" or "Crash".
- [x] I agree to follow Nextcloud's [Code of Conduct](https://nextcloud.com/contribute/code-of-conduct/).
### Steps to reproduce
1. Configure your device's photo storage for auto-upload
2. Take some photos
3. Get a notification about conflicts
4. Click notification to see conflicts
5. Click one that says "Sync conflict, please resolve manually"
6. Wait a few seconds
### Expected behaviour
File should be uploaded to the server.
### Actual behaviour
Toast message saying:
> File not found. Are you sure that this file exists or has a previous conflict not been resolved?
### Android version
16
### Device brand and model
Pixel 8 Pro
### Stock or custom OS?
Stock
### Nextcloud android app version
33.0.1
### Nextcloud server version
31.0.9
### Using a reverse proxy?
No
### Android logs
_No response_
### Server error logs
```bash
Nothing
```
### Additional information
I'm not even sure why the Android app is saying there is a conflict as I have checked the server and the file reporting the conflict does **NOT** even exist on the server.
The Android device in question is not kitted to get debug info. It is a "production" device for a user and _Developer options_ is not an appropriate security model for this device.
Ultimately this seems to be just yet another (of the many) bug(s) with auto-upload. I wish this feature could _just work_ without constantly being a bug-ridden steaming pile.
Contributor guide
Assessment
This issue has not been assessed yet.