There is still potentially a workaround that would enable you to resolve this.
Does your current app save any files to the documents directory on the device? If so, you could do the following. Release an update to your app. In that update, your code would check whether some file you choose exists in the documents directory. If it does, you know that the app was already previously installed on the device (at the time when it was a paid app), and therefore you should unlock the content. If the file doesn’t exist, you know the app was just downloaded and run for the first time, in which case you would keep the content locked. In both cases, you would set a more permanent flag in a dedicated file to indicate whether the content should be locked or unlocked, so that you can check it on future runs and future updates without this workaround.
- Andrew [import]uid: 109711 topic_id: 37068 reply_id: 145298[/import]