-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[Bug]: Retried uploads stuck in queued state #5136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I am able to reproduce this issue:
|
For the record, I used the app today to upload an unrelated new image. The "queued" image from December also uploaded, without my doing anything deliberately to initiate this, and without prior warning. |
Andy: I observed this too, I often perform a single upload to "unblock" stucked queued uploads. Far from ideal but that is a workaround. |
I can confirm both the bug and the workaround, in latest f-droid release (4.1.0~1649d1e2c) on Android 10 (EMUI 12), Huawei P30 Pro. |
Since about a month, the workaround above does not work anymore for me (master branch). Stuck upload stay stuck forever even if I upload new pictures and pause/unpause the stuck ones repeatedly. |
Summary
Copied from https://commons.wikimedia.org/wiki/Commons_talk:Mobile_app#Image_upload_stuck_at_%22queued%22 - where the only suggestion had been to ignore the issue and start a new upload]
I shared two images using the app yesterday [13 December 2022]; both failed and I retried them. The first (File:Image 70 coffee set - 2022-12-13 - Andy Mabbett - 01.jpg) then uploaded successfully, but the second (filename ending "02") is showing in the app as "queued". There appears to be no feature in the app allowing me to force the upload to start. I have forced the app to close, and restarted it, to no avail. What should I do?
Steps to reproduce
See above.
Expected behaviour
There should be a way to force "queued" uploads to restart.
Actual behaviour
See above.
Device name
OnePlus Nord
Android version
Android 11
Commons app version
4.0.5~f03b7dd8d
Device logs
No response
Screen-shots
No response
Would you like to work on the issue?
Prefer not
The text was updated successfully, but these errors were encountered: