viewDidAppear not firing ever again after app enters foreground

Question

I have traced a problem in my iPhone app code to the viewDidAppear method not always firing. When you start the app the event fires as expected. However if I close the app using a phone capable of multitasking and reopen in. My viewDidAppear events no longer fire.

My views are loaded from Nibs and I use viewDidUnload to clean up (release and nil all outlets). My views are nested in side and tab bar then navigation controllers. I looks like the events aren't wired up properly when the nibs reload. Any idea on what I'm doing wrong/missing and how I can fix this?

Thanks in advance.

UPDATE I do not mean the event is not fired when the app first comes into the foreground. I mean the event never fires again. Even when changing between tabs or moving though the navigation views.

Example:

- (void)viewDidAppear:(BOOL)animated {
   [super viewDidAppear:animated];
   NSLog(@"viewDidAppear called");
}

This code is placed in two views, each on different tabs. Each time I swap between tabs "viewDidAppear called" is written to the log. When I close and reopen the app and swap between tabs this no longer happens. Other button events fire normally.

Are other NSLogs still appearing? I mean, this isn't an issue of all NSLogs just failing to do anything once you've backgrounded and resumed? — occulus, Mar 24 '11 at 11:02
Are you doing anything unusual or complex with your UI setup in terms of UIViewControllers? Are you nesting things that Apple recommend not to nest, for example? — occulus, Mar 24 '11 at 11:05

score 10 · Answer 1 · edited May 23 '17 at 12:19

10

Btw, the viewDidUnload method is really badly named btw -- it's not an 'opposite' to viewDidLoad, it's only called if there was a low memory situation and the view for that controller was unloaded due to not being visible at that time.

(ORIGINAL, NOT SO RELEVANT ANSWER:)

Please see my answer to this similar question:

Why does viewWillAppear not get called when an app comes back from the background?

Basically, viewDidAppear gets called after your UIViewController's view was added to the application's UIWindow heirarchy. Backgrounding then restoring the app doesn't change your view in that respect, so viewDidAppear doesn't get called -- it's correct behaviour, and not a bug. Check out the API docs for UIViewController.

edited May 23 '17 at 12:19

Community

1
1

answered Mar 24 '11 at 10:03

occulus

16,959
6
53
76

:) it never gets called again. Even when I change between tabs, push and pop views. Once I've minimised and reopened the app this event is never fired again. – Magpie Mar 24 '11 at 10:12
1

make sure all your viewControllers are calling [super viewDidAppear] in their viewDidAppear method or the message can lost. – Kirby Todd Mar 24 '11 at 10:38

score 7 · Accepted Answer · edited Oct 31 '14 at 16:03

Found it.

While not new to programming I am new to iPhone development. On researching this problem I found it was not recommended to call the viewWillAppear and viewWillDisappear methods manually.

My viewWillDisappear methods resign any keyboards if shown, when my app enters the background it loads a splash screen ready for when the app re-enters the foreground (there is some logic I need to do to work out what the user is shown on restarting the app and I can do this under the splash screen).

As viewWillDisappear is not called when the app goes into the background to make sure no keyboards appeared over my splash screen I was calling viewWillDisapper in the applicationDidEnterBackground method. I guess this also un-registers my events.

By adding viewWillAppear to my applicationDidEnterForeground method my events started firing again. Lesson learned, I will refactor this so I don't call these events manually.

Thanks for the help.

Glad you sorted it. Your should accept your own answer - it's allowed and you're supposed to, if you find answer to your own issue. — occulus, Mar 25 '11 at 15:32
I strongly recommend this thread's solution over doing such stunts: http://stackoverflow.com/questions/15864364/viewdidappear-is-not-called-when-opening-app-from-background — Wirsing, Dec 07 '13 at 01:12

viewDidAppear not firing ever again after app enters foreground

2 Answers2

Linked