跪拜 Guibai
← All articles
HarmonyOS · Android · iOS

HarmonyOS Certificate Cap: Reuse One Signing Certificate Across Unlimited Apps

By 程序员一鸣 ·
Read original on juejin.cn ↗ Google Translate ↗ Alt translation

Shipping a fourth HarmonyOS app no longer requires a second developer account or re-running real-name verification; the signing model separates reusable identity from per-app declarations, so the practical ceiling is only Profile administration.

Summary

HarmonyOS developer accounts are limited to three debug and three release certificates, which stops a fourth app from being signed and published. The cap is not on app count: certificates are reusable identity files, only the Profile that declares package name, permissions, and device info is tied to a specific app. So a fourth or fiftieth app can reuse the same .cer and .p12, and needs only a fresh .p7b Profile. In DevEco Studio, point the new app's build-profile.json5 at the existing key and certificate, swap in the new Profile, and upload.

Pitfalls remain. Deleting or revoking a certificate invalidates every Profile that references it, breaking updates for all published apps with error 1005. A single app can have up to 100 Profiles, so that is rarely the bottleneck. Release certificates last three years for real-name developers; renew before pushing an update or the signed package is rejected. Auto-signing in DevEco Studio hits the same limit and needs manual cleanup or manual signing with a reused certificate.

Takeaways
— Each HarmonyOS developer account can hold at most 3 debug and 3 release certificates.
— Certificates are not bound to an app package name and can be reused across multiple apps.
— Profile (.p7b) files are bound to one specific app package name; each app requires its own Profile.
— To publish a 4th app, reuse an existing certificate and apply for a new Profile only.
— Deleting or revoking a certificate invalidates all associated Profiles, breaking version uploads for existing apps with error code 1005.
— A single app can have up to 100 Profile files, well above the certificate limit.
— Release certificates for real-name developers are valid for 3 years; expired certificates cause update uploads to fail.
— DevEco Studio auto-signing also fails when the certificate quota is reached; clean up unused certificates or switch to manual signing.
— In the 4th app's build-profile.json5, signingConfigs can point to the same .p12 and .cer, only the Profile file needs replacing.
Conclusions

Reusing one certificate concentrates signing authority across multiple apps, so a single key compromise or revocation takes down every app using it, not just one.

The three-certificate cap forces developers to treat certificates as account-level identity rather than per-app artifacts, which aligns with how Android and iOS signing already separate identity from per-app configuration.

The 100-Profile ceiling makes the real operational bottleneck administrative: every new app adds a Profile to create, track, and renew, so scaling to many apps is mostly a bookkeeping exercise.

Concepts & terms
Release certificate (.cer)
A file issued by the HarmonyOS developer center that proves a developer's identity for publishing applications; it is not bound to a specific app and can be reused across multiple apps.
Profile (.p7b)
A per-app signing declaration that binds an app's package name, permissions, and device restrictions to a certificate. Each app needs its own Profile, even when sharing the same certificate.
KeyStore file (.p12)
A password-protected file that holds the private key used for signing. It is not tied to a specific app and can be shared across all apps signed by the same developer.
Source: juejin.cn ↗ Google Translate ↗ Backup ↗