116 lines
10 KiB
Markdown
116 lines
10 KiB
Markdown
---
|
|
name: console-autofill
|
|
description: AI-assisted autofill of App Store Connect and Google Play Console forms that have no API (the New App dialog, App Privacy, the Play IARC content rating questionnaire, Target audience and content plus the Ads declaration; the App Store age rating is shown as guidance because the API sets it) in a visible browser that reuses the owner's Chrome sign-in (or one they sign in to); storebound opens the form itself. Answers come only from storebound.config.ts; anything the config does not prove stays empty and highlighted. storebound never signs in, never saves, submits or publishes. Use when the user wants help filling one of these console forms, asks what to answer in them, or wants the answers as a checklist.
|
|
---
|
|
|
|
# Console autofill (forms without an API)
|
|
|
|
CLI: `storebound` (or `bunx storebound` in a project that has it, or `bun <toolchain>/cli/index.ts`).
|
|
|
|
**Read this to the owner first.** Console pages change without notice. This is AI-assisted autofill and it may put an
|
|
answer in the wrong place. The owner reviews every field and presses the final button. storebound never types a
|
|
password, never touches a sign-in page, never prints or sends a cookie, and never clicks Save, Submit, Publish, Create,
|
|
Next or any similar control (English or Turkish console); it only clicks to open the form. It reuses the owner's
|
|
Chrome sign-in through a temporary copy of only the console cookies (deleted at the end; `--fresh-profile` opts out).
|
|
It is not available over MCP.
|
|
|
|
## Forms
|
|
|
|
| form | where | filled from |
|
|
|---|---|---|
|
|
| `apple-app-record` | App Store Connect > Apps > + > New App | apple.name (else app.name), apple.primaryLocale, apple.bundleId, console.appRecord (SKU, user access) |
|
|
| `apple-age-rating` | App Information > Age Ratings | guide only: `storebound apple appinfo` sets every question through the API |
|
|
| `apple-app-privacy` | the app > App Privacy | dataSafety (types and purposes); linked to identity and tracking are always the owner's |
|
|
| `play-content-rating` | Policy > App content > Content rating | app.contactEmail, app.profile, products, console.contentRating |
|
|
| `play-target-audience` | Policy > App content > Target audience and content (+ Ads) | console.targetAudience, ads.appAdsTxt |
|
|
|
|
## Steps
|
|
|
|
1. `storebound console fill` lists the forms. `storebound console fill <form> --dry` prints every answer with its
|
|
source; `[check]` lines are not proven by the config. Show them to the owner.
|
|
2. For each `[check]` line, ask the owner (AGENTS.md rule 5: never guess a compliance answer). If they want it filled
|
|
next time, add it to the config, for example:
|
|
```ts
|
|
console: {
|
|
appRecord: { sku: 'com.example.game', userAccess: 'full' },
|
|
contentRating: { category: 'game', answers: { violence: false, lootBoxes: false, userInteraction: false } },
|
|
targetAudience: { ages: ['13-15', '16-17', '18-over'], appealsToChildren: false, containsAds: true },
|
|
},
|
|
```
|
|
Age rating answers live in `apple.info.ageRating` (also `socialMedia`, `socialMediaAgeRestricted`).
|
|
3. The owner runs `storebound console fill <form>` in a terminal (or presses the button in the desktop app). The
|
|
first log line says which browser it uses, in this order:
|
|
- **attach**: Chrome already runs with remote debugging (a `DevToolsActivePort` file in Chrome's user data folder,
|
|
or `--cdp http://127.0.0.1:<port>`): storebound opens one new tab there and closes only that tab.
|
|
- **copy** (default on macOS with Google Chrome installed): the owner's existing Chrome sign-in, no second sign-in.
|
|
storebound copies ONLY `Local State` and the profile's `Cookies` (+ `Cookies-journal`) into a temporary folder,
|
|
deletes every cookie there except the ones App Store Connect and Play Console get (apple.com and google.com
|
|
domains), and opens real Google Chrome on that copy. Never copied: passwords (`Login Data`), history, extensions,
|
|
bookmarks or anything else. The temporary folder is deleted when the run ends (window closed, error, Ctrl+C, or
|
|
Cancel in the desktop app). Chrome decrypts the cookies with its own Keychain key ("Chrome Safe Storage"); macOS
|
|
may ask once to allow that. `--chrome-profile "Profile 1"` picks another Chrome profile (default: the last used).
|
|
Cookies are never printed, logged or sent anywhere.
|
|
- **profile** (`--fresh-profile`, `--profile <dir>`, `STOREBOUND_CONSOLE_PROFILE`, or when the other two do not
|
|
work): storebound's own profile (`~/.storebound/console-profile/<store>`, one per store, not per account: every
|
|
studio shares the one login). The owner signs in there once; it is kept for the next run.
|
|
Keeping the sign-in: Apple's and Google's sign-in cookies are partly session cookies. storebound launches the copy
|
|
and the own profile with `--restore-last-session` (so Chromium loads them again) and always closes the browser
|
|
gracefully (window closed or Ctrl+C), so they are written to disk. Apple keeps a long sign-in only with "Keep me
|
|
signed in" ticked and "Trust" chosen for the browser; Google with "Stay signed in"; storebound reminds the owner on
|
|
the sign-in page. In copy mode the owner's Chrome Cookies file holds the session cookies only while that Chrome
|
|
runs, or when Chrome's "On startup: Continue where you left off" is on; otherwise one sign-in in the window is
|
|
needed.
|
|
Sign-in is detected by URL and by frame (App Store Connect `/login`, a frame from idmsa.apple.com /
|
|
appleid.apple.com, accounts.google.com, Google `/signin`), by a visible password field in any frame, and by the
|
|
form's own texts ("Sign in with Passkey", "Email or Phone Number", "Keep me signed in" and the Turkish ones):
|
|
Apple's form starts with no password field. storebound checks before every navigation step, after each click or
|
|
load, and while a step waits. Then it prints "sign in in the browser window; storebound waits" and waits up to
|
|
10 minutes, never typing or reading anything there; when the console is back (no sign-in page, the console URL)
|
|
it opens the form again from step 1.
|
|
4. After sign-in storebound opens the form itself and logs every step ("opening the form, step 2/4: the add button
|
|
(+)"): New App: Apps > + > New App; App Privacy: `/apps/<apple.appId>/distribution/privacy`, or the app list > the
|
|
app (by name / bundle id) > App Privacy; Play forms: the app list > the app (by `play.packageName`) > Policy and
|
|
programs > App content > the form's Start or Manage link. These navigation clicks pass the same click gate: never
|
|
Save, Submit, Publish, Create, Send, Next or the Turkish equivalents; only a LINK named exactly Start / Manage /
|
|
Başla / Yönet is let through. If a step is not found in time, or two apps match (they are listed: set
|
|
`apple.appId` / `play.packageName`), storebound says which step failed, prints what to click, and keeps watching:
|
|
a sign-in that finishes restarts navigation at step 1; when the owner moves on by hand (the + button, the New App
|
|
item, the app in the list appear) it continues from that step; when the owner opens the form it fills it. Watching
|
|
ends when the window is closed. App
|
|
Privacy: the owner clicks Get Started (or Edit next to Data Types). When the form appears storebound fills the
|
|
certain answers, outlines every unproven or unfillable field with a "storebound: check this" label, and lists them
|
|
in the terminal.
|
|
5. **One login, many developer accounts or teams.** storebound never asks for a second sign-in; it finds the
|
|
account that has the app and remembers it in `~/.storebound/console-accounts.json` (ids only, never cookies;
|
|
shared with the desktop app):
|
|
- Play: the app list of one account is `/console/u/0/developers/<id>/app-list`. The id is `play.developerId` in
|
|
the config, else the workspace account's `developerId` (`storebound.workspace.json`, passed as
|
|
`STOREBOUND_PLAY_DEVELOPER_ID`), else the remembered one; else storebound reads every developer account on the
|
|
"Choose a developer account" page and looks for `play.packageName` in each app list ("developer account 4/5:
|
|
..."). A package in none of them is said plainly (create the app, or ask to be invited).
|
|
- App Store Connect: the team is switched in the account menu at the top right. Order: the remembered team, the
|
|
menu entry that names `apple.teamId` (or the workspace account's `teamId`), then every other team. The app is
|
|
recognized by its entry in the app list (App Privacy) or, for a new app, by the bundle id in the New App dialog's
|
|
Bundle ID list (Cancel closes the dialog in a team without it). App Store Connect has no documented URL
|
|
parameter that picks a team, so storebound does not use one.
|
|
- Switching only changes what the console shows. Each switch click must be an account name storebound just read
|
|
from the chooser or the menu, and never Sign Out or a deny-listed name (a studio called "Next Games" is left
|
|
for the owner to pick).
|
|
6. Multi-page forms: the owner reviews the page and clicks Next; storebound fills the next page when it appears.
|
|
7. On the last page storebound prints "review every field and press <Save | Submit | Publish | Create> yourself". The
|
|
command ends when the owner closes the window (`--json` then prints the result with `filled`, `highlighted`,
|
|
`fallback`, `stoppedAt`).
|
|
8. If a field cannot be found or matches twice (for more than a moment: a page that is still loading does not count), the console UI changed: storebound stops filling and prints the
|
|
step-by-step list ("label: answer") for the owner to copy. That is the expected safe behavior, not an error.
|
|
|
|
## The owner decides
|
|
|
|
Every `[check]` answer, linked-to-identity and tracking for each App Privacy data type, the IARC answers, the target
|
|
ages, and pressing the final button (App Privacy Publish, IARC Submit, Target audience Save, New App Create).
|
|
|
|
## Out of scope
|
|
|
|
- Signing in, two-factor codes, accepting agreements, creating developer accounts or teams.
|
|
- Forms with an API: Data safety (`storebound play data-safety`), age rating, categories and content rights
|
|
(`storebound apple appinfo`), export compliance (`storebound apple encryption`).
|
|
- Recording or reading console data: storebound only fills the visible form.
|