Skip to content

docs: iOS parity, fetch control, and deprecation notice updates#791

Open
jaredlockhart wants to merge 1 commit intomainfrom
2026-02-25-mobile-docs-misc
Open

docs: iOS parity, fetch control, and deprecation notice updates#791
jaredlockhart wants to merge 1 commit intomainfrom
2026-02-25-mobile-docs-misc

Conversation

@jaredlockhart
Copy link
Contributor

Summary

Follow-up to #787 with smaller gaps across mobile docs.

  • iOS recordMalformedConfiguration(): Added to iOS integration guide (was only in Android)
  • setFetchEnabled() / isFetchEnabled(): Documented QA fetch control methods in mobile-ui.md
  • Deprecated custom-targeting notices: Updated both Android and iOS to link to the new recordedContext builder option in the integration guides

Fixes #790

🤖 Generated with Claude Code

Because

* iOS integration guide was missing recordMalformedConfiguration()
  that was added to the Android guide
* setFetchEnabled/isFetchEnabled QA methods were undocumented
* Deprecated custom-targeting docs didn't link to the new
  recordedContext builder option in the integration guides

This commit

* Adds recordMalformedConfiguration() section to iOS integration guide
* Adds setFetchEnabled/isFetchEnabled section to mobile-ui.md
* Updates deprecated custom-targeting notices on both Android and iOS
  to link to the integration guide's recordedContext section

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

iOS parity, fetch control, and deprecation notice updates for mobile docs

1 participant