Open phunkyfish opened 5 years ago
Even if you have container on the disk, in some cases, replacing it doesn't help. I got affected by this yesterday : had kodi running, updated to newer build and I lost settings. Replaced container and it didn't helped. So I deployed a earlier version of kodi (with the same app id of course) and data was back after the operation.
You will most likely find this was due to the nsuserdefaults commit. I would guess you hadnt run a build with that implemented until now.
Effectively, all xml settings are now saved in nsuserdefaults, and this information survives the tvos "wipes" that occur. On a first run, this information has to be put into nsuserdafults, therefore it puts in stock settings from a base install. This does not support a container import.
understood. Is there a way to detect old data on 1st run and migrate it ? The kodi instance was running master-darwin-atv branch from October 4th.
is there any change on the matter? at the moment what is the best practice to preserve settings in case we need to update kodi, eventually even with a different id?
With a different ID, I think the only way is to download/restore the container. But if you update Kodi with the same ID, your settings are preserved.
https://kodi.wiki/view/Add-on:Backup . Works. The setup of Google Drive / Dropbox is a little complicated, but works nicely .
Due to space limitations on tvOS the current way to update is to download the container, update kodi and then upload it again. A guide on how to do this, or even better, an automated process would be great.