> For the complete documentation index, see [llms.txt](https://docs.inji.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inji.io/inji-verify/releases/version-0.18.2.md). # Version 0.18.2 **Release Name**: Inji Verify v0.18.2 **Support**: Developer Release **Release Date**: 13th July, 2026 ### **Overview** We are pleased to announce the release of **Inji Verify v0.18.2**. Inji Verify **0.18.2** makes verify-service usable as a Maven library dependency, This patch release updates verify-service's build packaging so it can be consumed directly as a Maven dependency by other projects, in addition to running as a standalone service. The focus of this release is packaging: verify-service now publishes a plain library JAR as its default Maven artefact, alongside its existing executable JAR, with transitive dependencies resolved automatically via the published POM. It does **not introduce new features**, but improves stability, correctness, and reliability of existing functionality in the Inji Verify module. **Key Benefits**: * Embed verify-service's credential-verification logic directly inside another Java/Maven service * No manual dependency wrangling — transitive dependencies resolve through the published POM * Existing standalone/executable deployment of verify-service is unaffected {% hint style="info" %} **Note:** The Inji Verify UI is a *reference implementation* to demonstrate orchestration. Developers can selectively embed SDK components in the verifier applications as per their needs. {% endhint %} ### **Repositories: Released/Dependent** | Repositories | Tags: Released/Dependent | | ------------------- | --------------------------------------------------------------- | | Inji Verify Service | [**v0.18.2**](https://github.com/inji/inji-verify/tree/v0.18.2) | ### **Compatible modules** The following table outlines the tested and certified compatibility of Inji Verify 0.18.2 with other modules. | Module | Version | | ------------------ | ------------------------------------------------------------------ | | Inji Wallet | [0.22.1](https://github.com/inji/inji-wallet/releases/tag/v0.22.1) | | Inji Web | [0.17.0](https://github.com/inji/inji-verify/tree/v0.17.0) | | Pixel-Pass library | [0.8.0](https://github.com/inji/pixelpass/tree/v0.8.0) | ### **Bug Fixes** Below is the list of fixes as part of the **0.18.2** release, You can refer [here](https://github.com/inji/inji-verify/issues?q=milestone%3A0.18.2) to look at the list of bugs fixed through this release. | Bug ID | Summary | | -------------------------------------------------------- | ------------------------------------------------------------------------ | | [#2099](https://github.com/inji/inji-verify/issues/2099) | Configure verify-service to generate an additional library JAR - v0.18.2 | ### **Known Issues** Below is a list of some key known issues. For a detailed overview and the complete list of issues related to Inji Verify, please click [here](https://github.com/inji/inji-verify/issues?q=is%3Aissue%20state%3Aopen%20-milestone%3A1.0.0-alpha.1%20-label%3Ainjiverify_1.0.0%20type%3ABug)
Issue IDDescription
1790The OpenID4VP (Cross device) component in Inji Verify currently validates a presentation as successful even when a wrong Verifiable Credential (VC) is submitted. As a temporary workaround, implement credential type validation on the Relaying Party (RP) side, by verifying that the received VC matches the expected type defined in the original presentation_definition.
1845We are uploading an invalid QR code, and while it displays an error message stating that the QR code is invalid, the credential details are still visible.
1844On iPhone 8 and iPhone 7, uploading the Injiweb QR code PDF shows an error message.
1852Inji Verify - Upload not functioning on Mac Safari Browser Versions 16 and below.
1789INJI Verify SDK should be able to support integration with applications built on platforms beyond React (Typescript) applications, such as Angular, PHP, and others.
1805Long-polling listeners are implemented within the service layer, preventing the backend from scaling effectively in a multi-pod (distributed) environment.
### **Documentation** * [Feature documentation](https://docs.inji.io/inji-verify/overview/features) * [Integration Guide](https://docs.inji.io/inji-verify/technical-overview/integration-guides) * [API Documentation](https://mosip.stoplight.io/studio/inji-verify) * [Collab Guide](https://mosip.atlassian.net/wiki/spaces/PROD/pages/1306984580) * [QA Report](/inji-verify/releases/version-0.18.2/test-report.md) --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.inji.io/inji-verify/releases/version-0.18.2.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.