I've already got an unsigned beta demo version of my game for 3rd
edition devices out using an unprotected UID. I'm now going to submit
the version for signing, for which I have to switch to a protected
UID.
This seems like it's going to create an awkward situation where
existing users of the beta demo will effectively be installing a new
app, not replacing the beta when they switch to the signed version.
To make it worse, the install will fail if I keep my file names the
same as they can't be overridden while the previous version is still
installed.
So it seems I'll have to rename everything (which is suggested anyway
to stop clashes) and then leave the user with two versions of the game
on their phone, unless they install the old one manually.
One worry is if they've moved the demo icon into the main menu or
elsewhere, they won't notice the new version installed in the depths
"my own" or "installations" or wherever it ends up and will keep using
the old one oblivious to the fact there's a new version elsewhere.
To avoid this I could not rename files, then they'll have to uninstall
the old one, but this seems a pain, with the cryptic error messages
generated by the install system a lot of users won't figure this out,
and I'd like to avoid having to put out release notes with the sis
file.
Any better suggestions?
Or ideas for the future for how to release an unsigned pre-release
version and not have this sort of clash occuring.
http://www.GreatApe.com
http://www.Oval-Racer.com