I set up a game to test the "Is that a wicket? Nah I'll stay" bug a bit more and I think that it is something caused by appealing too early. Managed to trigger it twice now off edges to the keeper.
I know that my guess is completely useless without knowing anything of how the code works, but my guess would be: Since whether or not it's a wicket is still undecided (as the keeper is still to catch the ball, and that can go wrong depending on input) the game at the time the appeal is made decides no, a dot ball, due to no catch to that point. When it's caught of course the game decides it's a wicket, but the original dot ball ruling stands, despite the finger going up animation being triggered (as well as the keeper tossing the ball to the heavens). If that's the case I guess something could be done to make it so the appeal defers any decision until a bit later by default. The odd part there though is it seems to only happen sometimes.
Interesting bug to be honest.