http://iscoresports.com/

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.

Keep in mind that until the updates become available, doing the following prior to scoring a game will ensure the best experience:

1. Exit out of iScore completely.
2. Double tap Home button to bring up running apps in bottom tray
3. Press and hold iScore icon in bottom tray until it starts shaking. Press the "-" to stop iScore from running (if you see an "x" instead of a minus, it is the wrong one ... do not press that. Start over at step 1)
4. Press and hold the power button and home button on your device until the Apple Logo appears (this is a hard reset)


It seems the slowness really starts kicking in for baseball after about 200-220 pitches and gets worse fast from that point. That would explain why people sometimes report it starts in the second game of a double header.

All of us in the iScore community offer a very large thank you to FTM for their, in sure, thousand of hours spent attempting to solve the problem. Once again FTM come thru.

Well said Brian!

Way to persist FTM. A virtual TIP of my cap for your efforts on this

Thanks for all of the efforts FTM. This is a huge effort to track these types of bugs. I know I speak for many when I say kudos and thanks for all of your excellent customer service.

iScore Baseball Version 3.55 for iPad is now available in the App Store and includes the fix for the slowdown.

Thank you for the tremendous customer support.

I just re-downloaded from the App Store, but the main screen shows the version as 3.54.114. Does that mean that I am still getting the older version without the fix?

In our rush to get the fix out for this, we forgot to update the version number on the title screen. As long as no updates are showing as available in the App Store on your device for iScore, then you should be on the most recent version if you just updated.

I scored two games last night with the latest update. I still had the slowdown issue even with iOS 6.01. This update fixed it. Everything went great. I scored both games and did not have to power cycle my iPad at all. Awesome work FTM.

I noticed something else I was wondering about. I have an iPad 3rd gen and I normally Scorecast my games. I turn off bluetooth, wifi and LTE and just use 3G cellular for the Scorecast. I can normally barely last scoring three games without charging on a full battery. Last night, I scored both games and my battery level was only down to 73%. In the past, two games would have left me at 35-45% battery level. Has anyone else noticed this?