> For the complete documentation index, see [llms.txt](https://docs.idlayr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.idlayr.com/changelog/readme/ios-sdk-v2.4.1-2026-08-07.md).

# iOS SDK v2.4.1 (2026-08-07)

{% hint style="info" %}
**SDKs** · iOS · 2026-08-07
{% endhint %}

### What Changed

This release brings no changes to the SDK's code, APIs, or behavior. It's an entirely safe, drop-in upgrade that focuses on strengthening how we build, publish, and document the SDK.

* **More dependable releases.** Our release process has been overhauled and fully automated through CI, reducing the risk of release-day issues going forward.
* **Smoother installs via CocoaPods.** A corrected podspec source URL and improved package publishing ensure installs resolve cleanly every time.
* **Clearer documentation.** Our docs have been reorganized and expanded, making it easier to find what you need.

**Upgrading:** No code changes are required on your end.

### For more information on SDKs, see [SDKs & SDK-less](/get-started/sdks.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.idlayr.com/changelog/readme/ios-sdk-v2.4.1-2026-08-07.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.