Crashing on 2.01.03 on minor lineup change.

[djandyo]

Thanks for clarifying OhioTex! The application is incredible! The 2.0 version is simply amazing! I am not even remotely discouraged by these minor issues. I would highly encourage anyone to download it as well. I am positive FTM is working hard on getting these fixed.

With 2.0.1, I did have the reordering line-up issue on mine when it crashed on #1 (Changing the side of the plate). Once I got back into the app, it was slightly out of order. Very easy fix however. It crashed again later and didnt have that issue at all.

[barkmo]

OhioTex

Nice job locating the exact scenario that causes the crash. I followed your 'batting all' section and got the same results. I was experimenting with a test game and will remember that for our next game.

[barkmo]

OhioTex

Nice job locating the exact scenario that causes the crash. I followed your 'batting all' section and got the same results. I was experimenting with a test game and will remember that for our next game.

[plivengood]

To detail the issues I had:

(1) I got the opposing team's line-up late, but since I *did* know their roster, I didn't want to use quick roster, but instead tried to juggle players within the starting line-up as I went. I had previously tied positions to players in team manager, so I had a lot of correcting to do for defensive and offensive positions. In a couple of instances, I forgot to unclick "batting" after marking the player "out" and consequently had players in the line-up who weren't even there. I corrected this (through starting line-up) when I noticed it, but I think this was already after one turn of the line-up, which was when I noticed players at bat not matching what was being shown. After having read a fair amount around this issue, I think this is not a bug but the way the program is designed (my understanding: you can move players in line-up positions, or add/remove players to the starting line-up, but not after you turn the line-up once; this is a problem for tournaments that allow a player to be added at any time if he shows up late, to the end of the line-up). However, as you can imagine this resulted in a severely screwed-up scorebook.

(2) As this was only the second time I had used the app, a lot of people were curious and I tried to go to the scorebook view a couple of times only to see the app crash out of iScore and go to the main iTouch screen. When I got back in, the line-up (again, using 2.0) had reverted to the line-up as it had originally been entered in Team Manager, prior to the changes I made to the starting line-up. This also happened in at least one other situation (I think it was a substitution) but I don't remember enough of the details.

I score for youth baseball (12U) and the rules allow either bat the order and full substution, or bat none with subs and one re-entry. One team can choose one thing, and the other the other, which makes for interesting scoring challenges, as they don't often tell you much other than give yoy a line-up minutes before "Play Ball!"

Part of the problem is I figured as a noob I was making mistakes and, in the interest of learning and getting better, I "re-scored" the game and deleted the old, so I can't forward the game for examination. This season is nearly finished for me, and every game I score I have somebody scoring on paper as a back-up (to preserve the integrity of the stats I gathered "the old-fashioned way") so I am happy to score this weekend's games and pay closer attention to exactly how/when these problems occur. I did subsequently upgrade to 2.01.03 and some of my issues may be resolved.

[FTMSupport]

Thanks for the details plivengood.

For #1, yes, once you bat through the lineup, increasing/decreasing the number of players in the lineup will cause issues. We have a fix now so that it will not crash if you do this, but there is no way we would be able to reconcile the stats correctly in this scenario as we expect the number of batters in the lineup to be constant after you have batted through the lineup one time. You can substitute for players, and the stats will be correct, but you can not add/delete players from the original lineup after batting through one time. (NOTE: If anyone does do this and is having a crash, you can easily fix the situation by going to the Pitch by Pitch editing, and set the lineup at the beginning of the game to the correct number of batters --- there are more detailed steps in several spots in the forum.)


For #2, we also believe we have addressed this with a combination of the 2.01 release, and a new 2.02 release that we just posted to the App Store today that addresses some less common scenarios (alternating batter=Yes, batter=No, and some other small issues). We will be posting another thread detailing what was fixed in 2.02, and are hopeful that Apple can give it similar fast treatment like they did for 2.01, though it is not of the emergency nature that 2.01 was (the issue 2.01 addressed with Team Stats could have impacted old games as well which would have been bad for customers with a lot of games already in their database).

Thank you.

[OhioTex]

on #1 - an idea.. Could iScore trigger a user message if someone tried to add/delete a player after batting through the line up. something like...

"Line Up Locked. Have Batted the Order. Can Skip Batters (out or no out) by the Misc menu. But Can not add/deleate a new batter after batting line up is locked. Stats would be garbage.

[FTMSupport]

Yes, we will be doing something like this in a future version. Thank you.