iOS6 - Apple Bug causing Slowness in iScore
Posted: Wed Nov 21, 2012 8:02 pm
OK... after countless hours of testing and feedback from you guys in the forum and emails, we have finally identified the issue.
Apple introduced a Bug in iOS6 related to something called the UISegmentedControl. We have not seen any documentation of this bug anywhere, so will be submitting the details to Apple on how they can reproduce and fix the issue. If Apple had any kind of "find a bug" reward, the iScore community would deserve one for this.
The UISegmentedControl in the case of Baseball is what allows you to tap the Inning # above the Pitch by Pitch data on the iPad.
In Basketball, it allows you to select the Period in a similar fashion.
Updating a UISegmentedControl repeatedly slowly does something internally in iOS6 that makes the future updates slower and slower until eventually it is so slow that it is unbearable.
We will be submitting updates to both Baseball and Basketball today that work around this issue (we are rejecting the current Basketball update and resubmitting since the previous update did not include this fix). We are going to request priority approval on this fix since it is an Apple Bug that was the cause, but being a Holiday week, who knows if that is going to help.
This same message is being posted in both the Baseball + Basketball Forums.
Apple introduced a Bug in iOS6 related to something called the UISegmentedControl. We have not seen any documentation of this bug anywhere, so will be submitting the details to Apple on how they can reproduce and fix the issue. If Apple had any kind of "find a bug" reward, the iScore community would deserve one for this.
The UISegmentedControl in the case of Baseball is what allows you to tap the Inning # above the Pitch by Pitch data on the iPad.
In Basketball, it allows you to select the Period in a similar fashion.
Updating a UISegmentedControl repeatedly slowly does something internally in iOS6 that makes the future updates slower and slower until eventually it is so slow that it is unbearable.
We will be submitting updates to both Baseball and Basketball today that work around this issue (we are rejecting the current Basketball update and resubmitting since the previous update did not include this fix). We are going to request priority approval on this fix since it is an Apple Bug that was the cause, but being a Holiday week, who knows if that is going to help.
This same message is being posted in both the Baseball + Basketball Forums.