> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/agent-release-notes/android-plugin.md).

# Android Plugin

## 2026 Release Notes

<table><thead><tr><th width="239.97265625">Version</th><th width="149.265625">Date</th><th>Changes</th></tr></thead><tbody><tr><td><p>Android Plugin 1.0.48</p><p>Android Test Listener 2.0.36</p></td><td>August 31, 2026</td><td><p><strong>New Features and Updates:</strong></p><ul><li>Upgraded Apache HttpClient to 5.6.4 and Jackson to 2.22.2 to address CVE-2026-68497, sonatype-2026-005959, and CVE-2026-71290.</li></ul></td></tr><tr><td>Android Plugin 1.0.42 Android Test Listener 2.0.30</td><td>July 21, 2026</td><td><p><strong>New Features and Updates:</strong></p><ul><li>Improved per-module CLI data resolution for multi-module builds by using the Gradle project path as the module key instead of the display name.</li><li>Added <code>staticParams</code> support to the Android configuration class to enable configuration overrides through system properties.</li><li>Added static parameters and system property configuration overrides to the Android Test Listener.</li><li>Added DEBUG-level logging for build configuration values such as <code>buildSessionId</code>, <code>appName</code>, and <code>branchName</code>.</li></ul><p><strong>Resolved Issues:</strong></p><ul><li>Removed vulnerabilities and updated dependencies in the Android Test Listener.</li></ul></td></tr><tr><td>Android Plugin 1.0.36 Android Test Listener 2.0.24</td><td>May 25, 2026</td><td><p><strong>New Features and Updates:</strong></p><ul><li>Improved build scanner attachment for multi-module Android projects.</li><li>Introduced <code>BuildScannerConfiguratorResolver</code> to replace the monolithic configurator with a modular approach.</li><li>Replaced integer-based method IDs with direct string signatures in the Android Test Listener, removing the <code>MethodIdIndex</code>, <code>MethodIdFileIndex</code>, and <code>MethodDataProvider</code> indirection layer.</li><li>Added static code instrumentation with a dynamic method index to the Android Plugin.</li></ul></td></tr><tr><td>Android Plugin 1.0.34 Android Test Listener 2.0.23</td><td>May 15, 2026</td><td><p><strong>New Features and Updates:</strong></p><ul><li>Upgraded the ASM bytecode manipulation library.</li><li>Added a CI pull request review workflow for the Android Test Listener.</li><li>Set the base version of the Android Test Listener to 2.0.</li></ul><p><strong>Resolved Issues:</strong></p><ul><li>Fixed <code>androidBuildType</code> population in the build scanner configuration.</li><li>Fixed <code>TokenData</code> tests in the Android Test Listener.</li></ul></td></tr><tr><td>Android Plugin 1.0.27 Android Test Listener 2.0.20</td><td>April 14, 2026</td><td><p><strong>New Features and Updates:</strong></p><ul><li>Upgraded infrastructure and Java agent dependencies.</li><li>Implemented the tinylog logging framework in the Android Test Listener.</li><li>Remediated transitive vulnerabilities.</li></ul></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sealights.io/knowledgebase/agent-release-notes/android-plugin.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.