-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Xtend + Android support library = error: cannot access DrawerLayoutImpl #32
Comments
Does this happen in a pure Java Android project? |
No it does not. |
Thanks for the example project, I'll look into it. |
Thank you! FYI:
|
Some more info: if you delete the
|
I think I know the reason for this. I'm on vacation for this week, but will get back to you when I return. |
Hey Toby, sorry for coming back so late, we are pretty busy with polishing 2.9 =) This issue no longer happens in version 0.4.8 of the plugin. Your example uses 0.4.7 |
I tried using 0.4.8 and it still happens |
It is harder to reproduce than I thought. It works when I run "clean build", but not when I run "clean" and then "build". I could solve the issue by pushing the classpath configuration even further down the lifecycle. Will be out as 0.4.9 soon. |
Thanks for the fix! It seems to work on that particular project now, using v0.4.9, but strangly, it still happens if you build this project from scratch: http://github.com/tobykurien/XtendApp (i.e. delete Error:
|
This error happens the first time you build a project that uses the Android support library. To reproduce, try cloning WebApps (https://github.com/tobykurien/webapps) and building by running
gradle assembleRelease
:The error only happens the first time (i.e. no
build
directory), thereafter it compiles fine. Unfortunately, this means that Travis CI builds fail. Happens with Gradle 2.2.1 and even Gradle 2.5.One way to make this build pass the first time is to extract the JAR file containing the class (i.e.
build/intermediates/exploded-aar/com.android.support/support-v4/22.2.1/jars/libs/internal_impl-22.2.1.jar
and copy it into a libs folder and include that in the gradle dependencies. This is not ideal (and means my app isn't accepted by FDroid).Also seems to affect Kotlin (https://devnet.jetbrains.com/message/5538844) and Groovy (groovy/groovy-android-gradle-plugin#31) and Maven (simpligility/android-maven-plugin#621) though there seem to be different work-arounds there.
Could you please look into why this might be happening? Any workarounds without including a binary jar file?
The text was updated successfully, but these errors were encountered: