Update: Version 2.0.1, which fixes this bug, has now been released. If you continue to have issues, contact me at Steven[at]SermonDesign.com, and we’ll make sure you get fixed up.
Everyone, I can’t tell you how much I hate writing this, but when version 2.o launched today, it has become apparent that it contained a bug for users who are updating, in which made two alerts cycle about 20 times upon launch, and then made it appear as though the user’s data had disappeared.
NOTE: New users will not be affected by this bug.
My apologies! Please be aware, though, that your data is safe, and a fix is on the way. I’ve submitted version 2.0.1, which addresses this issue, and requested an expedited review due to this bug. I hope this will be resolved in the next day or two.
If you have any questions, or if you need an immediate workaround for a current sermon, please email me at steven[at]sermondesign.com, and I will do my best to help you out, and give you what information I can about the bug and possible workarounds for the meantime. It is easiest to do that over the phone, so if you’ll include a phone number and a good time to call you, that would be best. If you don’t have much data in the app and just want to start over, the easiest solution by far is to simply delete the app and redownload it, and it should work.
Can I just say that personally, I really hate this. I know it’s a pain and an inconvenience, and it’s totally my fault. Sorry!
For those who are interested in the technical reasons behind the bug, it all comes down to something the app needs to do to prepare for iCloud usage. The previous versions of the app stored data in an XML store. However, iCloud sync really demands that the data be stored in a different type of database file, called a SQLite store. In version 2.0, as the app loads it needs to see if a store already exists, and then check what kind of store it is. If it finds a SQL store, then it can go ahead and get to work. However, if it finds an XML store, it then should do some preparation work: archiving that data to protect it, and copying it into a new SQLite store. If you then choose to use iCloud, it then can copy that data into the iCloud store.
The bug here is that there was a line of code preventing the app from beginning that check process. That meant that it was left trying to read the XML store as if it were an SQLite store. It doesn’t like that, and thus the alerts. That’s also why, once you cycle through the alerts, you get to the point where it asks about the iCloud store or is ready to load the iCloud store, the app functions, because at that point it doesn’t really care about the old file.