iAds

Hi Naomi,

Hard to say what is causing the freezing. The listener part not getting events is for sure something in your code. I just tried this:

local ads = require( "ads" )  
  
local function adListener(event)  
 print("event.response = " .. tostring(event.response))  
 print("event.provider = " .. tostring(event.provider))  
 print("event.isError = " .. tostring(event.isError))  
end  
  
ads.init( "iads", "com.test.test", adListener )  
ads.init( "inneractive", "com.test.test", adListener )  
ads:setCurrentProvider("inneractive")  
ads.show( "banner", { x=0, y=0, interval=60 } )  
  
local function switchAds()  
 ads.hide()  
 ads:setCurrentProvider("iads")  
 ads.show( "banner", { x=0, y=0 } )  
end  
  
timer.performWithDelay( 5000, switchAds )  

as a small testbed, and it works perfectly.

As for the freezing part, i just moved from a screen to another while displaying a fullscreen inneractive ad, and that works. I am thinking maybe deallocating some variables that you should not. I would need to know exactly what you’re doing (like i change from main to level1 while maintaining the adview on the screen) and what are you using (storyboard, director, custom code) at least to know where to start thinking at.

Alex. [import]uid: 196533 topic_id: 34226 reply_id: 144994[/import]

Thank you, Alex. I use storyboard, and I don’t change scene before or after the ad is shown. When the showAds.show is called, most of the display objects on the scene is made invisible, and what nextScreen function does is to make them all back to be visible.

Do you think it might be more effective if I create a test case project and file it as a bug?

Naomi [import]uid: 67217 topic_id: 34226 reply_id: 144996[/import]

Hi Naomi,

That would be amazing, and please paste back the bug number here so i can have a look.

Thanks a lot :slight_smile:

What about the listener not receiving events? Did you sort that out?

Alex. [import]uid: 196533 topic_id: 34226 reply_id: 144998[/import]

Hi Alex, I just filed Case 21361.

The listener-not-receiving-events when “inneractive” is used as the adnetwork is the bug. I can use iads and revmob together without a problem, but when I use iads and inneractive together, the listener isn’t getting any response when it’s on iPod device.

Thanks for looking into this.

Naomi [import]uid: 67217 topic_id: 34226 reply_id: 144999[/import]

@alexf can you tell us what all of the event types are in the adListener(event)

 

Thanks

 

Larry

Hi Alex, I saw a post by heftyApps that mentions the same issue (but described differently) along with another crash issue here:

http://developer.coronalabs.com/forum/2013/03/06/inneractive-major-crash-issue-please-help

Naomi [import]uid: 67217 topic_id: 34226 reply_id: 145208[/import]

@doubleslashdesign:

 

As event variables you get the event.isError variable which gets set to true or false, indicating if there was an error in the request, and event.response that contains the response returned by iAds.

 

We are in the process of refactoring this to return event phases (which i think correspond to the types you are asking about) depending on each phase the iAds view lifecycle goes through.

 

@Naomi:

 

We are in the process of fixing the issues with inneractive listener and some subsequent ones reported on the forums. Sorry that it took so long, but our agenda was pretty full.

More news soon.

 

Alex

@alexf, that sounds great.  In case you are not aware, inneractive does not display close button when it’s fullscreen ad on landscape.

 

Naomi

I tried to implement the switch between the 3 ad providers Corona supports (this is for iOS):

 

iAd -> error -> InMobi -> error --> Inneractive -> error -> iAd —> error -> InMobi etc.

 

It stuck on Inneractive.

 

It shows the ad, never refreshes and never triggers the listener …

 

I am very experienced with implementing ads (tried almost every major ad provider out there using native SDKs for Android) and although I really like Corona, I must say the ad implementation is “pain in the ass”. There is alwas something not working properly.

 

Hope this will change in the future, because to survive, indy developers really need good monetization options.

 

Regards,

Damir.

@ubj3d.android

 

AMEN!!

 

I can not believe how bad they all are. It really surprises me.

 

Larry

@alexf can you tell us what all of the event types are in the adListener(event)

 

Thanks

 

Larry

@doubleslashdesign:

 

As event variables you get the event.isError variable which gets set to true or false, indicating if there was an error in the request, and event.response that contains the response returned by iAds.

 

We are in the process of refactoring this to return event phases (which i think correspond to the types you are asking about) depending on each phase the iAds view lifecycle goes through.

 

@Naomi:

 

We are in the process of fixing the issues with inneractive listener and some subsequent ones reported on the forums. Sorry that it took so long, but our agenda was pretty full.

More news soon.

 

Alex

@alexf, that sounds great.  In case you are not aware, inneractive does not display close button when it’s fullscreen ad on landscape.

 

Naomi

I tried to implement the switch between the 3 ad providers Corona supports (this is for iOS):

 

iAd -> error -> InMobi -> error --> Inneractive -> error -> iAd —> error -> InMobi etc.

 

It stuck on Inneractive.

 

It shows the ad, never refreshes and never triggers the listener …

 

I am very experienced with implementing ads (tried almost every major ad provider out there using native SDKs for Android) and although I really like Corona, I must say the ad implementation is “pain in the ass”. There is alwas something not working properly.

 

Hope this will change in the future, because to survive, indy developers really need good monetization options.

 

Regards,

Damir.

@ubj3d.android

 

AMEN!!

 

I can not believe how bad they all are. It really surprises me.

 

Larry