Fixed
Status Update
No update yet.
Comments
nk...@google.com
nk...@google.com
This is a terrible oversight on our part but unfortunately there is no clean way to revert this API in order to break Guava dependency.
As a result, there will be a breaking public API change in the next release to address this issue. We introduced an ugly wrapper around Guava Optional class, named EspressoOptional which will live under "android.support.test.espresso.util" namespace. Developers that were using the leaked Guava Optional API will need to change their imports and references to use EspressoOptional during the update to the new version.
Sorry for the inconvenience this may cause. We'll make sure to add a note for this in the next release announcement and change-logs.
As a result, there will be a breaking public API change in the next release to address this issue. We introduced an ugly wrapper around Guava Optional class, named EspressoOptional which will live under "android.support.test.espresso.util" namespace. Developers that were using the leaked Guava Optional API will need to change their imports and references to use EspressoOptional during the update to the new version.
Sorry for the inconvenience this may cause. We'll make sure to add a note for this in the next release announcement and change-logs.
Description
Version used: 2.2.2
What steps will reproduce the problem?
1. Add espresso-intents to a project that contains an `AndroidManifest` in the test directory with a label on the application tag
What is the expected output? What do you see instead?
The tests should run without error, however manifest merging fails due to the conflicting labels present and suggests overriding espresso-intents label.