We recently put some updates live without testing the builds when upgrading – as a result, because the upgrade uses a different database structure, users will be left with a black screen instead of a menu. This should only affect people upgrading and not new purchases.

A silly thing to do on our part and apologies for the inconvenience. It can be fixed though.

Follow these simple instructions to fix the problem:

1. Sync the device to iTunes and make sure the app is saved to the computer.

2. Remove the app from the device. Once it is removed, re-sync with iTunes and add the application to the device again through the app menu on the device screen in iTunes (hit the apply button after selecting the app from the menu on the left in the device view > apps)

3. Previously we had asked users to re-start the app and click on restore purchases again (from the purchases menu under settings) UPDATE: we never got around to testing the restore purchases button because we presumed that it worked. This is the first update and we’ve found out the hard way that the  and so the restore version button doesn’t work.

What to do after re-adding the device

If you go to the purchases menu, instead of clicking the restore purchases button, just buy the in-app purchases that you purchased previously. iTunes will (or should) remember what you have purchased previously and you shouldn’t be charged again. This works the same way as the restore purchases button but you have to remember what you purchased….

After purchasing something you have already paid for previously you should see this message:

The restore purchases button is broken, so just re-purchase your previous in-app purchases

Once again. Apologies to all of our customers for the inconvenience! We’ll make sure this doesn’t happen again…

What to do if this doesn’t work

1. You could try reverting to an older version of the application. There’s an excellent tutorial on how to do this here.

2. Contact iTunes Support – we are unable to directly issue a refund. This seems to be a problem with the restore purchase function in the SDK. We’ve tried our hardest and there’s nothing we can do to fix it at present.