Export unsucessful or importing

[Coacheng]

Trying to export off iPhone (Have previously been successful) now everytime is unsuccessful and states same on importing!!!

What could make this happen?

Coach Eng

[FTMSupport]

The only thing that should be causing Export to fail would be lack of internet connectivity. Either no internet connection, or poor internet connection. You should not be trying to import if you have been having failed exports however... an import will overwrite your existing database.

To confirm connectivity to our servers, open Safari on your device, and try browing to http://iscorecentral.com" onclick="window.open(this.href);return false;. If that comes up on your device, it confirms your device is talking to our servers fine, and you should be able to do an export.

[plivengood]

This is a somewhat related issue that may be a bug. I am using the iPad version of the app, up-to-date. The last few times when I have returned home after a game and want to e-mail stats (to "web me@mydomain.com") I have been getting an unsuccessful message even though the e-mail is going through and the scorecard is being posted on our web site. I am not particularly bothered by this - just reporting it in case it may be a bug....

[plivengood]

I should add, too, that poor Internet connectivity is not the issue, and the export I do (very next thing) is always successful....

[FTMSupport]

If you are sending to "web me@mydomain.com", we could see that returning an error. We have the "web" option to post the scorecard to your team website, but that should only be used when you don't also want to email to yourself. You should be able to email to just "me@mydomain.com", and the server will still save the scorecard to your team website. Entering both will cause our server to try and actually send an email to "web" and also to "me@mydomain.com", and thus the error.

[Coacheng]

THis is the second conversation on this. I have great connectivity on my iPhone and can use every other application EXCEPT your export or import.

Please do not belittle and utilize the same generic answer.

I am presenting you a "BUG", "GLITCH" or whatever you want to call it. There is something otherthan the "INTERNET" connection going on.

[FTM Edit: removed personal information]

[Coacheng]

Should add also tried emailing the stats from the last game entered and was "Unsuccesful" per iPhone but checking email I did recieve a email but was only 1/8 of the regular information was received.

[OhioTex]

coach end

caution. be carful testing import. if you do that it will overright all your data on your handheld. keep focusing on fixing export before you try to test import

first, Have you any other issues with iscore on your handheld, or wiped out data or deleated data lately?

second, can you log onto your web based admin site successfully?

[FTMSupport]

When somebody posts generically that they can not export, all we can post back is a generic answer. If this were a bug, then every other user would be having the same issue, but we are receiving thousands of exports to our server every day.

We see now that we have had interations with you directly in email (no way to know that from your original post). When it is a specific case like this, email is going to get the most personal answers.

Have you tried updating to the version of the application that was just approved in the App Store (version 2.75)? It is possible that your version somehow got corrupted. It is probably best to continue the troubleshooting by contacting us directly at support@iscorecentral.com.

Thank you.

[iscore@tragus.org]

I have export failures about 1-in-10 times myself. In my case, however, I can always trace it back to a connectivity issue. AT&T's network is well known to have capacity issues and, of course, FTM's servers themselves are likely to experience high demand on weekends (when I generally have issues). Sometimes it is FTM's servers -- diagnosed by browsing to iscorecentral.com -- and other times it is AT&T -- diagnosed by browsing elsewhere and checking my email. I don't have a wi-fi setup (too many security issues there) but that would be another way to narrow down the problem. That is, if export fails over wi-fi it is probably an issue with the FTM servers since the AT&T mobile network is taken out of the picture at that point. On the other hand, if export over wi-fi succeeds I would have to suspect that the AT&T network is/was the issue.