Admob Mediation

[Rodrigo]

I need to add Admob mediation to my Android app.

I have followed instructions on this site https://developers.google.com/mobile-ads-sdk/training/mediation/custom-events/banners

For now, I need a custom event, I have created it at admob console, and added the class name with its package name.

The problem is that I cannot see the banners. In the log I get these messages:

01-17 10:00:24.673: I/Ads(7720): Starting ad request.

01-17 10:00:25.133: I/Ads(7720): Trying mediation network: 18351550913290782395

01-17 10:00:25.133: I/Ads(7720): Instantiating mediation adapter: com.google.ads.mediation.customevent.CustomEventAdapter

01-17 10:00:35.133: I/Ads(7720): Timed out waiting for adapter.

01-17 10:00:35.143: I/Ads(7720): No fill from any mediation ad networks.

01-17 10:00:35.143: I/Ads(7720): Scheduling ad refresh 30000 milliseconds from now.

01-17 10:00:35.143: W/Ads(7720): Failed to load ad: 3

I have added this same mediation network to another app and there it is working.

Any help on why this is happening would be great.

Thanks!

[Eddie Lee]

Please the people in Google fix this problem as soon as possible this has been last for hours. Google recommend us to use google play services admob, but we were punished because we listened to google's recommendation.

My other apps which use the old admob 6.4.1 doesn't have any problem.

2014/1/18 Rodrigo <roy.le...@gmail.com>

--
 
---
You received this message because you are subscribed to the Google Groups "Google AdMob Ads Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[William Ferguson]

Well it seems pretty clear that your adapter didn't receive any ad within 10 seconds at which point it timed out.

Suggest you add some logging into your CustomEvent  so you can see what it is doing. At the moment I would say that it's not returning an ad (within the 10 second timeout period).

William

[Giuseppe Iuculano]

The problem isn't the custom adapter, even with the admob adapter there is the timeout

[William Ferguson]

In that case it is your network connection.

--
 
---
You received this message because you are subscribed to a topic in the Google Groups "Google AdMob Ads Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-admob-ads-sdk/HClGVPHAnGg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-admob-ads...@googlegroups.com.

[Rodrigo Guerrero]

I found the solution. There was an update of google play services library. You need to update it and use the new version. That made this thing work again.

[Giuseppe Iuculano]

So all my users who upgraded GPS have network connecion issue....

To unsubscribe from this group and all its topics, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.

[Eddie Lee]

I am sure you are not using the GPS in the mediation, so you are easy blame it as network connection problem. Before posting a problem, WE WILL FIRST MAKE SURE THAT IT IS NOT OUR PROGRAMMING FAULT AND NETWORK FAULT. For your information, we've several apps, some of them using GPS in the mediation as suggested by google recently, and the others we are still using the old admob 6.4.1 .....All the ads in the apps with the old admob 6.4.1 just work fine,however for those with GPS, starting from yesterday, no ad received. In order to test whether this is a problem with our account, we even use the admob test account, and the same thing happen. This is definitely not the problem of our apps,not a problem of our connection network, we try to get the ad from different countries and we have old admob 6.4.1 which is working, so it is also nothing related to the fill-rate of admob. We suffer big lose because of this, not just admob ads....but all the other ad networks who use GPS as the mediation.

Some of admob user here already figure out updating the library to the latest GPS can fix the problem, but I want to make it clear that when this problem started yesterday our team try to download the latest library from google immediately however at that time no update version at that moment. A new update version is actually uploaded may be a few hours ago. It seems that google is trying to fix this problem by using a new GPS library, but we want to make it clear that this is definitely not a way to solve the problem. We've many user who is using the old library, around 40-50% they will no longer receive the ads because they just don't always update the version.

I just hope that you STOP GIVING COMMENT on an issue that you don't understand at all. Your reply just give a wrong impression to the people in google that this is not their problem. We want everything to be examined logically. The only thing we are asking here is to make sure the service of our old version apps will be back to normal asap, and since until now no GOOGLE staff reply on this issue, we are very disappointed on this..

2014/1/18 William Ferguson <william....@xandar.com.au>

--
 
---

You received this message because you are subscribed to the Google Groups "Google AdMob Ads Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads...@googlegroups.com.

[William Ferguson]

