AdWhirl ignoring backfill priorities

[GoogleCodeExporter]

AdWhirl is not getting any iAds if I have iAd set to 100% and AdMob set to 0%, 
with iAd as backfill priority 1 and AdMob backfill priority 2.

If I disable AdMob completely, iAds work great.

Original issue reported on code.google.com by jholl...@gmail.com on 17 Nov 2010 at 8:43

[GoogleCodeExporter]

Try a couple of times. iAd in development mode is made to intentionally fail 
from time to time to test fallback.

Also, you want to fall back to AdMob right? So you should set AdMob priority to 
1. Make sure you get the latest AdWhirl SDK. There was a bug earlier that 
prevented AdMob from back-filling in this situation, but it has been fixed.

If none of these solves your problem, please reopen this Issue and supply more 
information: AdWhirl SDK version used, debug output, etc.

Original comment by nigelc...@google.com on 17 Nov 2010 at 5:08

• Changed state: Invalid

[GoogleCodeExporter]

I'm using the latest SDK - 2.6.1.

I've tried all of these solutions. The ONLY thing that will display iAds 
properly is to turn AdMob off. The behavior is that if an AdMob ad is ever 
displayed, it will never display another iAd.

My refresh rate is set to 60 seconds.

Original comment by jholl...@gmail.com on 17 Nov 2010 at 5:47

[GoogleCodeExporter]

How many times have you tried? Mind sharing some code?

Original comment by nigelc...@google.com on 17 Nov 2010 at 6:23

[GoogleCodeExporter]

What code would you like to see? At this point, I have admob disabled as it 
causes a dramatic revenue increase. However, seeing iAd's poor fill rate, I 
know there's plenty of room left.

I think AdWhirl may be integrating with iAd incorrectly. The way I've observed 
iAd working is that it does not follow any set loading or refresh interval - it 
may fail to get an ad when you create it, but 2 seconds later grab one. I'm 
almost completely certain that the AdWhirl SDK tries to create an ADBannerView, 
gets a failure, and moves on to the next network. 

The way I see this working is to always have one ADBannerView offscreen and 
reveal it anytime you get the ad loaded callback - even if it preempts an admob 
ad that was showing. (Or in the general case, preempt any ad that had a lower 
priority than iAd).

Original comment by jholl...@gmail.com on 18 Nov 2010 at 4:04

[GoogleCodeExporter]

Are you observing this live or in your development environment?
If this is in your development environment, mind turning on debug output and 
paste that here with AdMob turned on? Here's how to do this:

In your application delegate:

#import "AdWhirlLog.h"

...

- (void)applicationDidFinishLaunching:(UIApplication *)application {
  AWLogSetLogLevel(AWLogLevelDebug);
  ...

Original comment by nigelc...@google.com on 18 Nov 2010 at 6:17