增加新的谷歌登录到Android应用程序后Proguard的混淆问题 [英] Proguard obfuscation issues after adding new Google Sign In to Android application

查看:1250
本文介绍了增加新的谷歌登录到Android应用程序后Proguard的混淆问题的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在新的谷歌Play服务库(8.3.0)有进行登录的新途径。该方法包括添加以下的依赖:

的build.gradle(应用级):
类路径'com.google.gms:谷歌服务:1.4.0-β3

和应用上的水平:

 编译com.google.android.gms:发挥服务-auth的:8.3.0`应用插件:'com.google.gms.google-services'`

在创建具有 minifyEnabled 设置为 A发布的应用程序版本,应用程序被释放并正常工作。但是,创建一个发布版本时,
minifyEnabled 设置为真正在启动应用程序崩溃,并显示以下异常:

 了java.lang.RuntimeException:无法获取提供商com.google.android.gms.measurement.AppMeasurementContentProvider:抛出java.lang.ClassNotFoundException:找不到类com.google。 android.gms.measurement.AppMeasurementContentProvider的路径:DexPathList [zip文件/data/app/com.xxx.xxx-1/base.apk\"],nativeLibraryDirectories=[/data/app/com.xxx.xxx- 1 / lib目录/手臂/供应商/ lib中/系统/ lib目录]
12月11日至8日:47:13.497 3672-3672 /? E / AndroidRuntime:在android.app.ActivityThread.installProvider(ActivityThread.java:5156)
12月11日至8日:47:13.497 3672-3672 /? E / AndroidRuntime:在android.app.ActivityThread.installContentProviders(ActivityThread.java:4748)
12月11日至8日:47:13.497 3672-3672 /? E / AndroidRuntime:在android.app.ActivityThread.handleBindApplication(ActivityThread.java:4688)
12月11日至8日:47:13.497 3672-3672 /? E / AndroidRuntime:在android.app.ActivityThread.-wrap1(ActivityThread.java)
12月11日至8日:47:13.497 3672-3672 /? E / AndroidRuntime:在android.app.ActivityThread $ H.handleMessage(ActivityThread.java:1405)
12月11日至8日:47:13.497 3672-3672 /? E / AndroidRuntime:在android.os.Handler.dispatchMessage(Handler.java:102)
12月11日至8日:47:13.497 3672-3672 /? E / AndroidRuntime:在android.os.Looper.loop(Looper.java:148)
12月11日至8日:47:13.497 3672-3672 /? E / AndroidRuntime:在android.app.ActivityThread.main(ActivityThread.java:5417)
12月11日至8日:47:13.497 3672-3672 /? E / AndroidRuntime:在java.lang.reflect.Method.invoke(本机方法)
12月11日至8日:47:13.497 3672-3672 /? E / AndroidRuntime:在com.android.internal.os.ZygoteInit $ MethodAndArgsCaller.run(ZygoteInit.java:726)
12月11日至8日:47:13.497 3672-3672 /? E / AndroidRuntime:在com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
12月11日至8日:47:13.497 3672-3672 /? E / AndroidRuntime:抛出java.lang.ClassNotFoundException:产生的原因没有找到路径级com.google.android.gms.measurement.AppMeasurementContentProvider:DexPathList [zip文件/data/app/xxx.xxx .. 。

我曾尝试将这些设置添加到ProGuard的项目配置,但它并不能帮助(同一个异常不断出现):

  -optimizationpasses 5
-keepattributes的SourceFile,LineNumberTable,例外,签名,InnerClasses,*注释*
-keep类com.google.android.gms ** {*。 }
-dontwarn com.google.android.gms。**


解决方案

我已经提起的这个的错误报告。

In the new Google Play Services library (8.3.0) there is a new way to perform sign-in. This method involves adding the following dependencies:

build.gradle (app level): classpath 'com.google.gms:google-services:1.4.0-beta3'

And on app level:

compile 'com.google.android.gms:play-services-auth:8.3.0'

`apply plugin: 'com.google.gms.google-services'`

When creating a release app version with minifyEnabled set to false, the app is being released and works fine. However, when creating a release version with minifyEnabled set to true the app crashes on startup with the following exception:

java.lang.RuntimeException: Unable to get provider com.google.android.gms.measurement.AppMeasurementContentProvider: java.lang.ClassNotFoundException: Didn't find class "com.google.android.gms.measurement.AppMeasurementContentProvider" on path: DexPathList[[zip file "/data/app/com.xxx.xxx-1/base.apk"],nativeLibraryDirectories=[/data/app/com.xxx.xxx-1/lib/arm, /vendor/lib, /system/lib]]
11-08 12:47:13.497 3672-3672/? E/AndroidRuntime:     at android.app.ActivityThread.installProvider(ActivityThread.java:5156)
11-08 12:47:13.497 3672-3672/? E/AndroidRuntime:     at android.app.ActivityThread.installContentProviders(ActivityThread.java:4748)
11-08 12:47:13.497 3672-3672/? E/AndroidRuntime:     at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4688)
11-08 12:47:13.497 3672-3672/? E/AndroidRuntime:     at android.app.ActivityThread.-wrap1(ActivityThread.java)
11-08 12:47:13.497 3672-3672/? E/AndroidRuntime:     at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1405)
11-08 12:47:13.497 3672-3672/? E/AndroidRuntime:     at android.os.Handler.dispatchMessage(Handler.java:102)
11-08 12:47:13.497 3672-3672/? E/AndroidRuntime:     at android.os.Looper.loop(Looper.java:148)
11-08 12:47:13.497 3672-3672/? E/AndroidRuntime:     at android.app.ActivityThread.main(ActivityThread.java:5417)
11-08 12:47:13.497 3672-3672/? E/AndroidRuntime:     at java.lang.reflect.Method.invoke(Native Method)
11-08 12:47:13.497 3672-3672/? E/AndroidRuntime:     at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
11-08 12:47:13.497 3672-3672/? E/AndroidRuntime:     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
11-08 12:47:13.497 3672-3672/? E/AndroidRuntime:  Caused by: java.lang.ClassNotFoundException: Didn't find class "com.google.android.gms.measurement.AppMeasurementContentProvider" on path: DexPathList[[zip file "/data/app/xxx.xxx...

I have tried to add these settings to the proguard project config but it doesn't help (same exception keeps appearing):

-optimizationpasses 5
-keepattributes SourceFile,LineNumberTable,Exceptions, Signature, InnerClasses,*Annotation*
-keep class com.google.android.gms.** { *; }
-dontwarn com.google.android.gms.**

解决方案

I've already filed a bug report for this.

这篇关于增加新的谷歌登录到Android应用程序后Proguard的混淆问题的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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