Ok, so in my AppDelegate, I initialise various stuff in didFinishLaunchingWithOptions
, however I create my views in applicationDidBecomeActive
.
My reasoning behind this was that when the app is executing stuff in the background (push notifications), the didFinishLaunching...
will be called so I don't want to create UI stuff there, if the application will not be visible.
This has worked for me, however now with quick actions, say i want to have a quick action that goes to one of my tabs. I can't do it in didFinishLaunchingWithOptions
, since the views won't be created until didBecomeActive
.
So, my questions are:
Have I misunderstood something regarding the lifecycle and timing of UI and
didFinishLaunching...
/didBecomeActive
? That is, is it good practice to do what i do, create the views to be used indidBecomeActive
and notdidFinishLaunching...
?I haven't really found any good examples regarding this. I suppose i could store away the
UIApplicationShortcutItem
indidFinishLaunching...
and then use it indidBecomeActive
. It seems a bit 'hacky', but i haven't figured out anything else.
Pointers much appreciated.