致命意外:GoogleApiHandler [英] FATAL EXCEPTION: GoogleApiHandler

查看:128
本文介绍了致命意外:GoogleApiHandler的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在我的项目中,我使用的是获利服务(Vungle / AppLovin)。
当我尝试加载广告时,出现此异常

In my project i'm using the monetization service(Vungle/AppLovin). When I'm trying to load an ad, i get this exception


E / AndroidRuntime:致命例外:GoogleApiHandler
进程:kz.ikar,PID:3673
java.lang.NoSuchMethodError:没有虚拟方法setChannelId(Ljava / lang / String;)Landroid / support / v4 / app / NotificationCompat $ Builder;在类Landroid / support / v4 / app / NotificationCompat $ Builder中;或其超级类(声明为 android.support.v4.app.NotificationCompat $ Builder出现在/data/app/kz.ikar-2oCl4DY4J8w7wP-jirbYvA==/split_lib_dependencies_apk.apk)中,位于com.google。 android.gms.common.GoogleApiAvailability.zza(未知来源:225)在com.google.android.gms.common.GoogleApiAvailability.zza(未知来源:15)
在com.google.android上。 gms.common.api.internal.zzbm.zzc(未知来源:4)
,位于com.google.android.gms.common.api.internal.zzbo.onConnectionFailed(未知来源:104)
,位于com.google.android.gms.common.api.internal.zzbo.connect(未知来源:83)
at com.google.android.gms.common.api.internal.zzbo.zza(未知来源:47 )
,位于com.google.android.gms.common.api.internal.zzbm.handleMessage(未知来源:283)
在android.os.Handler.dispatchMessage(Handler.java:102)
在android.os.Looper.loop(Looper.java:164)
在android.os.HandlerThread.run(HandlerThread.java :65)

E/AndroidRuntime: FATAL EXCEPTION: GoogleApiHandler Process: kz.ikar, PID: 3673 java.lang.NoSuchMethodError: No virtual method setChannelId(Ljava/lang/String;)Landroid/support/v4/app/NotificationCompat$Builder; in class Landroid/support/v4/app/NotificationCompat$Builder; or its super classes (declaration of 'android.support.v4.app.NotificationCompat$Builder' appears in /data/app/kz.ikar-2oCl4DY4J8w7wP-jirbYvA==/split_lib_dependencies_apk.apk) at com.google.android.gms.common.GoogleApiAvailability.zza(Unknown Source:225) at com.google.android.gms.common.GoogleApiAvailability.zza(Unknown Source:15) at com.google.android.gms.common.api.internal.zzbm.zzc(Unknown Source:4) at com.google.android.gms.common.api.internal.zzbo.onConnectionFailed(Unknown Source:104) at com.google.android.gms.common.api.internal.zzbo.connect(Unknown Source:83) at com.google.android.gms.common.api.internal.zzbo.zza(Unknown Source:47) at com.google.android.gms.common.api.internal.zzbm.handleMessage(Unknown Source:283) at android.os.Handler.dispatchMessage(Handler.java:102) at android.os.Looper.loop(Looper.java:164) at android.os.HandlerThread.run(HandlerThread.java:65)

在我的项目中,我在一个活动中有两个片段。用户在第二个广告中获得一个广告。如果我从活动中加载广告,则效果很好。造成此问题的原因是什么?

In my project I have two fragments in one activity. The user gets an ad in the second one. If I load an ad from the activity, it works well. What can be the cause of this issue?

通过两个广告网络(Vungle和AppLovin)都返回此异常

By the way both ad networks(Vungle and AppLovin) return this exception

推荐答案

我遇到了同样的问题,并将其降级为Firebase Google Play服务11.6.0

I had the same problem and I fixed it downgrading to firebase Google Play services 11.6.0

这篇关于致命意外:GoogleApiHandler的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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