Document iOS target configuration requirements for DAT apps#161
Conversation
|
Hi @gmays! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
Summary
Adds README guidance for common iOS target configuration required by DAT integrations.
This documents the native app configuration values consumers need to verify when integrating the SDK outside a plain Xcode sample, including app link scheme registration,
MWDATkeys, URL scheme querying, external accessory protocol, Bonjour/local network permissions, Bluetooth permissions, microphone/photo usage strings, and background modes.Why
The current README explains how to add the package through Swift Package Manager, but it does not summarize the native iOS target configuration needed for registration, device discovery, and camera/media flows.
When integrating DAT into an Expo/React Native iOS app, missing or unclear plist/capability setup caused registration/device readiness failures and stale native builds. A checklist in the public README would reduce integration friction for other consumers.
Test Plan
Docs-only change. Verified the README Markdown with
git diff --checkandgit diff --cached --check.