AppsFlyer iOS SDK release notes (July 2026): fewer lost purchases, better ATT timing, and more explicit consent plumbing
AppsFlyer’s iOS SDK release notes (last modified July 27, 2026) include fixes to purchase validation reliability, improvements to Apple Search Ads token timing when waiting for ATT, and a continued push toward explicit consent and hashed PII handling. For growth teams, this is ‘measurement stability’ work, not a developer nicety.
Original post (source): AppsFlyer Developer Docs - “iOS Release Notes” (updated July 27, 2026)
Highlights (what is likely to matter in practice)
This page is a rolling changelog, but a few items are notable for app growth teams because they touch measurement and revenue reliability:
- Purchase validation reliability: a fix where purchase validation requests that failed due to a network error could be lost after an app restart. The SDK now attempts to retrieve pending StoreKit transactions on init and re-submit.
- Apple Search Ads token timing: improved handling of ASA token requests when using waitForATTUserAuthorization, deferring requests until the user decision or timeout.
- Consent + privacy plumbing: additional consent flags (including an “ad_storage” flag) and continued emphasis on explicit consent handling.
- API cleanup: removal of older setUserEmails/setPhoneNumber APIs in favor of single-value setters.
Why this matters
Two practical themes:
-
You can’t out-market broken plumbing. If purchases are intermittently lost or not validated, you will misread LTV, subscription starts, and even channel performance.
-
Privacy changes show up as performance volatility. ATT timing, consent, and SDK behavior change the stability of your attribution signals, especially during launches.
Tiny win
If you are running meaningful spend on iOS, treat “SDK upgrade cadence” like part of your growth stack:
- write down your current attribution + purchase SDK versions
- set a quarterly upgrade window (and a hotfix path for critical bugs)
- after upgrades, run a quick regression on: install attribution, deep links, and purchase/restore flows
Want help with ASO?
If you want this implemented for your app, check out our services - or run your workflow in APPlyzer.