It happens on an Android device when trying to init both admob and kidoz… then in the log it looks like kidoz is not finishing the init process and the app freezes before moving to the next scene. When removing the admob and only using kidoz everything works fine.
In most of our monetization plugins, you must wait for the “init” event phase before calling any other API functions.
I’ll make sure this is clarified in the Kidoz documentation.
You don’t need a performWithDelay(). You should move the kidoz.load() statements to your Kidoz ad listener and call them when the “init” event triggers.
One question: How can I handle the case if there is no “init” event? Can this happen for example if there is no active internet connection? Do I then have to try to init() again after a while?
if kidoz.isLoaded ("interstitial") then kidoz.show ("interstitial") else kidoz.load ("interstitial") end
In this case it could be sometimes that a interstitial ad is loaded, but didn’t finish loading, so the load is called a second time. Will the load then start again complete new or the first load just continued?
I just encountered one more problem showing KIDOZ interstitial ads (or rewardedVideos)…
sometimes the full screen ad is not starting a video and just showing a grey screen with a little video icon in the center. Clicking on this screen brings me to the ads game download page. But when returning back to the game the grey screen stays there, no video is shown and I can not get out of this screen.
Unfortunately I have no Galaxy Tab to test with, however I’ve tested ads successfully on Nexus 7 and Nexus 9 devices without any issues. I suggest that you contact Kidoz directly and report this problem.
It happens on an Android device when trying to init both admob and kidoz… then in the log it looks like kidoz is not finishing the init process and the app freezes before moving to the next scene. When removing the admob and only using kidoz everything works fine.