Previously uploaded photos get rescheduled for upload
Bug #926324 reported by
Matt Griffin
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu One Files App for iOS |
In Progress
|
Medium
|
Zachery Bir |
Bug Description
I've deleted many folders and files from my iPhone's photos UDF from my desktops (both Ubuntu and Windows) and from the web but they still show up in the iOS app even after forcing a refresh and killing the app.
Steps to recreate:
1. take some photos with your iOS device
2. launch U1Files w/ auto-upload enaled and upload them to U1 into the device's UDF
3. close the app
4. go to your desktop. after the files have downloaded to the desktop move the photos out of the UDF into another folder (e.g. desktop)
5. launch U1Files again
6. go to the Uploads tab
U1Files will think that it needs to re-upload the photos. The app displays the list of photos as in a Pending state.
Changed in ubuntuone-ios-files: | |
assignee: | nobody → Ubuntu One iOS Client Team (ubuntuone-ios-client-team) |
Changed in ubuntuone-ios-files: | |
status: | New → Confirmed |
Changed in ubuntuone-ios-files: | |
status: | Confirmed → In Progress |
importance: | Undecided → Medium |
assignee: | Ubuntu One iOS Client Team (ubuntuone-ios-client-team) → Zachery Bir (urbanape) |
description: | updated |
summary: |
- App still displays folders and files that have been deleted + Previously uploaded photos get rescheduled for upload |
To post a comment you must log in.
I see an occasional app crash due to be a bad retain / release cycle involving the docController found in U1FilePreviewVi ewController and U1FileDetailsVi ewController. Depending on events I could see where items presumed deleted might not actually get deleted since the commends didn't get called. However in my own testing files / folders were being deleted as long as the app didn't crash.
My patch is commit #56 in lp:~tom-gall/+junk/ubuntuone-ios-files
That said a device log via apple's developer site would be quite helpful. A crash log or two would help. (Perhaps that is why the bug is marked confirmed but a paste of that information would be quite helpful to validate.