Version 2.01 provided an emergency fix related to using Team Stats, and Version 2.02 addresses the remainder of the issues that were found with the 2.0 release including the following:
- Fixes remaining issue that could cause lineup to revert to roster order in some situations
- Run scoring on Pickoff Attempt was not getting credited to runner
- Dropped third strike on pass ball was not being counted as an error in fielding stats
- Run would not show in pitcher stats when run was scored as the result of On the Throw, Defensive Indifference or Pickoff Attempt
- End Inning being pressed by user now shows in pitch by pitch listing
- Viewing pitching stats for home team shows visitor team name from Game Manager (though the actual data is correct, just the title was wrong)
- If > 15 fouls in a single at bat, would cause a crash when viewing the scorecard
- Fixed box score issues that would cause "-" to not appear in some situations and runs to not always appear correctly
- Fixed issue with Batting=No players being interleaved with Batting=Yes players in lineup
- Fix of crash when clicking batter to go to the sub screen and making a defensive substitution instead of an offensive substitution when no defensive fielder position was selected (blue)
MEMORY ISSUES
After a lot of research, we believe we have also identified why there seems to have been an increase in the number of memory related issues being reported lately.
It appears there is a bug in iPhone OS 3.0 that causes memory to leak every time an image is moved around on the screen. This means any time you use any of the "scroll" capabilities in iScore (sliding over to the pitch location view, sliding to the scoreboard, scrolling around the stats or scorecard, etc), a very small amount of memory is leaked. Over time however, this memory leak can add up, and erratic behavior can result.
This appears to be specific to iPhone OS 3.0 - users still using OS 2.2 should not be affected by this issue. It is also not specific to iScore --- any application that has images moving around the screen (with the exception of action games as they use a different technology for graphics to achieve high frame rates) would be effected by this issue.
There are reports this is fixed in iPhone OS 3.1 which is due out in a few weeks.
The issue would be exaggerated on iPod Touch or any iPhone prior to iPhone 3GS because of the amount of memory available to the device to begin with. The iPhone 3GS doubled the amount of memory on the device, so while the leak would still be present, it would be much longer before it has any effect (the doubling of memory is total memory, not just available memory, and all that new memory now becomes available for use).
Our suggestion is that if you have not upgraded to iPhone OS 3.0, you wait until iPhone OS 3.1 comes out before doing so. For those who are already using 3.0 or 3.01 with the iPod Touch or iPhone 3G we strongly recommend powering the device off and back on before a game and in between games if there is a double header. Those using a 3GS should not be affected by memory issues.