java.lang.IllegalAccessError：Method’void android.support.v4.content

概述我在我的sdk中更新了playservice,我收到了这个错误.我无法访问GCM令牌.在更新sdk之前,我的项目完美运行.我浪费了整整一天但没有找到任何解决方案.我尝试了this但是在这个依赖项中的gettting错误com.google.android.gms：play-services-plus：9.0.0这是我的logcatCausedby:java.l

我在我的sdk中更新了playservice,我收到了这个错误.我无法访问GCM令牌.在更新sdk之前,我的项目完美运行.

我浪费了整整一天但没有找到任何解决方案.我尝试了this但是在这个依赖项中的gettting错误com.Google.androID.gms：play-services-plus：9.0.0

这是我的logcat

Caused by: java.lang.IllegalAccessError: Method 'voID androID.support.v4.content.ContextCompat.<init>()' is inaccessible to class 'com.Google.androID.gms.iID.zzd' (declaration of 'com.Google.androID.gms.iID.zzd' appears in /data/data/com.hwindiapp.passenger/files/instant-run/dex/slice-com.Google.androID.gms-play-services-iID-9.0.0_b51865a18dbfbfb3651aaa54856c955adf1e354f-classes.dex)   at com.Google.androID.gms.iID.zzd.zzeC(UnkNown Source)   at com.Google.androID.gms.iID.zzd.<init>(UnkNown Source)   at com.Google.androID.gms.iID.zzd.<init>(UnkNown Source)   at com.Google.androID.gms.iID.InstanceID.zza(UnkNown Source)   at com.Google.androID.gms.iID.InstanceID.getInstance(UnkNown Source)   at com.mainProfile.classfiles.RegisterFbLoginResCallBack$registerFBUser.processGCMID_user(RegisterFbLoginResCallBack.java:166)   at com.mainProfile.classfiles.RegisterFbLoginResCallBack$registerFBUser.doInBackground(RegisterFbLoginResCallBack.java:219)   at com.mainProfile.classfiles.RegisterFbLoginResCallBack$registerFBUser.doInBackground(RegisterFbLoginResCallBack.java:153)   at androID.os.AsyncTask.call(AsyncTask.java:292)   at java.util.concurrent.FutureTask.run(FutureTask.java:237)   at androID.os.AsyncTask$SerialExecutor.run(AsyncTask.java:231)    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)    at java.lang.Thread.run(Thread.java:818) 12-01 12:23:59.553 18157-18703/com.hwindiapp.passenger E/ACRA: Not adding buildConfig to log. Class Not found : com.Volleylibfiles.BuildConfig. Please configure 'buildConfigClass' in your ACRA config12-01 12:24:00.013 18157-19059/com.hwindiapp.passenger E/AndroIDRuntime: FATAL EXCEPTION: AsyncTask #4 Process: com.hwindiapp.passenger, PID: 18157 java.lang.RuntimeException: An error occured while executing doInBackground()     at androID.os.AsyncTask.done(AsyncTask.java:304)     at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:355)     at java.util.concurrent.FutureTask.setException(FutureTask.java:222)     at java.util.concurrent.FutureTask.run(FutureTask.java:242)     at androID.os.AsyncTask$SerialExecutor.run(AsyncTask.java:231)     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)     at java.lang.Thread.run(Thread.java:818)  Caused by: java.lang.IllegalAccessError: Method 'voID androID.support.v4.content.ContextCompat.<init>()' is inaccessible to class 'com.Google.androID.gms.iID.zzd' (declaration of 'com.Google.androID.gms.iID.zzd' appears in /data/data/com.hwindiapp.passenger/files/instant-run/dex/slice-com.Google.androID.gms-play-services-iID-9.0.0_b51865a18dbfbfb3651aaa54856c955adf1e354f-classes.dex)     at com.Google.androID.gms.iID.zzd.zzeC(UnkNown Source)     at com.Google.androID.gms.iID.zzd.<init>(UnkNown Source)     at com.Google.androID.gms.iID.zzd.<init>(UnkNown Source)     at com.Google.androID.gms.iID.InstanceID.zza(UnkNown Source)     at com.Google.androID.gms.iID.InstanceID.getInstance(UnkNown Source)     at com.mainProfile.classfiles.RegisterFbLoginResCallBack$registerFBUser.processGCMID_user(RegisterFbLoginResCallBack.java:166)     at com.mainProfile.classfiles.RegisterFbLoginResCallBack$registerFBUser.doInBackground(RegisterFbLoginResCallBack.java:219)     at com.mainProfile.classfiles.RegisterFbLoginResCallBack$registerFBUser.doInBackground(RegisterFbLoginResCallBack.java:153) at androID.os.AsyncTask.call(AsyncTask.java:292)

在这行代码中显示错误

 InstanceID instanceID = InstanceID.getInstance(mContext);            GCMregistrationID = instanceID.getToken(CommonUtilitIEs.SENDER_ID, GoogleCloudMessaging.INSTANCE_ID_ScopE,                    null);

