Frequently asked questions
App Store Connect, AI providers, and the things that trip people up
Which App Store Connect role does my API key need?
App Manager is enough to read and write metadata, and it is the role we recommend. Admin works too, but it grants far more than the app needs. Mint a dedicated key rather than reusing an Account Holder key, so the blast radius stays small if it ever leaks.
Why can I only publish promotional text?
That is Apple, not us. Promotional text is the one field that can change without a new submission. Every other field needs an app version in an editable state. Create or edit a version in App Store Connect, then publish again and the remaining fields will go through.
One locale failed and the others worked. What now?
Retry that locale on its own from the review panel. Generation and publishing are per-locale, so a single failure never invalidates the locales that succeeded and never makes you re-run the whole job.
Why do my Chinese or Japanese keywords come back shorter?
Apple caps the keyword field at 100 bytes, not 100 characters. A Chinese, Japanese, Korean or Arabic character can cost up to three bytes, so a keyword list that fits comfortably in English overflows in those locales. The app enforces the byte limit while generating, which is why some locales come back with fewer keywords rather than a truncated, rejected field.
How much does the AI cost?
Whatever your provider charges. You bring your own Anthropic, OpenAI or DeepSeek key and they bill you directly at their list prices. We add no markup, take no cut, and never see your usage.
Can I use it on a second Mac?
Yes. Your keys live in the macOS Keychain on the Mac where you entered them, so add them again on the second machine. Nothing is tied to an account with us, because there are no accounts.