It's very likely related to internal timers at the OS. The OS will create a different object for the activation flow, and the 'old' object's callback won't be called. This is more of a guess, but I had a similar problem with such a behavior in another component.