Having Guava and espresso-web as androidTest dependencies does not compile [37063389]

Fixed

Bug

Status Update

No update yet.

Description

sl...@google.com

created issue #1

Sep 28, 2015 09:51PM

The espresso-web:2.2 release contains some classes from Guava. This makes it impossible to have espresso-web:2.2 and Guava as dependency for Android tests.

*What steps will reproduce the problem?*
1. Create a new Android project in AndroidStudio
2. Add espresso-web and Guava (or any other library that transitively depends on Guava) as dependencies for testing (see attached build.gradle)
3. Build the connectedAndroidTest target

*What is the expected output?*

I expect that the build succeeds and starts the tests

*What do you see instead?*

The build fails with an exception:

{{{
:app:dexDebugAndroidTest
UNEXPECTED TOP-LEVEL EXCEPTION:
com.android.dex.DexException: Multiple dex files define Lcom/google/thirdparty/publicsuffix/PublicSuffixPatterns;
at com.android.dx.merge.DexMerger.readSortableTypes(DexMerger.java:596)
at com.android.dx.merge.DexMerger.getSortedTypes(DexMerger.java:554)
at com.android.dx.merge.DexMerger.mergeClassDefs(DexMerger.java:535)
at com.android.dx.merge.DexMerger.mergeDexes(DexMerger.java:171)
at com.android.dx.merge.DexMerger.merge(DexMerger.java:189)
at com.android.dx.command.dexer.Main.mergeLibraryDexBuffers(Main.java:454)
at com.android.dx.command.dexer.Main.runMonoDex(Main.java:303)
at com.android.dx.command.dexer.Main.run(Main.java:246)
at com.android.dx.command.dexer.Main.main(Main.java:215)
at com.android.dx.command.Main.main(Main.java:106)
Error:Execution failed for task ':app:dexDebugAndroidTest'.
> com.android.ide.common.process.ProcessException: org.gradle.process.internal.ExecException: Process 'command '/Library/Java/JavaVirtualMachines/jdk1.8.0_45.jdk/Contents/Home/bin/java'' finished with non-zero exit value 2
}}}

*What version of the product are you using? On what operating system?*

Espresso 2.2, Guava 18.0 with AndroidStudio 1.2.2 on MacOS 10.10.4

Comments

[Deleted User] <[Deleted User]> #2Jun 13, 2016 01:29PM

Hi,

This looks really bad but w/o a repro app, we really cannot do anything about it. Is it possible for you to provide a sample app that reproduces your problem ?

pa...@gmail.com <pa...@gmail.com> #3Apr 15, 2017 08:38PM

Attached is a simple testing app. It inserts 10000 items into the db when activity starts and then displays them using paging. The db is also updated every 1 second. On the screen, if you drag the fast scroll bar up and down quickly a few times, it will eventually crash with this IndexOutOfBoundsException error.

nk...@google.com <nk...@google.com> Jun 19, 2017 09:24PM

Assigned to br...@google.com.

br...@google.com <br...@google.com> Jun 29, 2017 05:31PM

Marked as fixed.

pa...@gmail.com <pa...@gmail.com> #4Jun 29, 2017 09:55PM

Thanks for the great repro case, tracked it down, investigating a fix.

Problematic behavior:
1) AsyncPagedListDiffer receives new list, takes snapshot for diffing (ui thread)
2) At roughly the same time:
2a) Diff snapshot of old snapshot vs new snapshot (bg thread)
2b) New data arrives in new list, way earlier in the list, so the list is essentially: new page, lots of empty pages, initial load
3) AsyncPagedListDiffer updates lastLoad position with diffutil position mapping

In 3, we try to map the lastLoad position from old snapshot to new snapshot, but fail to distinguish between new list vs new snapshot. Because of all the empty pages, that's a huge discrepancy. This is why the huge scrollbar + lots of swaps triggers this well - there are lots of swaps to new PagedLists while loads are happening very far away from initial load positions.

Will need to account for pages loaded in between time of snapshot, and time of swap.

Issue 37063389