LoadAdError(code: 3, domain: com.google.android.gms.ads, message: No ad config... 当尝试在发布模式下加载 BannerAd 时 [英] LoadAdError(code: 3, domain: com.google.android.gms.ads, message: No ad config... when trying to load BannerAd in release mode

查看:16
本文介绍了LoadAdError(code: 3, domain: com.google.android.gms.ads, message: No ad config... 当尝试在发布模式下加载 BannerAd 时的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个带有广告的应用,当我使用测试广告单元在调试模式下运行我的应用时,一切正常.但是,当我使用来自 AdMob 的真实广告单元以发布模式运行应用时,出现错误

I have an app with the ads, when I run my app in debug mode with the test ad unit, everything works fine. However, when I run the app in release mode with the real ad unit from AdMob, I have an error

LoadAdError(code: 3, domain: com.google.android.gms.ads, message: No ad config., responseInfo: ResponseInfo(responseId: null, mediationAdapterClassName: , adapterResponses: []))

这个问题已经快两个月了,请帮我解决.

I'm having this for almost two months, please help me resolve it.

这里是我在 GitHub 上遇到的问题的链接打开,查看更详细的说明.

Here is a link for a GitHub issue I've opened, refer to it for a more detailed explanation.

推荐答案

我已经找到了问题的原因和解决方案.该应用程序未签名的事实是LoadAdError(code: 3, domain: com.google.android.gms.ads, message: No ad config., responseInfo: ResponseInfo(responseId: null, mediationAdapterClassName: , adapterResponses: []))

I've found the cause of the problem and the solution. The fact that the app was not signed was the cause of LoadAdError(code: 3, domain: com.google.android.gms.ads, message: No ad config., responseInfo: ResponseInfo(responseId: null, mediationAdapterClassName: , adapterResponses: []))

签署应用程序解决了我的问题.

Signing the app have solved my issue.

这篇关于LoadAdError(code: 3, domain: com.google.android.gms.ads, message: No ad config... 当尝试在发布模式下加载 BannerAd 时的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