Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Unintended behavior
View staffing
Description
Version used: 2.2.1
What steps will reproduce the problem?
1. Add Espresso dependency
2. Enable ProGuard on tested variant
3. Observe build failure when ProGuard runs over test APK classes.
ProGuard logs these messages:
Warning: android.support.test.espresso.core.deps.guava.cache.Striped64: can't find referenced class sun.misc.Unsafe
Warning: android.support.test.espresso.core.deps.guava.cache.Striped64$1: can't find referenced class sun.misc.Unsafe
Warning: android.support.test.espresso.core.deps.guava.cache.Striped64$Cell: can't find referenced class sun.misc.Unsafe
Warning: android.support.test.espresso.core.deps.guava.primitives.UnsignedBytes$LexicographicalComparatorHolder$UnsafeComparator: can't find referenced class sun.misc.Unsafe
Warning: android.support.test.espresso.core.deps.guava.primitives.UnsignedBytes$LexicographicalComparatorHolder$UnsafeComparator$1: can't find referenced class sun.misc.Unsafe
Since Espresso isn't using these classes, it should ship consumer ProGuard rules which automatically suppress these warnings. This will enable consumers to not be required to modify their own ProGuard rules when consuming this dependency.
The contents of the consumer rule file would simply be:
-dontwarn android.support.test.espresso.core.deps.guava.**