Ans :
There are 5 application states :
iOS Application Lifecycle :
When an iOS app is launched the first thing called is
Initialise :
application: willFinishLaunchingWithOptions:-> Bool.
This method is intended for initial application setup. Storyboards have already been loaded at this point but state restoration hasn’t occurred yet.
Launch :
application: didFinishLaunchingWithOptions: -> Bool is called next. This callback method is called when the application has finished launching and restored state and can do final initialisation such as creating UI.
applicationWillEnterForeground: is called after application: didFinishLaunchingWithOptions: or if your app becomes active again after receiving a phone call or other system interruption.
applicationDidBecomeActive: is called after applicationWillEnterForeground: to finish up the transition to the foreground.
Termination :
applicationWillResignActive: is called when the app is about to become inactive (for example, when the phone receives a call or the user hits the Home button).
applicationDidEnterBackground: is called when your app enters a background state after becoming inactive. You have approximately five seconds to run any tasks you need to back things up in case the app gets terminated later or right after that.
applicationWillTerminate: is called when your app is about to be purged from memory. Call any final cleanups here.
Both application: willFinishLaunchingWithOptions: and application: didFinishLaunchingWithOptions: can potentially be launched with options identifying that the app was called to handle a push notification or url or something else. You need to return true if your app can handle the given activity or url.
Above all methods are defined in UIApplicationDelegate and AppDelegate.swift has to implement these methods.
If you have any comment, question, or recommendation, feel free to post them in the comment section below!
There are 5 application states :
- Not Running
- Inactive
- Active
- Background
- Suspended.
 |
| Application States |
iOS Application Lifecycle :
When an iOS app is launched the first thing called is
Initialise :
application: willFinishLaunchingWithOptions:-> Bool.
This method is intended for initial application setup. Storyboards have already been loaded at this point but state restoration hasn’t occurred yet.
Launch :
application: didFinishLaunchingWithOptions: -> Bool is called next. This callback method is called when the application has finished launching and restored state and can do final initialisation such as creating UI.
applicationWillEnterForeground: is called after application: didFinishLaunchingWithOptions: or if your app becomes active again after receiving a phone call or other system interruption.
applicationDidBecomeActive: is called after applicationWillEnterForeground: to finish up the transition to the foreground.
Termination :
applicationWillResignActive: is called when the app is about to become inactive (for example, when the phone receives a call or the user hits the Home button).
applicationDidEnterBackground: is called when your app enters a background state after becoming inactive. You have approximately five seconds to run any tasks you need to back things up in case the app gets terminated later or right after that.
applicationWillTerminate: is called when your app is about to be purged from memory. Call any final cleanups here.
Both application: willFinishLaunchingWithOptions: and application: didFinishLaunchingWithOptions: can potentially be launched with options identifying that the app was called to handle a push notification or url or something else. You need to return true if your app can handle the given activity or url.
Above all methods are defined in UIApplicationDelegate and AppDelegate.swift has to implement these methods.
If you have any comment, question, or recommendation, feel free to post them in the comment section below!
Please add the scan delegate life cycle for ios 13 which is added now.
ReplyDelete