Comments on: Using iAds While Maintaining Backwards Compatibility

By: Greg

Greg — Sat, 26 Feb 2011 23:35:14 +0000

'self' simply refers to the object (see here). The modern Obj-C runtime no longer needs these ivars declared as well, so this code segment could use an update. There's been debate about using 'foo = nil' in destructors. The ideal syntax has been shown to be '[foo release], foo = nil;'

By: Patty

Patty — Sat, 26 Feb 2011 05:33:11 +0000

What’s the difference between:
A> adView.delegate = nil;
B> self.adView.delegate = nil;

What’s the difference between:
C> self.adView = [[[ADBannerView alloc] init] autorelease];
C> self.adView = nil; // in dealloc

D> self.adView = [[ADBannerView alloc] init];
D> [self.adView release]; // in dealloc

By: Greg

Greg — Sat, 09 Oct 2010 18:00:13 +0000

@Alexandra: Haven’t seen that before, make sure you have imported everything you need from AdWhirl. Start over perhaps, I know AdWhirl bundles a step-by-step PDF instruction guide on using the service.

As far as limiting features, that was just my concept of how you might capitalize with an iPhone app. You’re certainly free to do what you want.

By: Alex

Alex — Thu, 07 Oct 2010 22:57:11 +0000

Hello,

I’m trying to set iAd in bounds of AdWhirl for 3.x iOS and 4.x iOS.
I’ve done all steps:
Week link + building app without AdWhirlAdapterIAd files is processed successfully
Target OS is 3.0 and Base OS is 4.0.
But when I try to add these files with additional conditions where ADBannerView appears, it couldn’t find items from iAd lib:

“_ADBannerContentSizeIdentifier320x50″, referenced from:
_ADBannerContentSizeIdentifier320x50$non_lazy_ptr in AdWhirlAdapterIAd.o
ld: symbol(s) not found”

What I can missed? What do you mean with “Limit a few “pro” features in the iOS 3 version that can be unlocked with a minimal in-app purchase.”?

Looking forward for receiving answer
Thanks
Alexandra

By: Ali

Ali — Tue, 27 Jul 2010 10:15:15 +0000

I was looking for this on the web and found your post, really well done mate!
Not just this post, the whole blog is great!
Keep up the good work!!

Cheers,
Ali

http://twitter.com/outofthebit

By: Greg

Greg — Fri, 23 Jul 2010 01:06:23 +0000

@tylerweitzman Yes, that is the expected behavior. The underlying iAd framework did not exist until iOS 4 so the ads cannot be displayed on anything < iOS 4. This post was simply a means to tell you how to use iAds while on iOS 4 but not shut out your users who haven’t upgraded and are stuck with iOS 3.

You all might also want to check out AdWhirl. I’ll probably be posting about it soon, as I’m pretty fed up with iAd’s performance.

By: Rosco

Rosco — Sat, 17 Jul 2010 09:53:16 +0000

Great article Greg.

The app store rejected my app twice for not implementing iAds correctly and it seems like you might have saved the day with your clear instructions.

Cheers.

Rosco

By: tylerweitzman

tylerweitzman — Sat, 17 Jul 2010 00:51:16 +0000

I followed the instructions and the ads do show up on an iOS4 device but when I put it on an iOS3 device it doesn’t crash but the ads don’t show up either. Is it meant to be like that? Is there any way to have the ads show up on a iOS3 device.

By: JerryBeers.com » Blog Archive » Using iAds While Maintaining Backwards Compatibility

Sun, 11 Jul 2010 22:24:27 +0000

[...] Great post from Greg Fiumara about using iAds and still deploying to pre-iOS4 devices. Read More [...]

By: Greg

Greg — Sat, 03 Jul 2010 14:07:26 +0000

@Carol: Select the Target from the Groups and Files pane in Xcode. On the right side of the screen after selecting, it lists all the Frameworks used in your project (it will look like the screenshot I posted). Then change “Required” to “Weak” next to iAd.framework. You can also just add “-weak_framework iAd” to your linker flags. For more info, see the Apple Developer Documentation link in my post about weak linking frameworks.