asc-in-app-events

1# asc in-app events
2 
3Use `asc app-events` for the requested stages only. A localization, media upload,
4or diagnostic request does not authorize creating or submitting another event.
5Preserve the resolved app, event, platform, locales, and existing authorization.
6 
7## Inspect the target
8 
9Check `asc app-events --help` and the relevant subcommand help before execution.
10Resolve the app ID and auth profile; inspect an existing event before changing it:
11 
12```bash
13asc app-events list --app "APP_ID" --paginate --output json
14asc app-events view --event-id "EVENT_ID" --output json
15asc app-events localizations list --event-id "EVENT_ID" --paginate --output json
16```
17 
18Use explicit `--output json` when parsing results; output defaults are TTY-aware.
19Keep event IDs and localization IDs distinct.
20 
21## Prepare and create
22 
23- Choose the event badge and intended territories. Check help for accepted
24  `--event-type`, `--purpose`, and `--purchase-requirement` values; do not infer
25  that every value described in App Store Connect is supported by the CLI.
26- Set future RFC 3339 dates: start before end, duration from 15 minutes to 31 days,
27  and publish start no more than 14 days before the event and no later than start.
28  The CLI parses timestamps but does not enforce all of Apple's schedule rules.
29- Provide a deep link that opens the event's destination. Test the universal link
30  or custom URL scheme in the intended app build; a registered scheme alone does
31…