-
Notifications
You must be signed in to change notification settings - Fork 216
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
1.3.1 -> 1.3.2 java.lang.IllegalAccessError: class com.android.resources.ResourceType tried to access method 'java.util.stream.Collector #1231
Comments
Can you please try this? // TODO Remove when https://github.com/google/guava/issues/6567 is fixed.
// See also: https://github.com/google/guava/issues/6801.
dependencies.constraints {
testImplementation("com.google.guava:guava") {
attributes {
attribute(
TargetJvmEnvironment.TARGET_JVM_ENVIRONMENT_ATTRIBUTE,
objects.named(TargetJvmEnvironment, TargetJvmEnvironment.STANDARD_JVM)
)
}
because("Paparazzi's layoutlib and sdk-common depend on Guava's -jre published variant." +
"See https://github.com/cashapp/paparazzi/issues/906.")
}
} |
Closing as similar/duplicate of #552 and #906. There is a slight difference in that in those issues, the version of Guava did have missing method support between -jre and -android artifacts. Since then, in the latest Guava, those methods have been copied over, but with Until then, I've added the following workaround/snippet to the change log and 1.3.2 release notes:
Related issues:
|
@jrodbx Thanks, the snippet provided worked 🎉
from to |
Description
Steps to Reproduce
After upgrading from Paparazzi 1.3.1 -> 1.3.2 our snapshots tests crash with the above stack.
Expected behavior
Tests don't crash.
Additional information:
openjdk 17.0.7 2023-04-18
OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)
OpenJDK 64-Bit Server VM (build 17.0.7+0-17.0.7b1000.6-10550314, mixed mode)
We are also using
com.google.testparameterinjector
v1.14Example Test
To confirm. 1.3.1 works fine for us, only after upgrading to 1.3.2 do we see this issue.
The text was updated successfully, but these errors were encountered: