I've just found a serious problem with iOS app version 5.1.16 and have removed it from the App Store. I have already submitted a fixed version 5.1.17, which
is waiting for Apple's review should be available for download now.
If you launch version 5.1.16 the first time, there's no problem. But when you launch this version a second time, a bug in the startup sequence will either crash a slower device, or reset some of your database data, like MIDI presets and custom layouts, on a faster device.
You can view your current app version in the Settings app under General > Usage > Storage > Manage Storage > Set List Maker. If you have a version older than 5.1.16, you can stop reading because you should have no problems. If you have version 5.1.16, I recommend not launching Set List Maker until version 5.1.17 is installed in its place.
If you have already launched version 5.1.16 twice and experienced the data loss, you have two options for restoring your data:
- If you have been backing up your device to iTunes or iCloud, you can restore your device from your backup now. Assuming you have not backed up again since the problem occurred, this will restore any lost data. Then install version 5.1.17 before launching the app again. Please note: If you are going to restore from iTunes, you must cancel an iTunes sync that starts when you connect your device to your computer. Otherwise that will make a new backup, overwriting the backup that you need to restore from.
- If you have been syncing your database with the built-in database sync function, you can install version 5.1.17, then open the app and click Help > Utilities > Reset Local Data. This will restore any lost data except layouts. You can reinstall the default layouts with the Help > Utilities > Load Default Layouts button. If you have custom layouts that you previously copied to an unaffected device, you can copy them back to affected devices. If you had custom layouts that are not saved anywhere else, you will unfortunately have to recreate them.
This problem is database specific, so if you have multiple databases on your device, it will only affect the databases that you have opened with app version 5.1.16. Any databases you have not yet opened should be unaffected and will work normally after updating to 5.1.17.
I'm deeply sorry for the inconvenience this problem has caused. I consider any loss of user data to be the worst mistake I can make as a developer and I'll do whatever I can to help you get back up and running. Hopefully you are all making backups with iTunes, iCloud and/or the database sync function and you can move past this issue quickly.