Getting http 403 forbidden response when our jw player tries to hit the google ad server

[sac...@houseofgod.co]

platform : Android

Issue: Google responds http 403 forbidden response when our jw player tries to hit the google ad server

Initial findings: apparently the issue is with 'msid' parameter in the request ( which is our package name). using any other text than our package name, it works perfectly fine.  We think our package name is blocked by google somehow.

Please note we are using JW player in our Android app and we do not have control over this 'msid' param. 

[Joshua Lagonera (Mobile Ads SDK Team)]

Hi there,

If you feel that your package name has been blocked from serving any ads, then it would be classified as an Ad Serving issue and not something specific to the Mobile Ads SDK. I would recommend you reach out to our Product Support Team for further assistance regarding your concern. Alternatively, you may use our Troubleshooter for more specific solutions.

Regards,

Joshua Lagonera

Mobile Ads SDK Team

[shi...@houseofgod.co]

Hi Joshua,

Below is the detail description of the problem that we are facing in our app which sac...@houseofgod.co has mentioned in the above post.

Subject : msid=<android_package_name> is throwing 403 error while requesting ads(ima + jw player) in Android 

In Android, while requesting the ad, there is a parameter getting added automatically. 

The parameter is msid (which is equal to package name. msid=<android_package_name>) 

In our iOS app, ads are coming & this msid parameter is 0 (we found this using Charles proxy software). For iOS, the return code is 200 & for Android, we were getting 403 forbidden error. (according to Charles tool)

So, I just rename the package name of my android app and now I think ads will be displayed. (actually now I am NOT getting the same error, the error string now is 'the VAST document is empty' which means(to the best of my knowledge) as the number of app downloads increases and when more & more people start watching the video then VAST document will not be empty as ads will be served when number of views increases).

My question is: 

1) How do I explicitly set this msid parameter = 0 in AD_URL?

I tried appending my AD_URL (like...&msid=0) but while requesting it is automatically getting override by msid=<actual_android_package_name>.

2)Why are ads not coming with my old android package name? 

The original package name is "com.tf.eros.faythTv". With this package name, the response code was 403 forbidden (according to Charles tool). When I changed this package name to something else then I am no longer getting the old Ad Error: Unable to request ads from the server due to network error. 

Is this package name is blocked on Google AdSense Server for some reason to request the ad? I don't want to change the package name of our app as it means that while uploading/updating the app on PlayStore it will be a different app with same 'app-name' (every android app has a package name which is unique across PlayStore even if 2 or more apps have the same app-name). 

Thanks

Shikhar Deep

Android Developer

[Joshua Lagonera (Mobile Ads SDK Team)]

Hi Shikhar,

This does not look like something from the Mobile Ads SDK. Upon further investigation from your concerns and your code snippets, it looks like you are using the IMA SDK. Do note that this forum is for Mobile Ads SDK concerns only. If you have concerns related to the IMA SDK, it would be better for you to reach out to the experts over at the IMA SDK Forums.

Regards,

Joshua Lagonera

Mobile Ads SDK Team