I have a plist in my Resources folder that I use to store conversion information. I would like to give the user the option to “disable” certain units so that these units are never used in conversions. I don’t want to maintain two conversion information lists.
I can save the data back to this plist file in the stimulator. (using writeToFile and pathForResource). I am wondering if this is a problematic approach.
- Will there be problems with this during deployment? (that is, whether the apple will seal the layer).
- What happens if I push an update? What if this update contains new blocks added to the list?
- Will it do something like copying plist to the user's document directory?
Thanks.
source
share