When the app goes to background a new NSTimer is allocated and the previous is invalidated.
However, when it comes back to foreground, a new NSTimer is allocated but the previous isn't invalidated, resulting in multiple instances of NSTimer looping and fetching data.
Easily solved adding [self.dataFetchTimer invalidate] before allocating a new instance. I'll see if I can work on this.
When the app goes to background a new NSTimer is allocated and the previous is invalidated.
However, when it comes back to foreground, a new NSTimer is allocated but the previous isn't invalidated, resulting in multiple instances of NSTimer looping and fetching data.
Easily solved adding
[self.dataFetchTimer invalidate]before allocating a new instance. I'll see if I can work on this.