Crash when Create New Player iPad3 (player manager team manager) (pending user action)
Posted: Fri Apr 07, 2017 1:44 pm
I've tried to add a new player under Team > Roster, as well as within Player Manager - both outcomes are the same. I click on Create New and then the app shuts down. We've been using the Ipad App for the last 3 seasons with no issues, until now.
Our primary scorebook is on an Ipad 3rd Gen - which is the one we are having the problem noted above. It has been updated to the most current version of iScore (v5.011).
Our backup scorebook is on an Ipad Mini - which is working as expected, meaning it is not shutting down when adding a new player.
I tried to use Data Share to build the players on the Ipad mini and transfer to the primary scorebook - but players are not moving over for our team. Only the new players on other teams are moving over, as long as they are on the game rosters.
What can we do here? How can I get the primary book working as needed?
Also, is there a way I can have both scorebooks point to the same iScore database? Right now each go to their own, but I'd rather have our secondary point to the primary database. I can do the Data Sharing, but it's cumbersome when the two scorebooks live in separate households and aren't always near each other to perform data syncs or imports/exports.
Our primary scorebook is on an Ipad 3rd Gen - which is the one we are having the problem noted above. It has been updated to the most current version of iScore (v5.011).
Our backup scorebook is on an Ipad Mini - which is working as expected, meaning it is not shutting down when adding a new player.
I tried to use Data Share to build the players on the Ipad mini and transfer to the primary scorebook - but players are not moving over for our team. Only the new players on other teams are moving over, as long as they are on the game rosters.
What can we do here? How can I get the primary book working as needed?
Also, is there a way I can have both scorebooks point to the same iScore database? Right now each go to their own, but I'd rather have our secondary point to the primary database. I can do the Data Sharing, but it's cumbersome when the two scorebooks live in separate households and aren't always near each other to perform data syncs or imports/exports.