> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/ios/changelogs/version-12/12-2-0.md).

# Version 12.2.0 Changelog (October 1, 2026)

Review the 12.2.0 changelog for the Apryse Mobile SDK.

### Notes

* Version 12.2.0.30566
* Built with Xcode 15.4 (15F31d)

### New

* \[Liquid Glass] Added a glass-effect background to the top navigation tool group switcher, plus a new `PTToolGroupIndicatorView.hidesBackground` option to hide it when needed. Standard `tintColor` customization is still supported.

### Fixes

* \[Liquid Glass] Fixed layout and sizing issues in the free text annotation toolbar, and removed the duplicate **Choose Fon**t title in the font picker.
* \[Liquid Glass] Fixed the layout and appearance of the form-fill toolbar.
* \[Liquid Glass] Fixed the tool group switcher tint color to match the other top bar buttons.
* \[Liquid Glass] Fixed the tint color of the navigation lists and reading mode buttons in `PTDocumentController` to match the other toolbar buttons.


---

# 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.apryse.com/ios/changelogs/version-12/12-2-0.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.