v3.40, iPhone: Location of hits gone crazy!

[FTMSupport]

We see your movie, but are unable to reproduce this issue on our test devices. Unless we can reproduce the issue, there is not going to be much we can do about it. We have responded to your email with a request for some more information.

[Danger]

Information has been sent. It looks like saboda53 was having the issue on an iPhone while my device is just an old iPod Touch. But maybe we're running the same iOS. Good luck!

Looks like you guys work all night long so either this is freaking you out, too, or your Customer Support is off the charts! Probably both.

[m_churchill]

I'm getting exactly the same thing on a 2nd generation iPod touch - i.e. NOT upgradable beyond iOS 4.2.1

[FTMSupport]

We have tried on every device we have to try and reproduce this issue, and have just not been able to do so. If anyone happens to have the issue and lives in the Southern California area and would be willing to meet us somewhere, we can take a look. Just email us direct at support@iscoresports.com.

[Danger]

I'm on the other coast, but since it's starting to turn cold here, I'd be happy to have you guys fly me out there! Or, if you'd like to buy me a new iPhone, I'd be willing to send you my iPod Touch in the mail. You can just take it out of the R&D budget, right?

No? Ok, just a thought.

Seriously, however, if you don't have any takers and if there's anything I can walk thru with you over the phone, I'd be happy to do so.

[Danger]

In the meantime, is there a way for me to "un-do" the latest software upgrade to go back to the previous version?

[FTMSupport]

You would have to talk to Apple about an undo.

[Roloyank]

I have the same problem in my ipod touch since an the last update. Please resolve this problem soon.

[FTMSupport]

We have now been able to reproduce with an iPod Touch specifically with v4.2.1 of iOS. We are working on a fix.

[FTMSupport]

It turns out the issue is with Apple's LLVM compiler (new default for iOS 5 builds). The "Optimization Level" in the compiler was set to the "Fastest" setting (always has been), and it started stripping some of our logic out. When we turn off the code optimization, things would work fine.

We were able to come up with a workaround for their optimization bug, and have this fixed for the next release.