Is anyone else having trouble with applicationDidBecomeActive
incorrectly firing on deactivation of the app on the new iPhone X?
Here\'s my test ap
In fact there are three notifications fired in rapid succession when the application is deactivated in the iPhone X Simulator:
This is wrong (and you might want to file a bug report), but it is something that could happen if a user deactivates - activates – deactivates the app quickly, so the app should cope with that situation anyway.
Both notifications must be handled in a symmetric fashion (and they come properly balanced, even with that bug): Actions done on "activate" must be reversed on "deactivate".