asc in-app events

Use asc app-events for the requested stages only. A localization, media upload, or diagnostic request does not authorize creating or submitting another event. Preserve the resolved app, event, platform, locales, and existing authorization.

Inspect the target

Check asc app-events --help and the relevant subcommand help before execution. Resolve the app ID and auth profile; inspect an existing event before changing it:

asc app-events list --app "APP_ID" --paginate --output json
asc app-events view --event-id "EVENT_ID" --output json
asc app-events localizations list --event-id "EVENT_ID" --paginate --output json

Use explicit --output json when parsing results; output defaults are TTY-aware. Keep event IDs and localization IDs distinct.

Prepare and create

• Choose the event badge and intended territories. Check help for accepted --event-type, --purpose, and --purchase-requirement values; do not infer that every value described in App Store Connect is supported by the CLI.
• Set future RFC 3339 dates: start before end, duration from 15 minutes to 31 days, and publish start no more than 14 days before the event and no later than start. The CLI parses timestamps but does not enforce all of Apple's schedule rules.
• Provide a deep link that opens the event's destination. Test the universal link or custom URL scheme in the intended app build; a registered scheme alone does not prove the destination works. Creation without a deep link can succeed even though the event is not ready for review.

Replace the date variables with the agreed schedule before creating: