As a web developer one thing I like about my job is that I can instantly update code whenever I need and that basic enough backup methods for our resources mostly does (site files and DBs to an Amazon S3 account). Rarely do I have a file that if I lost or if I only have a slightly older version of that I would be screwed.
Recently I was wrapping up another mobile app and started getting paranoid about losing access to my Google play keystore file. For the unaware the keystore file is a file that a developer signs his applications with to prove they are authentic. The problem is if a developer loses this file then they cannot update any of the apps already in the app store. They would have to create a new file and release any updates as new apps!
So with me getting worried about losing the file (even though I have continuous online backups of my machine) I had the bright idea of simply moving it to our Google Apps Drive folder and therefore it would be synced up to our Google Drive as a backup to the already present backups. However when I came to have to push a point update to the app I tried signing it with the keystore file only to be told after uploading to Google Play that it wasn’t validly signed!
What happened is that Google overwrote the most up to date version of the file on my machine when it was syncing it with the server. No doubt you can imagine when I figured this out that I had a very bad feeling in my stomach. I pictured having to go to clients to let them know that we can’t update their apps anymore! However I was saved as Google drive as a previous versions feature which let you go back in time and revert to older versions.
After a lot of panicking I had the correct keystore file versions again and I immediately stored it out of my Google Drive folder.
So a word of warning in case you too have a bright idea for your keystore file dear reader. Keep it out of your Google Drive (and most likely other syncing services) folder. However do make sure that it is backed up!