Eddie, I was commenting on an issue that Guiseepe posted in which according to the log it was clear that the CustomEvent he was using had timed out.

I have no doubt you have your own problem, but please confine your discussion of that to your thread and don't hijack Guiseppe's

William

[Giuseppe Iuculano]

William, the issue is the same, and the problem started after Google updated GPS. We know what is a timeout, but you assumed that the timeout is caused by a local network issue, and that's not the case.

[William Ferguson]

Giuseppe, based on the information that you provided it is the natural first diagnosis.

I still haven't seen any evidence to suggest that your problem is anything other.

On Sun, Jan 19, 2014 at 11:48 AM, Giuseppe Iuculano <gius...@iuculano.it> wrote:

William, the issue is the same, and the problem started after Google updated GPS. We know what is a timeout, but you assumed that the timeout is caused by a local network issue, and that's not the case.

[Giuseppe Iuculano]

The evidence is that only in this thread we are 3 people that have the same issue and the fix is to update GPS.

[Eddie Lee]

William, honestly speaking I think it is better for you to try it out before you comment on this issue. This issue is not something that cannot be duplicated. The easiest way is to copy and paste the code from admob website by using the GPS library with the old library then everybody will get the same result no matter which ad network you are using. The problem no longer exist in the latest version, but it doesn't mean that the problem is solved. We have many user using the old version with the old library build in, we cannot force our user to update to the latest version. It looks like that google is now only solving the problem by updating the latest library, but we just want to raise it out that this is definitely not enough to solve the issue. 

2014/1/19 Giuseppe Iuculano <gius...@iuculano.it>

The evidence is that only in this thread we are 3 people that have the same issue and the fix is to update GPS.

--

---

You received this message because you are subscribed to the Google Groups "Google AdMob Ads Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads...@googlegroups.com.

[William Ferguson]

Eddie/Guiseppe,

I never attempted to dig into or resolve the issue that you seem to be having with respect to GPS.

My sole post was specifically on Guiseppe's thread where he was looking for help with a time out issue with a CustomEvent.

My comments on that thread was based upon the information that Guiseppe had provided in that thread.

William

--
 
---
You received this message because you are subscribed to a topic in the Google Groups "Google AdMob Ads Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-admob-ads-sdk/HClGVPHAnGg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-admob-ads...@googlegroups.com.

[Eric Leichtenschlag]

Hey guys,

I can confirm the behavior you're seeing with respect to this timeout when doing mediation. I was able to reproduce the same behavior with the 4.0 library, and a 4.1 version of Google Play services on the device. Switching to using the 4.1 library solved the issue.

While we investigate the root cause of the issue, the workaround/solution is to update with the 4.1 library. Since we don't know the root cause yet, we don't know yet if an update can be made to the service to make the 4.0 library work.

Thanks,
Eric

On Saturday, January 18, 2014 7:04:36 PM UTC-8, William Ferguson wrote:

Eddie/Guiseppe,

I never attempted to dig into or resolve the issue that you seem to be having with respect to GPS.

My sole post was specifically on Guiseppe's thread where he was looking for help with a time out issue with a CustomEvent.

My comments on that thread was based upon the information that Guiseppe had provided in that thread.

William

On Sun, Jan 19, 2014 at 12:59 PM, Eddie Lee <eddi...@recax.com> wrote:

William, honestly speaking I think it is better for you to try it out before you comment on this issue. This issue is not something that cannot be duplicated. The easiest way is to copy and paste the code from admob website by using the GPS library with the old library then everybody will get the same result no matter which ad network you are using. The problem no longer exist in the latest version, but it doesn't mean that the problem is solved. We have many user using the old version with the old library build in, we cannot force our user to update to the latest version. It looks like that google is now only solving the problem by updating the latest library, but we just want to raise it out that this is definitely not enough to solve the issue. 

2014/1/19 Giuseppe Iuculano <gius...@iuculano.it>

The evidence is that only in this thread we are 3 people that have the same issue and the fix is to update GPS.

--

---

You received this message because you are subscribed to the Google Groups "Google AdMob Ads Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
 
---
You received this message because you are subscribed to a topic in the Google Groups "Google AdMob Ads Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-admob-ads-sdk/HClGVPHAnGg/unsubscribe.

To unsubscribe from this group and all its topics, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.