![itunes remote files itunes remote files](https://insmac.org/uploads/posts/2019-10/1570532928_remote-desktop_03.jpg)
#Itunes remote files update#
You can use a timestamp variable in your config so the app can check it to see if it needs to update the local values.ĥ. If your config file is small enough (and it should be tiny! You shouldn’t trying to stuff everything into this remote file), you may be able to get away with checking your remote config every time the app comes back into the foreground or starts up. Meaning, the user could potentially have the app open for the whole day so if you change the config variables in the middle of the day and the iOS app only checks the config file once during start up, how do you “force” the user to re-fetch the config file to get your updated variables?
#Itunes remote files how to#
You’ll have to think about how to manage staleness of the config variables that the app is using.
![itunes remote files itunes remote files](https://images.wondershare.com/recoverit/article/2019/07/how-to-open-apple-pages-on-windows-12.jpg)
If it successfully fetches it, it will update the values in local storage and use the new values.Ĥ. If it can’t fetch the remote config the next time the app starts, it will use the stored values. But after it has fetched the remote config, it will store those values in local storage until the next fetch. In the past, what I’ve done is ship the app with a default configuration file so if it can’t fetch the remote config on the first launch, it has fall back values. (Or what would happen if the server hosting your config file goes down?). The app may not have an internet connection when it starts up so you’ll need to think about what happens if your iPhone app can’t fetch the config file. Those are some of the common things that may change in between app updates.ģ. Most of the time, dynamic urls and feeds, analytics suite ids or advertising campaign ids will be good to store in the remote configuration file. If there is, I’ll see if it can be omitted from the remote config.Ģ. Personally, I’ll consider all the things that the client may want to change remotely after the app has been submitted (as well as ask them), and then ask them out of that list, if there is anything that is sensitive information. Don’t store sensitive information in your config file unless the connection is secure or you’ve encrypted the info in the file.
![itunes remote files itunes remote files](https://i.etsystatic.com/18158449/r/il/127058/2325244632/il_1140xN.2325244632_a3vs.jpg)
This way you can change the variables remotely even after the app is in the App Store. It will parse the file for all of the configuration variables it needs and use those values. The basic idea is that we will keep a file on a server that we can control and have our iOS app fetch that file on the application start up. So, the best thing to do is to be proactive about it and suggest adding it to the scope in the beginning of the project! However, even though it isn’t one of those things they ask for, it WILL come up later on after the app is in the App Store and they want to change a config variable! In my experience, this isn’t something the client asks for or thinks about during requirements gathering (unless they have a technical manager on their side). Hello! In this post, I’m going to show you guys how to use a remote config file for your iPhone/iPad application.