Skip to content

docs(mobile): add iOS allowlisted & private devices#166

Open
Erkan Erol (erkanerol) wants to merge 5 commits into
mainfrom
docs/ios-allowlisted-private-devices
Open

docs(mobile): add iOS allowlisted & private devices#166
Erkan Erol (erkanerol) wants to merge 5 commits into
mainfrom
docs/ios-allowlisted-private-devices

Conversation

@erkanerol

Copy link
Copy Markdown
Contributor

What

Adds a new Mobile group under the Features tab, with Android and iOS sections, and documents the two iOS device features for public customers.

New pages

  • Android devices — QA Wolf runs Android tests on ephemeral emulators provisioned fresh per run.
  • iOS devices — overview of real-device testing (shared pool + app resigning) and when to reach for the two features below.
  • Allowlisted devices (iOS) — for features that don't work on a resigned app (push notifications, universal links). Covers signing the app for QA Wolf's devices, injecting QA Wolf instrumentation (Fastlane action / script), targeting allowlisted devices, and disabling resigning via the qawolf:disableResigning capability.
  • Private devices (iOS) — devices dedicated to a single team for MDM testing and persistence across runs, with an allowlisted-vs-private comparison.

Navigation

Features → Mobile → { Android, iOS } added to docs.json.

Source

Adapted from the internal Allowlisted Devices and Private Devices feature docs.

Internal info deliberately excluded

Device UDIDs, customer names, MDS configuration, internal repos (ios-agent, deploy-production), instrumentation library internals, device-selection strategy, Apple Pay (marked not-yet-public), and internal Notion/Slack links.

Notes for review

  • Device targeting is documented using the internal meta: { ..., targetDevices } object ("Allowlisted Device" / "Team Dedicated Device"), per request. Note this differs from the existing public target string literals documented in the Target Literals reference (e.g. "iOS - iPhone 15 (iOS 26) (allowlisted)"). Worth deciding whether to reconcile the two in a follow-up.

🤖 Generated with Claude Code

Add a Mobile group under the Features tab with Android and iOS sections:

- Android: ephemeral emulators provisioned per run
- iOS: real devices shared across customers via app resigning, plus two
  features for cases the shared/resigning model can't cover:
  - Allowlisted devices: sign the app for QA Wolf's devices to test
    push notifications and universal links; includes instrumentation
    injection and disabling resigning
  - Private devices: devices dedicated to a single team for MDM testing
    and persistence across runs

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@mintlify

mintlify Bot commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
qawolf 🟢 Ready View Preview Jun 22, 2026, 10:31 AM

Replace the inline allowlisted/private targets note in the API reference
with links to the Allowlisted devices and Private devices pages.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (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

Development

Successfully merging this pull request may close these issues.

1 participant