I know that when you background an app, the timer stops running. However, what is the behavior when you come back from the background? Does the timer maintain its original <
You observed correctly how an NSTimer behaves.
If you create a timer right now that should fire every ten minutes, it will try to fire ten minutes, 20 minutes, 30 minutes and so on from now. If the app goes to sleep after one minute and wakes up after 12 minutes, the timer will fire immediately, and then again at 20 minutes (not ten minutes after the timer firing, but 20 minutes after the original time).
But if the timer misses one event completely and then is late for the next timer event as well, say if you wake up after 29 minutes, then the 10 minute event is dropped, the 20 minute event is fired as soon as possible (after 29 minutes), and the 30 minute event is fired after 30 minutes.
You can't use timers for this problem. Here is what I discovered after investigating a similar problem:
What you can do to overcome this problem and add this functionality properly you would have to implement the timers on your backend server. Hit a service when the timer starts and start the timer when the app is in foreground. The timer will take care of itself but when app is terminated or in the background the server will come into play. Hit a service to get how much time has elapsed or send a push notification when the 10 minutes have passed.