HarmonyOS 7.0 App Store Submission: Complete Step-by-Step Guide
A comprehensive technical walkthrough for publishing HarmonyOS apps to AppGallery Connect, covering key generation, certificate and profile management, dual signing configurations for debug and release, package upload validation, asset specifications, compliance requirements, and version upgrade procedures.
Overview: Six Steps to App Store Submission
Publishing a HarmonyOS app is not a single upload action but a chain: generate keys locally, request certificates and profiles on AppGallery Connect (AGC), configure signing in the project, build and upload the package, complete store metadata, then submit for review. The first three steps ensure the package can be signed; step four ensures it can be uploaded; the last two ensure it passes review.
Four Key Files: Local vs Cloud
Manual signing requires four files. Two are generated locally in DevEco Studio via Build > Generate Key and CSR :
Keystore .p12 : holds a public/private key pair for digital signing and verification.
Certificate Signing Request .csr : contains the public key and organization info, used to request a certificate from AGC.
The other two are issued by AGC based on the .csr:
Digital Certificate .cer : issued by AGC, proves ownership of the public key.
Profile .p7b : binds package name, certificate, allowed permissions, and debug devices; every app package must include one.
Rule : .p12, .csr, and .cer can be shared across multiple apps; .p7b is per-app because it contains the package name. Release certificates are valid for 3 years; debug certificates for 180 days. Account limits: 3 release certificates, 3 debug certificates, 100 profiles per app. Revoked certificates do not count against quotas.
Generating Keystore and CSR
In DevEco Studio, open Build > Generate Key and CSR . Two values must be recorded:
Keystore password : must contain at least two of uppercase, lowercase, digits, special symbols; minimum 8 characters.
Alias : arbitrary but memorable; used later in signing config.
Set validity to 25+ years to cover the app lifecycle. The wizard produces .p12 and .csr files. Note: the CSR does not contain the package name; changing the package name only requires a new Profile, not a new keystore.
Creating App, Certificate, and Profile on AGC
Order matters: create app (get APP ID) → request certificate → request profile . Profile binds both app and certificate, so it comes last.
1. Create App
In AGC, go to Certificates, App IDs and Profiles > App ID , choose HarmonyOS app. The package name must exactly match bundleName in AppScope/app.json5 and cannot be changed later. Rules: 7–128 chars, at least three dot-separated segments, no consecutive dots, alphanumeric plus underscore, cannot use reserved words (oh, ohos, harmony, etc.), must be unique across Android and HarmonyOS apps. Device types can be added later but not removed. Category is also immutable.
2. Request Certificate
Switch to Certificates , click Add Certificate . Name suggestion: Release_2026. Choose Release Certificate (debug certificates are separate and not interchangeable). Upload the .csr generated earlier. When status becomes Active , download the .cer. Release certs valid 3 years, debug 180 days. Renewal uses the same .csr and .p12; only the cert and Profile need replacement. Warning : revoking a certificate is irreversible and invalidates all Profiles that used it.
3. Request Profile
Go to Profiles , click Add . Select the app (package name auto-filled). Profile type: Release , Debug , or Specified Device Release . For release: choose release certificate, no devices. For debug: choose debug certificate, must select devices . Certificate type and Profile type must match. If the app uses restricted permissions, enable them in the Profile; missing permissions cause runtime failures. Download the .p7b when active. Place .cer and .p7b in the project's sign directory alongside the local files.
Debug Devices: Register UDID
Debug Profiles require registered devices. In AGC Devices page, add device UDID (64 chars). Obtain via hdc: hdc shell bm get --udid For multiple devices:
hdc list targets
hdc -t <device-id> shell bm get --udidMax 100 devices per account; batch import supported. When adding a new device, update the debug Profile and re-download the .p7b to overwrite the project copy; otherwise the new device cannot install the app.
One Project, Two Signing Configs
Debug uses debug certificate; release uses release certificate. Both coexist via product flavors . Configure in File > Project Structure > Signing Configs , then edit build-profile.json5:
// build-profile.json5
{
"app": {
"signingConfigs": [
{
"name": "default",
"type": "HarmonyOS",
"material": {
"storeFile": "./sign/release.p12",
"storePassword": "******",
"keyAlias": "releaseKey",
"keyPassword": "******",
"certpath": "./sign/release.cer",
"profile": "./sign/release.p7b",
"signAlg": "SHA256withECDSA"
}
},
{
"name": "dev",
"type": "HarmonyOS",
"material": {
"storeFile": "./sign/debug.p12",
"storePassword": "******",
"keyAlias": "debugKey",
"keyPassword": "******",
"certpath": "./sign/debug.cer",
"profile": "./sign/debug.p7b",
"signAlg": "SHA256withECDSA"
}
}
],
"products": [
{ "name": "default", "signingConfig": "default" },
{ "name": "dev", "signingConfig": "dev" }
],
"modules": [
{
"name": "entry",
"srcPath": "./entry",
"targets": [
{ "name": "default", "applyToProducts": ["default", "dev"] }
]
}
]
}
}Details: passwords stored encrypted; .p12 is a private key — restrict repo access. Paths are relative to project root. Module targets must list both products. Daily debug: select dev product and Run. Release build: switch to default, run Build > Build APP(s) ; output .app in build/outputs/default. Do not interchange : debug-signed packages only run locally; release-signed packages only go to AGC. To test a release build on device, use invite or public test, not hdc install.
Upload Package: Automated Validity Check
In AGC Upload Software Package , upload the .app and choose usage scenario (test only or test + release). Automatic legality check returns three tiers:
Met : ready to submit.
Optimization Needed : submittable but may be flagged in review.
Failed : blocked; fix per hints.
Results show green checks per item. Optional Pre-launch Self-check (compatibility, stability, performance) does not block submission but recommended. Version numbers in AppScope/app.json5:
{
"app": {
"versionCode": 1000001,
"versionName": "1.0.1"
}
}versionNameis user-visible; versionCode is integer for system comparison. New version must exceed the live version's versionCode.
App Information and Assets
After package passes, fill store metadata. Text fields (description, one-liner, release notes) have character limits. Assets — first thing reviewers see — must meet exact specs for phone apps:
Icon: 216×216 or 1024×1024, square, PNG ≤ 3 MB.
Screenshots: 3–10 images; portrait 1080×1920, landscape 1920×1080; each ≤ 5 MB.
Video (optional): 1–3 clips, 15 s–2 min, ≤ 500 MB.
Orientation consistency: screenshots and video must match (all portrait or all landscape).
Use real-device captures (status bar, navigation bar, rounded corners visible) rather than stretched design mockups.
Compliance: Content Rating, Privacy, AI, Copyright
Separate compliance section; logic: declare what the app actually does.
Content Rating : questionnaire determines minimum age. Answer truthfully; mismatch triggers rejection.
Privacy Policy : mandatory. Either provide custom policy URLs or use Privacy Hosting (template-based, only for apps distributed in mainland China on phone/tablet/PC).
Privacy Description : explain purpose of each sensitive permission. Restricted permissions require a usage-scene video. Profile must also include the same permissions.
Privacy Labels : check data-collection scenarios actually used; do not check advertising if absent.
AI Feature Declaration : if app contains AI-generated content (text, image, audio, video, virtual scene, other), select "Involved" and upload AI labeling materials to Copyright Info > Authorization & Other Materials . Otherwise select "Not Involved".
Copyright Info : for mainland China phone apps, app copyright certificate or agent certificate required (JPG/PNG/BMP, ≤10 files, each ≤15 MB). Electronic copyright certificate (PDF ≤5 MB) optional. Authorization materials as ZIP (≤200 MB, max 3 directory levels, 200 images).
Submit, Rejection Handling, Upgrades
After signing, upload, metadata, and compliance are complete, click Submit for Review . Dialog reconfirms version number. If package supports more devices than declared in App Info, a prompt appears; can ignore without affecting review.
Common rejection reasons:
Certificate and Profile type mismatch.
Profile package name differs from project.
Screenshot specs (size, count, format) violated.
Missing privacy policy or privacy description/permission mismatch.
AI-generated content used but not declared.
Version upgrades only change versionName and versionCode in app.json5. Reuse same certificate and Profile; only replace when certificate expires.
Summary
Map the four files (p12, csr, cer, p7b) to their roles, separate debug and release via two products, then fill assets, rating, privacy, AI, and copyright in order. Once signing is configured correctly, each new version is just a version-number bump.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
