Uploading a binary from a chat is nice; being able to say 'stop the rollout' and have it happen immediately is the reason to wire this in. Proceeding, rolling back, halting and changing the percentage are each their own call, so the release can be steered from wherever you notice the problem — including from a phone.
A server over AppGallery Connect's publishing API. It covers the release cycle end to end — metadata, localised listings, binary upload, submission and phased release — with the app id defaulted from the environment so most calls do not need it.
- query_app_info and update_app_info for the draft's metadata, name, description, category and support contacts
- update_language_info and delete_language_info for a store listing in one language
- get_upload_url and upload_app_file — an APK or AAB from disk, chunked automatically when it is very large
- update_app_file_info to attach a binary you uploaded some other way
- query_compile_status for where an AAB is in compilation
- submit_app for review and release — full, phased, scheduled, or open testing
- submit_app_with_file when the binary is hosted on your own server
- change_phased_release_state and update_phased_release to proceed, roll back, stop, or change the rollout percentage
- update_release_time and set_gms_dependency
- get_download_report_url and get_install_failure_report_url for the reports after release
Connect API credentials — HUAWEI_CLIENT_ID and HUAWEI_CLIENT_SECRET, created under Users & Permissions with the App manager role. These are not the same as HMS Core app credentials, which is the usual first mistake. Set HUAWEI_APP_ID to avoid passing the app to every call. Installed from the registry or from pip.
One command plus a key — pip install huawei-app-gallery-mcp, then supply credentials