> 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/learn-more/upgrading.md). # Updating to the latest version of Apryse for iOS Learn how to update PDFNet using Cocoapods or manual integration methods. Ensure your project is using the latest version for optimal performance. Call getVersion to verify the PDFNet version. The Apr ## Via Cocoapods If you have integrated PDFNet using [Cocoapods](/ios/get-started/integration.md), you can update PDFNet by using `pod update` from the command line, which will update all pods, or, `pod update PDFNet`, which will update PDFNet only. Note that this works only if you are using the `latest.podspec` and have not pinned to a specific version's podspec. ## Via manual integration If your app is integrating PDFNet [manually](/ios/get-started/integration.md), you should follow those steps again whenever a new version of the PDFNet framework is obtained. {% hint style="warning" %} **Ensuring use of the new framework** If you remove the old references to `PDFNet.framework` or `Tools.framework` from the project, and then drag the new copies to the project, Xcode may continue to use the original ones. This will happen if the *old location* is listed in the project's framework search paths before the *new location*. Ensure that your project is using the new copy of the framework by placing the new version in the same location as the old one, or by adjusting the framework search paths to reference only the new location. You can call the `PDFNet` type method (class method) [`getVersion`](https://sdk.apryse.com/api/ios/Classes/PTPDFNet.html#/c:objc\(cs\)PTPDFNet\(cm\)GetVersion) to verify which version of PDFNet is being used. {% endhint %} --- # 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/learn-more/upgrading.md?ask=&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.