1
任何想法爲什麼會發生這種崩潰?調試版本的作品,但試圖用戶得到簽署時Dexguard釋放崩潰(在使用signInWithCustomToken
簽署)與Dexguard的Firebase崩潰
更新:繼proguard的設定固定問題
-keep類com.google。 android.gms.internal。** {*; }
火力地堡版本:9.4.0
Caused by java.lang.IllegalArgumentException: field o.ս.ʽ has type android.support.v4.util.ArrayMap, got o.dj
at java.lang.reflect.Field.set(Field.java)
at com.google.android.gms.internal.zzaog$1.zza(Unknown Source)
at com.google.android.gms.internal.zzaog$zza.zzb(Unknown Source)
at com.google.android.gms.internal.zzamp.zza(Unknown Source:46000)
at com.google.android.gms.internal.zzafy.zze(Unknown Source:8000)
at com.google.firebase.auth.FirebaseAuth.(Unknown Source)
at com.google.firebase.auth.FirebaseAuth.(Unknown Source)
at com.google.android.gms.internal.zzaft.(Unknown Source)
at com.google.firebase.auth.FirebaseAuth.getCurrentUser(Unknown Source:19000)
Proguard的配置:
# Firebase
-keepattributes Signature
-keepattributes *Annotation*
-keep class com.google.firebase.** { *; }
-keep class org.apache.** { *; }
-keepnames class com.fasterxml.jackson.** { *; }
-keepnames class javax.servlet.** { *; }
-keepnames class org.ietf.jgss.** { *; }
-dontwarn org.apache.**
-dontwarn org.w3c.dom.**
-keepresources string/default_web_client_id
-keepresources string/firebase_database_url
-keepresources string/gcm_defaultSenderId
-keepresources string/google_api_key
-keepresources string/google_app_id
-keepresources string/google_crash_reporting_api_key
-keepresources string/google_storage_bucket
# Supoort
-dontwarn android.support.**
-keep class android.support.v4.** { *; }
-keep interface android.support.v4.** { *; }
-keep class android.support.v7.** { *; }
-keep interface android.support.v7.** { *; }
-keep class android.support.design.** { *; }
-keep interface android.support.design.** { *; }
看起來像android.support類正在改名。嘗試添加-keep類android。* * {*; } –
對不起,更新了支持相關proguard規則的帖子,這些規則已經存在。 –
btw。你可以回答你自己的問題。 –