appium-espresso-driver 8.5.6 → 8.6.1

package/CHANGELOG.md

@@ -1,3 +1,15 @@
+## [8.6.1](https://github.com/appium/appium-espresso-driver/compare/v8.6.0...v8.6.1) (2026-06-19)
+
+### Miscellaneous Chores
+
+* **deps:** bump composeUiTest in /espresso-server ([#1179](https://github.com/appium/appium-espresso-driver/issues/1179)) ([931be2d](https://github.com/appium/appium-espresso-driver/commit/931be2de4873b81dcee5771a98a0bbbaec179ae6))
+
+## [8.6.0](https://github.com/appium/appium-espresso-driver/compare/v8.5.6...v8.6.0) (2026-05-24)
+
+### Features
+
+* Add a script for app diagnosis ([#1175](https://github.com/appium/appium-espresso-driver/issues/1175)) ([c2b48e8](https://github.com/appium/appium-espresso-driver/commit/c2b48e828d8595c90cba4e5222e21485f99b686d))
+
 ## [8.5.6](https://github.com/appium/appium-espresso-driver/compare/v8.5.5...v8.5.6) (2026-05-23)
 
 ### Miscellaneous Chores

package/README.md

@@ -13,6 +13,8 @@ The Espresso package consists of two main parts:
 - The driver part (written in Node.js) ensures the communication between the Espresso server and Appium. Also includes several handlers that directly use ADB and/or other system tools without a need to talk to the server.
 - The server part (written in Kotlin with some parts of Java), which is running on the device under test and transforms REST API calls into low-level Espresso commands.
 
+See the [end-to-end architecture diagram](./docs/architecture.md).
+
 > [!IMPORTANT]
 > Since major version *5.0.0*, this driver is only compatible with Appium 3. Use the `appium driver install espresso`
 > command to add it to your distribution.
@@ -239,6 +241,8 @@ The `swiper` argument is not supported in Compose mode. Available since driver v
 
 Calling other driver element-specific APIs not listed above would most likely throw an exception as Compose and Espresso elements are being stored in completely separated internal caches and must not be mixed.
 
+If session startup or Compose interactions fail, see [How To Troubleshoot Jetpack Compose Apps](docs/compose-troubleshooting.md).
+
 You could also check end-to-end tests for more examples on how to setup test capabilities and
 on the Compose usage in general:
 - https://github.com/appium/appium-espresso-driver/blob/master/test/functional/commands/jetpack-componse-element-values-e2e-specs.js
@@ -1830,6 +1834,8 @@ more details.
 
 ## Troubleshooting
 
+* Run `appium driver run espresso diagnose-app --app /path/to/your/android-project` or `--app /path/to/debug.apk`. The script checks manifest permissions, obfuscation, AndroidX/Compose dependency alignment, and other static preconditions for precompile. Exit code is non-zero when the app is not ready for precompile.
+* If you test **Jetpack Compose** apps (or hybrid View + Compose UIs) and see server startup failures, `NoSuchMethodError` in `androidx.compose.*`, misleading `INTERNET` permission errors, `InitializationProvider` / `Resources$NotFoundException`, or locator issues in `compose` subdriver mode, read [How To Troubleshoot Jetpack Compose Apps](docs/compose-troubleshooting.md).
 * If you observe Espresso server crash on startup and various exceptions about missing class/method in the logcat output then consider updating [appium:espressoBuildConfig](#espresso-build-config) capability with module versions that match your application under test. This might require some experimentation, as different apps have different module requirements. Check, for example, [issue #812](https://github.com/appium/appium-espresso-driver/issues/812). Another solution might be
 to [integrate](#consuming-espresso-server-as-library) Espresso Server with the application under test in form of a library.
 * If you experience issues with application activities being not found or not starting then consider checking [How To Troubleshoot Activities Startup](docs/activity-startup.md) article.
@@ -1851,8 +1857,6 @@ to [integrate](#consuming-espresso-server-as-library) Espresso Server with the a
   -keep class android.support.v7.** { *; }
   ```
   Please read [#449](https://github.com/appium/appium-espresso-driver/issues/449#issuecomment-537833139) for more details on this topic.
-* When you want to build without compose dependencies
-    * Espresso driver has Jetpack Compose dependencies to [support Jetpack Compose](#jetpack-compose-support). It could break the application under test's dependencies. The typical case is when the application under test does not have the Jetpack Compose dependencies. Then, you can try out [no compose dependencies branch](https://github.com/appium/appium-espresso-driver/pull/879)). In Appium 2.0, the branch is available as `appium driver install --source=local /path/to/the/appium-espress-driver` with the `no-compose-deps` branch instead of npm installation.
 
 
 ## Contributing

package/espresso-server/buildSrc/.gradle/buildOutputCleanup/cache.properties

@@ -1,2 +1,2 @@
-#Sat May 23 18:58:58 UTC 2026
+#Fri Jun 19 05:54:14 UTC 2026
 gradle.version=9.5.1

package/espresso-server/gradle/libs.versions.toml

@@ -3,7 +3,7 @@ androidGradlePlugin = "9.2.1"
 kotlin = "2.3.21"
 androidxTest = "1.7.0"
 annotation = "1.10.0"
-composeUiTest = "1.11.2"
+composeUiTest = "1.11.3"
 gson = "2.14.0"
 espresso = "3.7.0"
 nanohttpd = "2.3.1"

package/espresso-server/library/src/main/java/io/appium/espressoserver/lib/helpers/Version.kt

@@ -2,6 +2,6 @@ package io.appium.espressoserver.lib.helpers
 
 // This value is updated automatically by the NPM versioning script
 // It should be in sync with the NPM module version from package.json
-private const val VERSION = "8.5.6"
+private const val VERSION = "8.6.1"
 
 fun getEspressoServerVersion() = VERSION