Skip to content

docs: appId in associated-domains registration is the app identifier, not a domain - #121

Open
dianaKhortiuk-frontegg wants to merge 1 commit into
masterfrom
docs/fix-associated-domain-app-id
Open

docs: appId in associated-domains registration is the app identifier, not a domain#121
dianaKhortiuk-frontegg wants to merge 1 commit into
masterfrom
docs/fix-associated-domain-app-id

Conversation

@dianaKhortiuk-frontegg

Copy link
Copy Markdown
Collaborator

Companion to frontegg/frontegg-ios-swift#314 - full analysis and live-environment evidence there.

docs/setup.md told readers to register a domain in the appId field of POST /vendors/resources/associated-domains/v1/ios. The field is the Apple app identifier ({teamId}.{bundleId}) as published in the apple-app-site-association file. The API accepts any string without validation, so a domain registered there produces an AASA entry iOS silently ignores - Universal Links and passkeys fail with no error anywhere.

Corrected the payload to {{TEAM_ID}}.{{BUNDLE_ID}} with a concrete example and a warning about the silent failure.

Docs-only change.

🤖 Generated with Claude Code

…ier, not a domain

The guide told readers to put a domain in the appId field of
POST /vendors/resources/associated-domains/v1/ios. The field is the Apple app
identifier ({teamId}.{bundleId}) published in the apple-app-site-association
file; the API accepts any string without validation, and a domain registered
there yields an AASA entry iOS silently ignores, so Universal Links and
passkeys fail with no error. Same fix as frontegg-ios-swift#314.

Co-Authored-By: Claude Opus 5 <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.

1 participant