http://iscoresports.com/

@support, Can you research this issue on reported difference of behavior on ANDROID and IOS. it does not track with me but i can not test on ANDROID

randy21m wrote:.Another thing to note (ON ANDROID), if you enable a league and do an export, all of the scorecasts are then visible again on the website - if you're just going to the generic http://www.iscorecast.com and entering the device ID. I tested this on iOS and it does NOT import the scorecast back to the website. You have to manually go into the game and do a Sync per game. Just something to note as I ran into that after I removed everything, then when I went back to view the other league I did an Export (forgetting to turn the other leagues off) and all of the scorecasts were listed again on the iscorecast.com page.

source:viewtopic.php?f=5&t=11997

The way this came about, I created a new league, went to iscorecast.com (with device ID), and all the games were there. I removed them from my admin website, then disabled the expired league on my tablet, all was good, and only the game(s) for the new league were on the site. A couple of days later I re-enabled the expired league to review some stats from the expired league, and I forgot to disable it before I did an export. Later that day a parent informed me that all the "old" games were there again. So I repeated the same process, and all has been good with the expired league disabled.

After switching back to my Android as the Master device, I imported my DB (from the changes I had made while the iPad was the Master). I then enabled an expired league that had scored games, and exported my data back up to the server with the expired league still enabled. Alas, no scorecasts were synced back up to the site.

Although my initial results were different, we can chalk this one up to user error for now as I am unable to replicate it again.

Thanks!

@ support - I think we can pass on this for now.

@ randy, thanks for the update

randy21m wrote:Although my initial results were different, we can chalk this one up to user error for now as I am unable to replicate it again.
!