Other things I've noticed:

If I play a game with settings other than the default (ie not 5 overs/bat first) and then go back to play another game the settings will say whatever type of game I've just played but starting a game will always start a 5over bat first game.

The " you've just beaten your record score" message pops up twice, before and after the match result message (occasionally after a score that wasn't my highest)

It would be good to be able to select difficulties or targets for the bat to a target option - playing 50 overs I keep being given targets of 75-80 runs

I've noticed the following also:

1 - occasionally during a normal game, 2 balls will be bowled ala blitz mode
2 - there's definitely a problem with selecting the length of the game. I've selected 50 overs but only get a 5 over game. Maybe something to do with quiting the game sand then coming back to it. (game running in background - iOs 4.0?)
3 - with the sound turned right down, there is occasionally a short burst of crowd noise. This can be disconcerting. If phone is on vibrate, I don't believe it happens.
4 - Sometime obvious sixes are only scored as 4
5 - again, occasionally, I see a bowler bowl consecutive overs - haven't yet determined under what circumstances.
6 - For the away team, position 7 is the wicketkeeper but is identified as Bowler (Pace) when editing.
7 - Home team batting first (may be irrelevant) if the first and second players are run out, only the first seems to be recorded in the scorecard. The score is still 71/2, for example, but the scorecard only shows the first batsman run out

And another thing (sorry)

I just quit a game mid over, then continued from where I left off and a new bowler started the partially completed over. (A different bowler had bowled the previous 2.3 overs)

I've just restarted my ipod touch (the battery ran out) and now playing flick cricket some of the problems seem to be sorted - the red arrow has gone, the bowlers only seem to bowl one over at once and the batsman facing changes between overs as it should. I updated to 1.04 over a week ago, but maybe the update wasn't completed because the program was still open with the multitasking in iOS 4.0?

Couple of other nits I've seen:

1 - If the ball goes the strikers end on a run out (going for a single), the striker is out, even though he would be running to the non-striker's end. Similarly if the ball goes to the non-striker's end (when going for a second run) the striker is also out. I think the striker is out in all run out cases.

2 - There's still an issue where if a bowler takes a wicket with the last ball of an over, the AI bowler does no change at the start of the next over.