Hi
@all,
assumed ad delivery works at all (see
http://giderosmobile.com/forum/discussion/comment/38412#Comment_38412 ): Why does a RevMob#load call already display the ad? Isn't RevMob able to preload the ad? If so it would be super cool when this call wouldn't do anything or if the would be a method to check whether the provider supports the preloading mechanism =| .
Thanks and greetings
Sebastian
Comments
banner is added to the view hierarhcy when two conditions are true
1) banner is loaded
2) show method was called to set the shouldShow bool property to true.
Are you sure you are not calling ad:showAd somewhere in the code?
That would also explain the "WARNING: USING ADS WITHOUT STARTING A SESSION COULD PRODUCE UNPREDICTED BEHAVIOUR!"
in both cases, it seems that ad:showAd is called somewhere (possibly before setKey method is called)
I now cleaned up the Ads eventlistener meaning each event got it's own listener.
The code create two different ads. One for a banner (auto). And one for an interstitial. Thats why the init, enableTesting and load part appears twice.
This is the player log:
This is the Xcode output:
you need to create only one single revmob instance, it will be able to manage both banner and interstitial.
Two revmob instances is probably what messing it all up now
Can you try everything with one single revmob instance?
Thanks a lot in advance for your help !
From their docs:
To start a RevMob session just call the startSession:
http://sdk.revmobmobileadnetwork.com/ios.html
No callback no nothing
And now that you have said I also noticed that warning poping up in Log
EDIT
I also noticed that in swift you do provide a callback to setting session:
RevMobAds.startSessionWithAppID("copy your RevMob Media ID here",
withSuccessHandler: completionBlock, andFailHandler: errorBlock);
But in Objective-C no callback provided
The reason why I want to preload the ads is, that when I don't the ad is first displayed and then positioned - which results in very short flickering, meaning the ad (banner) is visible for a very short time (one frame maybe?) at the top. Positioning the banner in the received and displayed callback doesn't help =| .
Btw: What would happen to ads when the app goes to background comes back after a while? Restart of the session and same problems then? Hm ...
Yes Ads:show and Ads:load basically does the same, except first also adds the add to the rendering tree
And yes basically it seems there should be a callback but I did not find it when I was implementing it.
Going to background and back does nothing, only the cold start seems to be reseting session