Mac OS X 10.11.5: App Store sometimes shows NaN instead of real numbers
Originator: | igeek1 | ||
Number: | rdar://26529630 | Date Originated: | 27-May-2016 10:03 PM |
Status: | Duplicate of 26378721 | Resolved: | 15-Jul-2016 02:09 AM |
Product: | OS X | Product Version: | Mac OS X 10.11.5 (15F34) |
Classification: | UI/Usability | Reproducible: | Sometimes |
Summary: The Mac App Store sometimes shows download progress numbers as “NaN GB of NaN GB” instead of showing real numbers. Steps to Reproduce: I don’t know of any particular steps to reproduce this, other than to say it shows up under the app update progress bar. Not sure about the “installation” progress bar under the Purchased tab. I’ve included a screen recording of a case where I did reproduce it, but it just seems to happen some times and not others. I’ve seen others tweet about it. A Twitter search turned up two recent ones, for example: https://twitter.com/jaytennier/status/733662932798734336 and https://twitter.com/joshdee_52/status/734080911348637698 Expected Results: The label under the progress bar while updating apps shows only non-negative real numbers of bytes. Actual Results: The label sometimes shows NaN GB. Regression: This seems fairly recent, in Mac App Store years - maybe within the last year? But hard to say for sure. Notes: I’ve attached a screen recording, also posted here: http://cl.ly/gIz7
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!
Message from Apple Developer Relations
We need more information to investigate this issue.
Please provide a sysdiagnose output from the affected system(s). Please collect this either while the issue is occurring, or as soon after as possible (for example, take it after a reboot if necessary).
Please let us know what you were doing that caused the issue, so we can correlate your actions with the diagnostic output in sysdiagnose. Please try to focus on one or two actions that cause an issue. If you perform many different actions, it will be difficult for us to determine which action caused the sysdiagnose output.
More on running sysdiagnose:
An alternative approach uses a key command:
Please provide your response or results by updating your bug report.
Note: the attached screen recording was originally recorded for http://www.openradar.me/26529581 rdar://problem/26529581