这是我的傻瓜

    apply plugin: 'com.androID.application'androID {    signingConfigs {        config {            keyAlias 'hwindi'            keyPassword '123456'            storefile file('D:/Company Projects/Hwindi/Project 2/Play_KeyStore/HwindiKeyStore.jks')            storePassword '123456'        }    }    compileSdkVersion 24    buildToolsversion "24.0.3"    defaultConfig {        applicationID "com.hwindiapp.passenger"        minSdkVersion 16        targetSdkVersion 24        versionCode 12        versionname "1.12"    }    buildTypes {        release {            MinifyEnabled false            proguardfiles getDefaultProguardfile('proguard-androID.txt'), 'proguard-rules.pro'        }    }    packagingOptions {        exclude 'lib/arm64-v8a/libcardioDecider.so'        exclude 'lib/arm64-v8a/libcardioRecognizer.so'        exclude 'lib/arm64-v8a/libcardioRecognizer_tegra2.so'        exclude 'lib/arm64-v8a/libopencv_core.so'        exclude 'lib/arm64-v8a/libopencv_imgproc.so'        exclude 'lib/armeabi/libcardioDecider.so'        exclude 'lib/armeabi-v7a/libcardioDecider.so'        exclude 'lib/armeabi-v7a/libcardioRecognizer.so'        exclude 'lib/armeabi-v7a/libcardioRecognizer_tegra2.so'        exclude 'lib/armeabi-v7a/libopencv_core.so'        exclude 'lib/armeabi-v7a/libopencv_imgproc.so'        exclude 'lib/mips/libcardioDecider.so'        exclude 'lib/x86/libcardioDecider.so'        exclude 'lib/x86/libcardioRecognizer.so'        exclude 'lib/x86/libcardioRecognizer_tegra2.so'        exclude 'lib/x86/libopencv_core.so'        exclude 'lib/x86/libopencv_imgproc.so'        exclude 'lib/x86_64/libcardioDecider.so'        exclude 'lib/x86_64/libcardioRecognizer.so'        exclude 'lib/x86_64/libcardioRecognizer_tegra2.so'        exclude 'lib/x86_64/libopencv_core.so'        exclude 'lib/x86_64/libopencv_imgproc.so'    }    configurations.all {        /*resolutionStrategy {            force 'com.androID.support:design:23.4.0'            force 'com.androID.support:support-v4:23.4.0'            force 'com.androID.support:appcompat-v7:23.4.0'        }*/    }}repositorIEs {    mavenCentral()    maven { url "https://jitpack.io" }}dependencIEs {    compile filetree(include: ['*.jar'], dir: 'libs')    testCompile ('com.squareup:fest-androID:1.0.8') {        exclude module: 'support-v4'    }    compile 'com.androID.support:appcompat-v7:24.2.0'    compile 'com.androID.support:design:24.2.0'    compile 'com.androID.support:cardvIEw-v7:24.2.0'    compile 'com.androID.support:recyclervIEw-v7:24.2.0'    compile 'com.Google.androID.gms:play-services-gcm:9.0.0'    compile 'com.Google.androID.gms:play-services-location:9.0.0'    compile 'com.Google.androID.gms:play-services-maps:9.0.0'    compile 'com.Google.androID.gms:play-services-plus:9.0.0'    compile 'com.facebook.androID:facebook-android-sdk:[4,5)'    compile 'com.paypal.sdk:paypal-android-sdk:2.13.3'    compile 'com.wdullaer:materialdatetimepicker:2.2.0'    compile 'com.mukesh:permissions:1.0.3'}

解决方法:

请检查您的declared dependencies.如给定的documentation中所讨论的,app / module的build.gradle文件中有三种不同类型的直接依赖项.

示例依赖关系如下：

androID {...}...dependencIEs {    // The 'compile' configuration tells Gradle to add the dependency to the    // compilation classpath and include it in the final package.    // Dependency on the "mylibrary" module from this project    compile project(":mylibrary")    // Remote binary dependency    compile 'com.androID.support:appcompat-v7:25.0.1'    // Local binary dependency    compile filetree(dir: 'libs', include: ['*.jar'])}

此外,正如@Diego Giorgini在相关的SO post中所回答的,

The issue you are experIEncing is due to an incompatibility between
play-services / firebase sdk v9.0.0 and com.androID.support:appcompat-v7 >= 24 (the version released with androID-N sdk)

有了这个,您可能想尝试建议的修复：

You should be able to fix it by targeting an earlIEr version of the support library. like:

compile 'com.androID.support:appcompat-v7:23.4.0'

您可能还想查看以下SO帖子中的其他建议：

> IncompatibleClassChangeError after updating to Android Build Tools 25.1.6 GCM / FCM
> Android Google Cloud Messaging (GCM) token generation crash after Firebase-related Google Play Services update.

总结

以上是内存溢出为你收集整理的java.lang.IllegalAccessError：Method’void android.support.v4.content全部内容，希望文章能够帮你解决java.lang.IllegalAccessError：Method’void android.support.v4.content所遇到的程序开发问题。

如果觉得内存溢出网站内容还不错，欢迎将内存溢出网站推荐给程序员好友。