Good. Because the issue I'm now having from having to create and sign with a new Keystore is when updating the app on the Google Play Store I'm getting the following error:
You uploaded an APK that is signed with a different certificate to your previous APKs. You must use the same certificate. Your existing APKs are signed with the certificate(s) with fingerprint(s):
[ SHA1: ORIGINAL FINGERPRINT HERE ]
and the certificate(s) used to sign the APK you uploaded have fingerprint(s):
[ SHA1: NEW FINGERPRINT HERE ]
So once this new update to revert to the original system is live I'll be able to use my original keystores for updating my existing apps.
Until the update is live though, we're all screwed.