[Admob] Interstitials bug - font decode

Solar2D Monetization (in-app purchases, ads, etc.)
#1

Hi

I’m using latest paid Admob Plugin in my app (SDK Version 2018.3215) and I found an error in AdMob that reduces the number of views. I do not know if the problem is in Admob Plugin or in Admob itself.

In logcat on Android I’m getting this error:

02-08 13:11:37.788 10723-10754/? V/Corona: \> Class.forName: plugin.admob.LuaLoader 02-08 13:11:37.798 10723-10754/? V/Corona: \< Class.forName: plugin.admob.LuaLoader 02-08 13:11:37.798 10723-10754/? V/Corona: Loading via reflection: plugin.admob.LuaLoader 02-08 13:11:38.788 10723-10723/? I/Corona: plugin.admob: 1.2.2 (SDK: 11400000) 02-08 13:11:39.438 10723-10894/? W/Ads: The Google Mobile Ads SDK will not integrate with Firebase. Admob/Firebase integration requires the latest Firebase SDK jar, but Firebase SDK is either missing or out of date 02-08 13:12:52.788 10723-10723/? W/Ads: JS: Failed to decode downloaded font: https://fonts.gstatic.com/stats/Roboto/normal/400 (https://googleads.g.doubleclick.net/mads/gma?\_activity\_context=false&android\_num\_video\_cache\_tasks=0&caps=inlineVideo\_interactiveVideo\_mraid1\_mraid2\_sdkVideo\_th\_autoplay\_mediation\_av\_transparentBackground\_sdkAdmobApiForAds\_di\_aso\_sfv\_dinm\_dim\_nav\_navc\_dinmo\_gcache&eid=request\_pkg=plugin.admob.LuaLoader%2524Load%25241&scroll\_index=-1&seq\_num=1&target\_api=25:0) 02-08 13:12:52.788 10723-10723/? I/chromium: [INFO:CONSOLE(0)] "Failed to decode downloaded font: https://fonts.gstatic.com/stats/Roboto/normal/400", source: https://googleads.g.doubleclick.net/mads/gma?\_activity\_context=false&android\_num\_video\_cache\_tasks=0&caps=inlineVideo\_interactiveVideo\_mraid1\_mraid2\_sdkVideo\_th\_autoplay\_mediation\_av\_transparentBackground\_sdkAdmobApiForAds\_di\_aso\_sfv\_dinm\_dim\_nav\_navc\_dinmo\_gcache&eid=eid=request\_pkg=plugin.admob.LuaLoader%2524Load%25241&scroll\_index=-1&seq\_num=1&target\_api=25:0)
#2

Hi o.jacek,
 

We’re looking into it, but for now it seems like an internal SDK issue.

I’ll comment more on this here after investigation.

#3

We’ve investigated and it is an internal admob sdk warning.

You can ask their support on this, especially if you think that it reduces the number of views (I don’t so sure about that).

If you have any more questions or concerns - feel free to share them, it’s easier to solve everything together.

#4

Ok thanks for the info.

When I see this error in logcat the interstitial ad does not appear.

My statistics are for example:

  • Admob request: 1000

  • Matched request: 999

  • Match rate: 99%

  • Impression: 720

Is that normal?

#5

Almost every request was matched and showed, looks pretty normal for me, but really you should discuss it with an admob support, since it’s not exactly my field of work.

#6

No, its only shows 72% of request. So my income is 20-28% less and this is a big loss for me.

Ok I will ask them.

#7

I have updated my app from older Admob plugin (2016) to Admob V2 and I see that my “show rate” is getting lower.

Why users don’t gets ads? I paid for it 199$ and I’m getting lower income!

Another app has only 30% show rate.

Is there a way to track bugs in yours SDK? 

#8

Hi o.jacek,
 

I have updated my app from older Admob plugin (2016) to Admob V2

What do you mean by that? We don’t have any v2 version of this plugin, the updates were always incremental.
 

I see that my “show rate” is getting lower.

Why users don’t gets ads? I paid for it 199$ and I’m getting lower income!

Sorry to hear that, but Corona Admob plugin don’t have any control over Google’s Admob sdk. All issues with show or fill rate are possible to solve with the help of Admob support team. If you haven’t talked to them yet, as I’ve suggested earlier, I highly recommend to do so.
 

Is there a way to track bugs in yours SDK? 

You mean Corona Admob plugin? Of course, do you have any specific bug to be deal with? If you meant this whole rates situation then Corona team have nothing to do about it, unfortunately.

If you have any more questions or concerns - don’t be shy, feel free to share them, it’s easier to solve everything together!  B)

#9

Yes sorry, i have change from V2 to new plugin

https://coronalabs.com/blog/2017/01/26/legacy-admob-plugin-to-be-removed-march-1-2017/

is there a chance to implement addapptr in Corona by your team?

https://www.addapptr.com/monetization

#10

I’ll rase a question about addapptr integration, we always welcome new partners. Thanks for the tip!

Hope that your rates issue will be solved soon. Don’t hesitate - write a message to Admob support right now, I’m sure that they’ll help you in no time.

#11

My friend uses this product in native app and he has 90-99% fillrate.

You should integrate it as soon as possible. Its good solution becouse its connects all networks.

#12

My friend uses this product in native app and he has 90-99% fillrate.

 
That’s why I am sure that your case is unique and Admob engineers can help to quickly solve it, since they have access to all needed statistics.

#13

You should check Appodeal, https://docs.coronalabs.com/plugin/appodeal/

#14

Interesting I don’t see that error in my logs. 

As far as Addapptr just looks like a more expensive version of Appodeal. They charge 20% to 30% of all revenue you get. I think last time I checked Appodeal charges around 10% of revenue. In my case and from my calculations, I don’t think Appodeal is getting that much. I doubt anybody will have higher fillrate than Appodeal since for me in tier 3 countries it is close to 100%. 

As far as revenue, I doubt anybody will double the revenue you get from Admob. Admob pays pretty well everywhere. I can see somebody squeezing out 10% maybe 20%. I just don’t see the numbers where a random RTB and network aggregator would get more than that especially if they are charging you 20 to 30% of revenue.

#15

Hi o.jacek,
 

We’re looking into it, but for now it seems like an internal SDK issue.

I’ll comment more on this here after investigation.

#16

We’ve investigated and it is an internal admob sdk warning.

You can ask their support on this, especially if you think that it reduces the number of views (I don’t so sure about that).

If you have any more questions or concerns - feel free to share them, it’s easier to solve everything together.

#17

Ok thanks for the info.

When I see this error in logcat the interstitial ad does not appear.

My statistics are for example:

  • Admob request: 1000

  • Matched request: 999

  • Match rate: 99%

  • Impression: 720

Is that normal?

#18

Almost every request was matched and showed, looks pretty normal for me, but really you should discuss it with an admob support, since it’s not exactly my field of work.

#19

No, its only shows 72% of request. So my income is 20-28% less and this is a big loss for me.

Ok I will ask them.

#20

I have updated my app from older Admob plugin (2016) to Admob V2 and I see that my “show rate” is getting lower.

Why users don’t gets ads? I paid for it 199$ and I’m getting lower income!

Another app has only 30% show rate.

Is there a way to track bugs in yours SDK?