Last modified: 2013-05-31 21:57:11 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T49614, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 47614 - First load of My uploads freezes app, then refresh continues indefinitely but only earliest 500 contribs show
First load of My uploads freezes app, then refresh continues indefinitely but...
Status: RESOLVED FIXED
Product: Commons App
Classification: Unclassified
iOS (iPhone or iPad) (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-04-24 15:35 UTC by Sage Ross
Modified: 2013-05-31 21:57 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Sage Ross 2013-04-24 15:35:25 UTC
On iPhone 3Gs, I just installed the App Store version and logged in.

The My uploads screen was unresponsive for several minutes (although I could pull down the notifcations thing or whatever iOS calls it). After that, it sent me back to the accounts screen, and when I pressed log-in again, it showed my oldest 500 uploads.

Refreshing after that basically causes unending resfresh spin (5+ mins to no effect), but no additional photos appear except the oldest 500.
Comment 1 Brion Vibber 2013-05-13 20:03:19 UTC
In latest code first load should be less painful, but we still have to modify to fetch more than 500 items.
Comment 2 Brion Vibber 2013-05-21 19:58:20 UTC
In latest beta, should work with more than 500 items... May still be slow on initial load, but should be less awful than before. Please test. :D
Comment 3 Monte Hurd 2013-05-31 21:57:00 UTC
This should be resolved on the next release. When the new release comes out, completely delete the app and re-install to confirm bug is gone.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links