Page 1 of 1

Replacement IPAD 2

Posted: Mon Mar 12, 2012 7:12 pm
by Rkeaney
Sorry for reposting. I have seen several other areas that discusses this but none seem to fix my issue.

I got a new IPAD2 today and restored from icloud. The user identifier on the new IPAD changed and when I go to my.iscorecentral.com, everything appears to be correct with the exception of the website. The app prompts me create a new website. When i enter the old website, i get an error that the website is already taken (as expected).

How do i fix this. All my teams, leagues, players, etc are accurate but on the new IPAD, when i look at the player card, i dont see any photos as the app is not speaking to the team website.

Thanks in advance.

Re: Replacement IPAD 2

Posted: Mon Mar 12, 2012 7:19 pm
by FTMSupport
Email us at support@iscoresports.com with the URL of your team website, and the Customer ID of your new device (found on Options screen in iScore), and we can update your team website to start pulling data from your new device.

Re: Replacement IPAD 2

Posted: Tue Mar 13, 2012 6:44 am
by mprusak
FTM - you get this request a lot. Is this something you can make user-updateable?

Re: Replacement IPAD 2

Posted: Tue Mar 13, 2012 9:49 am
by FTMSupport
Even making it user udpateable would not prevent this request as half the time people don't even realize that the new device is the cause. If Apple gave us a way to identify devices associated with an account we may be able to do something more automated, but they do not provide any such API.

Re: Replacement IPAD 2

Posted: Tue Mar 13, 2012 6:59 pm
by OhioTex
to all reading, this has been said many times. customer id is tied to a physical device, when you get a new/different physical device. FTM has to manually link the new device id to the existing team web site, because it was associated with the pevious device.

Re: Replacement IPAD 2

Posted: Wed Mar 14, 2012 7:30 am
by mprusak
FTMSupport wrote:Even making it user udpateable would not prevent this request as half the time people don't even realize that the new device is the cause. If Apple gave us a way to identify devices associated with an account we may be able to do something more automated, but they do not provide any such API.
Good point...too bad...Apple is pretty good at is selling new devices (in case you hadnt noticed :-))...this headache is only going to get worse...