Hi All,
I recently implemented Leadbolt ads into my Yahtzee app (using Leadbolt's latest SDK & B4A wrapper) & at first thought everything was working fine, however I've noticed a couple of issues that I'm wondering if anyone else has seen.
I am using loadToCache() to cache the interstitial ads. I make a call to loadToCache() in my Activity_Create & then every time I display an ad & I receive an AdClosed() callback, I cache another ad ready for the next time I want to display it.
The first issue I'm seeing is that sometimes the ads don't display at all when I call loadAd() to display the cached ad. By running in debug mode, I can see that the AdLoaded() callback gets fired, but no ad gets displayed - it just goes straight to the AdClosed() callback.
The second issue is that when I do get an ad displayed, I get a flash of one ad on the screen & then another ad slides in over the top of it - so I effectively show 2 ads.
I can reproduce both these issues easily by writing an app that spoofs my Yahtzee app id (so it will get ads), but just has a button that calls loadAd() every time I click it - so no additional functionality that might get in the way of showing an ad.
I have reported the issue to Leadbolt support & even sent them my sample app & source, & they told me that there is no issue that they can find - but that was after they modified the code so that the loadAd() call is made in the AdCached() callback, which makes no sense to me because I don't want to load the Ad as soon as it's cached.
Has anyone else experienced issues with the Leadbolt SDK / B4A wrapper?
Thanks - Colin.
I recently implemented Leadbolt ads into my Yahtzee app (using Leadbolt's latest SDK & B4A wrapper) & at first thought everything was working fine, however I've noticed a couple of issues that I'm wondering if anyone else has seen.
I am using loadToCache() to cache the interstitial ads. I make a call to loadToCache() in my Activity_Create & then every time I display an ad & I receive an AdClosed() callback, I cache another ad ready for the next time I want to display it.
The first issue I'm seeing is that sometimes the ads don't display at all when I call loadAd() to display the cached ad. By running in debug mode, I can see that the AdLoaded() callback gets fired, but no ad gets displayed - it just goes straight to the AdClosed() callback.
The second issue is that when I do get an ad displayed, I get a flash of one ad on the screen & then another ad slides in over the top of it - so I effectively show 2 ads.
I can reproduce both these issues easily by writing an app that spoofs my Yahtzee app id (so it will get ads), but just has a button that calls loadAd() every time I click it - so no additional functionality that might get in the way of showing an ad.
I have reported the issue to Leadbolt support & even sent them my sample app & source, & they told me that there is no issue that they can find - but that was after they modified the code so that the loadAd() call is made in the AdCached() callback, which makes no sense to me because I don't want to load the Ad as soon as it's cached.
Has anyone else experienced issues with the Leadbolt SDK / B4A wrapper?
Thanks - Colin.
