inneractive ad problems with mobileAdRegister mobileAdCreate

[sincipient820]

trying to install inneractive ads without success... I followed the directions exactly....

mobileAdRegister "YOUR-AD-KEY"

local tDetails
// See the dictionary for more metadata entries
put "30" into tDetails["refresh"] // The advert refresh interval in seconds
put 25 into tDetails["age"] // The age of the target audience
put "male" into tDetails["gender"] // The expected gender of the target audience
mobileAdCreate "myAd1", "banner", (0,0), tDetails

used my own APP ID copy + pasted directly from inneractive... nothing is displayed when tested on device... have had livecode script error msg when opening stack in livecode indicating mobileAdRegister handler error... do I need to define this handler??... I was under the impression it was a standardized livecode command not requiring additional code??... working on livecode V 5.5.4 which should support inneractive... help

[sincipient820]

SOLVED.... email from RunRev today gave the solution as follows...

Adding the following to an openCard handler is one way to enable ads from within
your app-

Code: Select all

on openCard
mobileAdRegister "APP ID FROM INNERACTIVE"
  local tDetails
// See the dictionary for more metadata entries
put "30" into tDetails["refresh"] // The advert refresh interval in seconds
put 25 into tDetails["age"] // The age of the target audience
put "male" into tDetails["gender"] // The expected gender of the target audience
mobileAdCreate "myAd1", "banner", (0,0), tDetails
mobileAdSetTopVisible ("myAd1", true) //  Sets the visible of the ad "myAd1" to
true
end openCard

In the case of the Android platform, you will need to enable ad support by
selecting the appropriate "ad support" option in your Android standalone
application settings.

.... the screenshot also had "internet" and "write external storage" option in the standalone app settings clicked.... have a hunch "internet" is needed also but unsure if "write external storage" is necessary... anyway, ads are being displayed now... thanks to Neil from RunRev Support Team!