flame-harness-submit

Automating Flutter game store metadata deployment uses Fastlane to push localized titles, descriptions, and categories to App Store Connect and Google Play Console. This skill transitions your build artifact to a live submission by enforcing compliance checklists and state management. It safely pauses the pipeline before the final manual submission steps required by Apple and Google.

Publishing a Flutter game requires strict pre-submission compliance checks for ATT, privacy policies, and data safety questionnaires. Enforcing these guardrails prevents store rejections. This skill checks these regulatory requirements automatically during the metadata synchronization process before transitioning to manual store submission.

Fully automating the App Store submission is not possible because Apple requires manual action for the final step. This skill automates the upload of store text metadata and categories via Fastlane, then enforces a structured pipeline pause to provide you with the final manual submission instructions.

Syncing localized release notes to Google Play and App Store Connect is handled by running this skill at the end of your development pipeline. It requires configured Fastlane lanes and adheres to a harness protocol for metadata synchronization, ensuring all localized text reaches both platforms correctly.

Pre-configured Fastlane lanes are required to deploy Flutter game metadata. This skill relies on your existing Fastlane setup to push metadata to the App Store and Google Play, enforcing compliance and state management before pausing the pipeline for manual submission.

Your Flutter game deployment pipeline pauses because Apple and Google require critical manual submission steps. This skill enforces this structured pause after automating the metadata sync and compliance checks, ensuring you safely finalize the regulatory and metadata requirements before manually clicking submit.