Skip to main content

is it a good practice to delete the AdBannerView on viewWillDisappear and add it back on viewWillAppear?



I am currently doing the following in my code avoid the issue of "obscured" ad. But is it a good practice? One potential problem is that - assume before the viewWillDisappear, there was an ad request send out, and then when the ad come back the adBannerView instance has gone. Would that be a big problem? Should I only do hideAdBanner instead?







- (void)viewWillAppear:(BOOL)animated {

[super viewWillAppear: animated];



// create the ad banner view

[self createAdBannerView];



if (adBannerView != nil) {

UIInterfaceOrientation orientation = self.interfaceOrientation;

[self changeBannerOrientation:orientation];

}

}



- (void)viewWillDisappear:(BOOL)animated {

[super viewWillDisappear:animated];



// iAd

if (adBannerView != nil) {

[self hideAdBanner];

adBannerView.delegate = nil;

[adBannerView release];

adBannerView = nil;

}

}




Comments

  1. I use a singleton for an ad banner and call it into view on each ViewDidLoad. This automatically removes it from the previous view.

    ReplyDelete

Post a Comment

Popular posts from this blog

Slow Android emulator

I have a 2.67 GHz Celeron processor, 1.21 GB of RAM on a x86 Windows XP Professional machine. My understanding is that the Android emulator should start fairly quickly on such a machine, but for me it does not. I have followed all instructions in setting up the IDE, SDKs, JDKs and such and have had some success in staring the emulator quickly but is very particulary. How can I, if possible, fix this problem?