store-forms

Automating App Store Connect and Google Play Console form submissions is done by running Python+Playwright scripts that read app.json and package.json to generate a forms_config.json, then execute deterministic browser automation to fill age rating, privacy, and compliance forms.

Yes, you can fill specific store forms like content rating or privacy by using per-form selection options, allowing you to target individual forms such as age_rating, content_rating, privacy, or ads declarations independently rather than running the entire submission workflow.

Yes, you need Python 3 and Playwright installed to automate filling mobile app store forms, along with a credentials store located at ~/.store-deploy/credentials.json to authenticate your App Store Connect and Google Play Console accounts during the automated submission process.

When UI elements change in App Store Connect or Google Play Console, the automation provides a manual fallback mode and stores error screenshots with troubleshooting guidance, ensuring you can diagnose failures and complete form submissions even when the deterministic scripts encounter unexpected page layouts.

Automating store submission forms requires app configuration files such as app.json or app.config.ts and package.json, which the scripts analyze to determine required fields and generate a forms_config.json that drives the Python+Playwright automation for both iOS and Android submissions.

Yes, you can test store form automation without submitting by using the dry-run option, which executes the Python+Playwright scripts against App Store Connect and Google Play Console forms without finalizing the submission, letting you verify field population and workflow behavior safely.