Commit ebc34132 authored Apr 16, 2024 by Colin Cross

Don't statically include DocumentsUI-lib in tests

DocumentsUI-libs shouldn't be included in tests, tests get those
classes via the app they are instrumenting. Including DocumentsUI-libs
causes androidx.startup to be included in both the app and the tests,
which then causes failures when starting the tests due to resource
conflicts:

Unable to get provider androidx.startup.InitializationProvider: android.content.res.Resources$NotFoundException: String resource ID #0x7f12001e
java.lang.RuntimeException: Unable to get provider androidx.startup.InitializationProvider: android.content.res.Resources$NotFoundException: String resource ID #0x7f12001e

Bug: 328639759
Test: atest DocumentsUIGoogleTests
Flag: TEST_ONLY
Change-Id: I05ba39a0fe51a455da95b6497ef2cb1243ea615f

parent 58e95f66

tests/Android.bp

+8 −1

Original line number	Diff line number	Diff line
		@@ -25,7 +25,6 @@ java_defaults {
		],

		static_libs: [
		"DocumentsUI-lib",
		"androidx.test.rules",
		"androidx.test.espresso.core",
		"androidx.test.ext.truth",
		@@ -70,6 +69,10 @@ android_library {
		"unit/*/.java",
		],

		libs: [
		"DocumentsUI-lib",
		],

		resource_dirs: [
		"res",
		],
		@@ -90,6 +93,10 @@ android_library {
		"unit/*/.java",
		],

		libs: [
		"DocumentsUI-lib",
		],

		asset_dirs: [
		"assets",
		],