http://iscoresports.com/

This has happened a few times in the last couple of weeks. Can't remember exact details, but will post here in case anyone else has experienced this.

When entering a play with multiple runners on base, when it asks what happened to say runner at third, I will press "safe, home, steal," or something similar, intended to advance the runner forward one base. I get the error message (paraphrased) "Are you sure? You are advancing runner to base they currently occupy." The first couple of times this happened I hit undo to recreate and the error message persisted. I finally just ignored the message and the scorecard and play by play are correct. The runner is clearly not advancing to a base they started from, so I'm not sure what causes the message. I will try to pinpoint the exact facts in case this happens again, but am wondering if anyone else has seen this.

Is this the message you see?


That message comes up when you attempt to "advance" a runner to the base they currently hold. Are you absolutely sure you are selecting the next base when you see this error? The only way I can get this to pop up is to not advance the runner (as it is designed for).

You are indicating pretty clearly that you are advancing the runner, so that is strange. If you are getting this on a sequence where the runner is being advanced to the next base, try to log the exact scenario.

That is the message, and I agree it is strange because I am clearly advancing the runner one base. I will definitely log the exact sequence the next time it occurs.

We have actually identified and fixed this. It happens when a runner is being forced to advance abase in some circumstances. The next update includes the fix.

Awesome thanks! Just glad to know I was not losing my mind.

I have seen this on a couple occasions, don't recall the exact circumstance, but recall it happened on a runner advancing home in one case. I had taken to ignoring the popup after going back to make sure that it was indeed the correct play and advance. Just never got around to reporting it, so thanks Team Mom!

Fixed in the 3.50 release we just submitted to Apple (announced elsewhere in forum).