On another but similar note, is it possible to get the URL that should be loaded into safari ( if thats the case ) so i can show it within my app?
thx
AC
Sent from my iPad
Are the http requests and responses documented anywhere to get ads and respond to clicks, I might need to roll my own.
Sent from my iPhone
Hmm it feels very hacky but I wonder if you could temporarily nil out
the window's rootViewController in viewWillAppear: for your modal
view, then set it back to the initial view controller in
viewWillDisappear: or something (you could probably temporarily save a
copy to that first root view controller somehow). I don't know if
changing the window's rootViewController like that dynamically will
have weird consequences though. I think the the ad is being presented
on a different view controller right now and is defaulting to the
window's rootViewController.
@Casey - I wonder if this issue is different from Alex's. Are you
saying that your entire app simply hangs after the ad is pressed? I
think in Alex's case, the ad just wasn't being presented but users
could carry on normal functionality in the application. Did I
interpret the issue wrong here however?
We are definitely working hard on an iOS5 compatible SDK though and
we're looking at pushing that out very soon.
Raj
@Casey
Since we have an enormous amount of experience in both issues you appear to be talking about, It would be in your best interest to FURTHER describe your app foundation.
Are you in Unity3d, Sparrow, Cocos2d, UIKit, Mobile Web of UIWebview or how are you building your app. There was horrible horrible problems with openGL prior to 4.1.1 causing screens to go black and failure for the UIWebview controller to AUTODISMISS upon click.
I can tell you right now, we are on XCODE 4.2 in Snow Leopard with IOS5 and we are running with a 100% ad fill rate with a 100% bug free, error free, crash free execution of Admob 4.1.1.
So, that leads us to believe it's operator error on client side and not server side on Admob. In order to get the fine folks of Raj, Eric and the rest of the hard working crew at Admob to help you, take the fog off of your window and give them the foundation of your app and more importantly your view controller hierarchy. This could be your root cause. They can't help you if you don't tell them how your app is built because the chances are more than high that it's your issue. If you're in a cocos2d, you could be running out of memory and not even know it. openGL is a whiney little bitch with the admob SDK if you don't have your textures packed and more importantly aren't running them with RGBA4444 with the Floydstein+Alpha algorithm.
TexturePacker will solve that problem for you and deal with what we found to be "invisible memory" problems that were short circuiting things if you are using any sort of sprites.
Regards
We are fixing the issue and we plan to push that fix into the iOS5
compatible SDK which we will release soon.
Raj
On Oct 18, 7:10 am, Alexander Cohen <naft...@me.com> wrote:
> Here's my project at it's simplest. Took me 30 seconds to put it together and i get the same behavior.
>
> admobfail.zip
> 2932KViewDownload
>
>
>
> AC
AC
I don't see very many clean workarounds that you can do to get around
this. I talked about the temporarily nil'ing out of you
window.rootViewController as one option or trying to change it so you
put your view controller into a navigation controller and push the
view controller from there instead of presenting it modally. Both
those feel very hacky to me though and I don't think I'd recommend
them.
Raj