Testing update before releasing it: how?
Here is what I want to do:
Save player data to a table, then create an update to the app that adds rows to that table between existing rows.
Here are my questions:
1. Can I use behaviors to add rows to a player's save data table in an update without overwriting the data already existing in the table?
3. Most importantly, how can I test an update before releasing it, to make sure it works properly?
Here is why I am asking:
I searched for an answer but all keyword searches result in links to pages about updates to GS itself, none of which are about how to do updates for apps made with GS.
Thank you in advance to anyone who can help me with this question!
Best Answer
-
vlaso Posts: 19
@Tryangle said:
Here is what I want to do:
Save player data to a table, then create an update to the app that adds rows to that table between existing rows.Here are my questions:
1. Can I use behaviors to add rows to a player's save data table in an update without overwriting the data already existing in the table?
3. Most importantly, how can I test an update before releasing it, to make sure it works properly?Here is why I am asking:
I searched for an answer but all keyword searches result in links to pages about updates to GS itself, none of which are about how to do updates for apps made with GS.Thank you in advance to anyone who can help me with this question!
The two ways I know of are:
1. You can test your app with the iOS viewer, which is probably one of the easiest. Here is a video how:
2. Submit the build to iTunes Connect, and run it through the new TestFlight.
Answers
For anyone who finds themselves on this thread looking for the same answer, what I found was that the iOS viewer retains save data when updating a build, if and only if the build being updated is updated with a build using the exact same name. So it is completely possible to test an update with new features onto a preexisting build, using the iOS viewer.
I cannot confirm, but it would seem that TestFlight works similarly.