Summary:
When viewing November 1st (daylight saving time end) in the Activity app, the app crashes. The rings show inaccurate data. Achievements that rely on this data (i.e. Move goal streak) are no longer accurate.
Steps to Reproduce:
Open Activity app.
Select November 1st.
App crashed before loading accurate data. Move ring does not reflect actual calorie burn for the day.
Expected Results:
No crash. App data should load and move data should continue to count for future achievements.
Actual Results:
App crashes in all circumstances when attempting to view data from November 1st. Rebooting phone does not solve the issue.
Version:
9.1 (13B143)
Notes:
I can very clearly see the bug here because I ran a marathon that day and should have had 4000 calories burned in my move goal. It only shows 562 before crashing. Not sure why it cuts off there.
Configuration:
Occurs under all circumstances following DST time change.
Description
Summary: When viewing November 1st (daylight saving time end) in the Activity app, the app crashes. The rings show inaccurate data. Achievements that rely on this data (i.e. Move goal streak) are no longer accurate.
Steps to Reproduce:
Expected Results: No crash. App data should load and move data should continue to count for future achievements.
Actual Results: App crashes in all circumstances when attempting to view data from November 1st. Rebooting phone does not solve the issue.
Version: 9.1 (13B143)
Notes: I can very clearly see the bug here because I ran a marathon that day and should have had 4000 calories burned in my move goal. It only shows 562 before crashing. Not sure why it cuts off there.
Configuration: Occurs under all circumstances following DST time change.
Product Version: 9.1 (13B143) Created: 2015-11-03T14:40:02.270090 Originated: 2015-11-03T00:00:00 Open Radar Link: http://www.openradar.me/23374091