> 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-9/v9-4-1-80691.md).

# Version 9.4.1.80691 Changelog (December 9th, 2022)

World's #1 PDF SDK Library for Web, Mobile, Server, Desktop

* Version: 9.4.1.80691
* Release Date: December 9th, 2022
* Built with Xcode 14.1 (14B47b)

## New

* Added German translations for the Line End Style feature.
* Created an API that allows you to customize the colour palette used for different annotations.
* Added a clear button in the input accessory view of a field to clear the current data.

## Bug fixes

* Fixed the `PTAnnotationViewController.readOnly` instance property not hiding the edit button.
* Fixed the annotation modified event not being called after editing a link annotation.
* Fixed a bug when using an Apple Pencil that caused the pencil-drawing annotation to disappear on zoom in/out.
* Fixed a crash on Mac Catalyst and macOS Ventura when opening a document.


---

# 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-9/v9-4-1-80691.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.