INMOBI ADS Display problem

Hi Tetu and Tom;

I was in this thread earlier and experienced the exact same thing as tetu (see above). But my app is not “Live” yet in iTunes. It is approved and will launch next Wednesday.

So my inMobi App ID does not yet have a verified URL.

So, were you guys able to figure it out since the last post on July 4th?

It seemed like Tetu had a everything “verified” – so it should have been working for him.

Any update would be great!

Steve

Hi Steve,

i sent my appID to Tom so that he can pass it along to InMobi

It will be great if this issue is resolved. InMobi is one of the largest mobile ad networks in the world

Hi tetu;

Thanks for the update. Anxious to hear what Tom finds.

Steve

Corona doesn’t support InMobi even though according to the docs (http://docs.coronalabs.com/api/library/ads/index.html) it does…

If testMode is set to true everything works fine (test ads are served), but if it is set to false no ads are served. 

The reason is that a required parameter, mk-carrier (the user’s IP address), is not sent from the SDK to the InMobi servers.

http://developer.inmobi.com/wiki/index.php?title=Integration_Guidelines#Mandatory_Request_Parameters

I sent an e-mail to developer@coronalabs on March 19, 2013 explaining the problem, but nobody bothered even to acknowledge the issue. 

They just keep writing in the docs that InMobi is supported. 

And more people are wasting their time trying to implement something that doesn’t work…

You are correct tetu. Or at least I think you are. I know nothing of the mk-carrier parameter, but I am seeing this too:

– When testMode is true, the inMobi test ads work fine on all of my iOS devices

– When testMode is false (wanting to go live), I get an error – and no ad displays (of course).

In the console, I can see the details of the “inMobi ad request post”. But inMobi is returning nil as an error to the post/request.

I am using build 2013.1150 (2013.6.25) and, of course, the latest “ads” plug-in is being grabbed as I build for device.

Quick help on this from Corona team would be greatly appreciated. This plug-in seems truly broken at present.

If test mode is false, you need to supply a valid inMobi appId. We just tested it here with build 1137 and it’s working for us.

sbullock, i didn’t know anything about the mk-carrier param either.

i found out by contacting the InMobi support team (they had been very helpful)

i sent them the Xcode console logs and this is what Dony Kurian, InMobi Support Engineer, replied to me:

"We have analyzed the ad request being made, it can be seen that one of the mandatory parameters ‘mk-carrier’ is not being send across in the ad request. This is the reason for not receiving ads at our end.

More information on the same is available at : http://developer.inmobi.com/wiki/index.php?title=Integration_Guidelines#Mandatory_Request_Parameters"

Tom, i used a valid InMobi appId, build 1137 and the sample code that ships with Corona. no ads are served if testMode is set to false.

What is the appId that you used? 

I did a little more testing and I have one app ID that gives ads and another one that doesn’t. The one that doesn’t give ads doesn’t have an app in the App store so it doesn’t have a verified URL associated with it. I’m not sure if that’s the reason it’s not delivering ads. We are trying to get an answer from inMobi. Both tests were performed with the inMobi sample app with testMode set to false. The only change was the appID used.

The inMobi plugin uses the inMobi SDK, which we can’t debug so it’s a “black box” as to what is going on.

Tom,

the appID i’m using has an app in the App store, so it has a verified URL and has also passed InMobi’s ownership verification process. yet, it doesn’t return any ads if testMode is set to false.

@tetu, the inMobi SDK is a black box to us since we don’t have their code and we don’t know what goes on with their servers. We figure if the testMode works, the interface is working and able to communicate with inMobi servers. Beyond that I’m afraid inMobi would need to tell you what is wrong. Nothing has changed in the basic inMobi code in the Corona SDK for the past few public releases.

@tetu, can you email me your inMobi app ID so I can pass it along to inMobi? It sounds like a valid appID with a verified URL should be delivering live ads. You can send it to: tom at coronalabs.com

If anyone else also has an appID and and a app URL that has been verified by inMob and is not getting live ads, please send me your ID.

Thanks.

Tom, i e-mailed you the appID i’m using

thank you!

Hi Tetu and Tom;

I was in this thread earlier and experienced the exact same thing as tetu (see above). But my app is not “Live” yet in iTunes. It is approved and will launch next Wednesday.

So my inMobi App ID does not yet have a verified URL.

So, were you guys able to figure it out since the last post on July 4th?

It seemed like Tetu had a everything “verified” – so it should have been working for him.

Any update would be great!

Steve

Hi Steve,

i sent my appID to Tom so that he can pass it along to InMobi

It will be great if this issue is resolved. InMobi is one of the largest mobile ad networks in the world

Hi tetu;

Thanks for the update. Anxious to hear what Tom finds.

Steve