> 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/web/changelogs/version-6/v6-0/v6-0-4.md).

# Version 6.0.4 Changelog (2020-01-10)

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

## Fixes

* Fixed issue where an error could occur sometimes when searching immediately after documentLoaded
* Fixed a number of incorrect types in the TypeScript declaration file
* Fixed issue with using TypeScript declaration file when importing WebViewer from npm
* Fixed issue where the stamp tool did not open the file dialog in iOS 13
* Fixed issue where selecting an annotation and holding the shift key while using the polyline tool would throw an error
* Fixed issue with loading WebViewer in some Salesforce environments
* Fixed issue with undo not working for the first change of an imported annotation


---

# 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.apryse.com/web/changelogs/version-6/v6-0/v6-0-4.md?ask=<question>&goal=<endgoal>
```

`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.