Overview
Publishing is the one action that sends your draft to the store. It is always yours to start: use Ready for reviewin the Editor or the Agent inbox header, or give Agent chat an explicit publish command when your role and the app's provider prerequisites allow it. A recurring agent run never starts it.
Ready for review sits in the editor header and to the right of All countries on the Agent inbox. The pop-up resolves store conflicts, a missing version, or a missing build before the final send. If there is nothing to send it says so rather than making a call.
Preflight
Before anything is sent, Spek checks the draft against what the store will accept: field limits, required values, and whether the version is in a state that allows an edit at all.
A fixable gap (a store conflict, a missing version, or a missing build) stays in the pop-up so you can finish it there. An unfixable failure stops the send and says what to fix. Nothing has been sent at that point.
Chat performs the same current-store, draft-revision and conflict checks on the server. Naming one locale sends that locale; naming several binds the exact set into one publish operation; leaving locale scope out means every pending locale for the selected app.
What publishing sends
Only the fields that differ from the store, for the markets you selected. Publishing writes those drafts and submits the eligible current version to App Review. If there is no draft change, an eligible version can still be submitted. Spek does not publish the app binary itself.
If some markets succeed and others do not, it reports Publish finished with errors and names the ones that failed, rather than rolling everything back.
Submitting for review
An iOS listing publish starts with Ready for reviewand ends with Submit for review in the same pop-up when the current version is eligible. Between the two, the pop-up lists every field about to change with its value before and after. The keyword field is shown word by word — the words leaving in red, the words joining in green — so a two-word change is not buried in a long comma list. Apple can keep other items in the same draft review submission, so those staged events, product pages or tests may go to review with the version.
Common questions
Can the agent publish for me?
Agent chat can publish after your explicit interactive command when your role and the app's provider prerequisites allow it. The recurring agent never publishes store content. See what the agent will never do.
Publishing failed for one market only.
That market's value was rejected by the store, usually a length or a required-field problem. The others went through; fix that one and publish again.
The store response was uncertain. Should I retry?
In Agent chat, use Reconcile. In Editor, opening publish again checks the same durable operation against the store before any new write. Spek replays an already-finished result or keeps an unresolved mismatch quarantined; it does not blindly send the same mutation again. Retry appears only when repeating the request is known to be safe.
Can I undo a publish?
Not from Spek. Edit the values back and publish again, the same way you would in the store console.