How to Submit Your App on Huawei AppGallery

To submit app on Huawei AppGallery, you work through AppGallery Connect, Huawei’s console for app records, services, testing, packages, releases, and review. The upload itself is only one part. Publishers also need verified identity, a signed Android package, accurate listing material, privacy and category declarations, reviewer access, and device testing that does not assume Google Mobile Services are present.

This guide reflects Huawei’s public documentation available in July 2026. Console fields, supported countries, package options, and qualifications can change. Check AppGallery Connect before each release, and never treat a completed checklist as an acceptance guarantee.

If you are starting from a website, first create and test a signed build with the website-to-Android conversion guide. Then use this guide for Huawei-specific distribution and Google-service dependency testing.

Verify Your Huawei Developer Account and Release Markets

Start at HUAWEI Developers and open AppGallery Connect. Register with a Huawei ID controlled by the app owner, then complete developer identity verification.

Huawei distinguishes individual and enterprise publishers, and available options depend on country or region. Select the legal owner that will hold app rights, receive notices, manage revenue, and sign future agreements. A company app should not remain indefinitely under a contractor’s personal identity.

Prepare the current documents requested by the portal. They may include:

• Government identity for an individual or authorized administrator
• Company registration and business address
• Authorization for the console operator
• Bank and tax information for paid products
• Trademark or app-ownership evidence
• Support website and public privacy policy
• Category qualifications for regulated services

Huawei’s official AppGallery Connect preparation guidance states that publishers must register as Huawei developers and complete identity verification. The portal is the final source for accepted document types in your country.

Before planning a worldwide launch, verify three separate things: your account can enroll, AppGallery distribution is offered in the intended countries, and your product is lawful and operational there. AppGallery reach, Huawei device sales, HMS Core service coverage, and in-app-purchase coverage are not interchangeable country lists.

Read the agreements presented in your account. Free publication does not remove tax, privacy, export, consumer, or local-content obligations. Category and country rules can require more evidence than general account verification.

With the publisher identity established, create the app project carefully because package and signing choices affect every release.

Create the App in AppGallery Connect and Configure Signing

In AppGallery Connect, create a project if needed, then add an Android app. Enter the exact package name used by the production build. Treat that application ID as permanent. It connects releases, APIs, deep links, analytics, push configuration, and signing fingerprints.

Huawei services commonly use the app record’s signing certificate fingerprint to verify authenticity. Huawei’s configuration documentation directs developers to add a SHA-256 certificate fingerprint under project settings. Generate it from the release certificate, not a debug keystore.

Keep a controlled record of:

• Keystore file and backup locations
• Alias and protected passwords
• SHA-256, SHA-1, and other required fingerprints
• Package name
• Version-name and version-code history
• People authorized to sign releases

Losing signing continuity can prevent normal updates. If WebInto.app builds and signs the package, confirm how the project retains its keystore and how your business can recover access. The SHA-1 and SHA-256 guide covers certificate extraction concepts even though menu paths differ by platform.

If you integrate HMS Core or AppGallery Connect services, download the current configuration file and follow that service’s official setup instructions. Do not add Huawei SDKs merely to pass review. Add only services the app uses, then update privacy disclosures for their data processing.

Choose whether one package serves several stores or Huawei receives a distinct edition. A shared package and signature simplify code and may support compatible update behavior. A separate package can isolate Huawei-specific features but creates another app identity, deep-link setup, analytics property, notification configuration, and support matrix.

Maintain version codes across channels. Each AppGallery update needs a higher code than its preceding release. If users can encounter the same signed package from multiple stores, coordinate codes to avoid unexpected downgrades or cross-store replacement.

Before uploading, verify that API keys and OAuth clients recognize the release certificate. A login flow that worked in a debug build can fail after production signing.

The AppGallery Connect record now matches your cryptographic identity. Next, make the package work on real Huawei devices.

Build the Release Package and Test Google-Service Dependencies

Huawei documentation exposes release paths for signed APK and App Bundle packages. Use the package format offered for your Android app and target regions in the current AppGallery Connect interface. Do not confuse a HarmonyOS APP package with an Android APK or App Bundle. Upload the format that matches the application type you created.

A production release should have:

• Stable package name and increasing version code
• Valid release signature
• 64-bit native support where libraries are included
• Current Android compatibility
• Production endpoints and HTTPS
• No debug flags, test keys, or sample accounts
• Only permissions needed for visible functions

The most important Huawei-specific test is not simply “does the APK install?” It is “does every core journey work on a device without Google Mobile Services?”

Audit dependencies for:

• Google Sign-In
• Firebase Cloud Messaging
• Google Maps or Places
• Google Play Billing
• Play Integrity or SafetyNet-era checks
• Google location APIs
• Google-hosted reCAPTCHA
• Play Asset Delivery or dynamic features
• Links that force users into Google Play
• Firebase services that require unavailable components

Some Firebase products can function without the Play Store, while others depend on Google Play services or configuration not present on many Huawei devices. Do not classify all Firebase use as broken or all of it as compatible. Test each SDK and user journey on the exact device environment.

Use one Huawei phone without GMS as a clean test device. Avoid a device where unofficial Google components were added, because it hides real customer failures. Test clean install, first launch, account creation, login, password reset, notifications, maps, location, payments, camera, file selection, deep links, background behavior, offline recovery, and update installation.

Create explicit fallbacks:

• Offer email or phone login when Google Sign-In is unavailable.
• Use HMS Push Kit or another supported design if FCM cannot deliver.
• Provide a compatible map implementation or functional non-map alternative.
• Use an approved payment route for the selected AppGallery market.
• Replace Google Play links with neutral web or AppGallery links.
• Avoid blocking startup on a Google-service availability check.

For WebView apps, inspect the website too. A “Continue with Google” button may be the only login route. Embedded maps, reCAPTCHA, Google-hosted fonts, payment redirects, and notification bridges can fail independently of the Android shell. Test from the target country and network.

Huawei’s open-testing FAQ discusses GMS/HMS-related availability in testing. Use AppGallery Connect testing tools, but rely on device evidence rather than a broad compatibility label.

When the release package works without hidden GMS assumptions, prepare the public listing and review evidence.

Complete Listing, Privacy, and Qualification Information

Open the app’s distribution or release area in AppGallery Connect and complete app information for the default language. Add localized listings only for countries where the service, support, legal terms, and product content are ready.

Prepare:

• Public app name and concise introduction
• Full description based on actual functions
• App icon and screenshots from the submitted build
• Category and age information
• Support email and website
• Public privacy-policy URL
• Pricing, ads, and purchase disclosures
• Copyright, trademark, or category qualifications
• Release notes for updates

Screenshots should show real UI. Do not use images from a Google Play edition if the AppGallery build replaces Google login, maps, or payments with different flows. The listing must set expectations for the package reviewers and customers actually receive.

Create a privacy inventory for native code, embedded SDKs, and website content. Include account data, analytics, crash reports, push tokens, location, camera, microphone, files, cookies, advertising identifiers, payment providers, retention, sharing, deletion, and contact information.

The privacy policy, permission prompts, console declarations, and package scan should agree. Common failures include requesting location without disclosure, declaring no ads while an ad SDK is active, omitting account deletion, or failing to name third-party services.

If your app requires login, provide a stable test account and clear steps. Huawei’s release guidelines state that test credentials should be provided when authentication is required. Use safe sample data and remove one-time barriers where possible. Reviewers should not need to pay or provide a real identity to inspect basic features.

Upload qualifications requested for categories such as finance, health, government, news, children’s services, gaming, or user-generated content. Requirements can vary by target country. An app accepted in one region may need different evidence elsewhere.

Once listings and disclosures are complete, use testing and package validation before asking for formal release.

Upload, Validate, and Test Through AppGallery Connect

Upload the signed package through the current package-management or version-information workflow. Huawei’s release documentation says AppGallery Connect performs a basic validity check when a package is uploaded. Resolve reported errors before selecting the package for release.

Inspect parsed information:

• Application ID matches the app record.
• Version code is higher than the prior release.
• Certificate is the expected release certificate.
• Architectures and device requirements are intentional.
• Permissions match your inventory.
• Package type matches the Android release workflow.

Do not dismiss warnings without understanding them. A required hardware feature can remove many devices. An obsolete SDK can introduce privacy or compatibility problems. A signature mismatch can break APIs even when installation succeeds.

Use AppGallery Connect’s available testing channel for the exact uploaded build. Invite internal staff or representative users in supported regions. Test installation through Huawei’s distribution link rather than only sideloading a local APK.

Run this release rehearsal:

1. Install on a factory-standard non-GMS Huawei phone.
2. Deny every permission once, then grant it in context.
3. Complete all sign-in options, including account recovery.
4. Receive a push notification after background restriction.
5. Exercise maps, payments, location, and file workflows.
6. Follow privacy, support, and account-deletion links.
7. Test offline and weak-network recovery.
8. Upgrade from the currently public version without data loss.
9. Verify the app does not redirect to Google Play for mandatory steps.

Imagine Nadia, who operates a city-events website. Her first package installs on a Huawei phone, but login offers only Google Sign-In and event directions open Google Maps. She does not submit it. She adds email login, a compatible map fallback, and AppGallery-aware links, then tests push and deep links through the uploaded test release.

Nadia also updates screenshots because the Huawei build has a different login screen. Her reviewer account opens a sample city with events already loaded. This is a realistic compatibility review, not a claim that replacing every Google service is always required.

When package validation and representative testing pass, configure the formal release conservatively.

Submit for Review, Select Regions, and Manage Release

Choose countries only where AppGallery Connect permits distribution and your app can legally and operationally serve users. Confirm translations, support hours, content rights, payments, privacy terms, and Huawei-service availability for each region. “Worldwide” in marketing does not override live portal options or local law.

Set the release time offered by AppGallery Connect. Huawei’s release guidelines describe release after approval or at a specified time. Build schedule buffer for questions or rejection.

Before submitting, confirm:

• Developer verification is active.
• Correct package passed validity checks.
• Signing and version records match.
• Store listing reflects the Huawei build.
• Privacy and permission declarations are consistent.
• GMS-dependent journeys have been tested and handled.
• Reviewer credentials work.
• Qualifications are current.
• Countries and devices are intentional.

Submit for review and monitor Version information, console messages, and registered email. Review duration varies with account, category, region, package findings, and documentation. No publisher can guarantee acceptance or a fixed publication date.

If rejected, read the complete review report. Reproduce technical issues on a non-GMS Huawei device. Correct the relevant package, listing, privacy statement, qualification, or reviewer instruction. Upload a higher version code if the binary changes, and explain the exact fix in review notes.

After approval, verify the live listing from a supported Huawei device in an initial country. Check developer name, screenshots, search, direct link, install, login, notifications, payment, privacy links, and updates. Regional indexing can vary, so use the direct AppGallery URL in launch communication.

For future updates, preserve package and signing continuity, increase the version code, rerun non-GMS dependency tests, revise SDK disclosures, and test update installation. Maintain a channel matrix for AppGallery, Google Play, Samsung, and other stores, especially when features differ.

Conclusion

To submit app on Huawei AppGallery, verify the publisher account and regions, create the Android app in AppGallery Connect, configure production signing fingerprints, upload a valid APK or supported App Bundle, and test every core journey on a Huawei device without Google Mobile Services.

Accurate listing material, privacy disclosures, reviewer access, qualifications, and regional settings are as important as the package. Begin with AppGallery Connect, use Huawei’s live documentation for current fields, and treat non-GMS testing as release-critical rather than optional.

FAQ

Does Huawei AppGallery accept APK and App Bundle files?

Huawei documents Android release workflows for APK and App Bundle packages. The formats shown can depend on app type, region, and current console. Use the option offered for your Android app, and do not confuse it with a HarmonyOS APP package.

Must I replace every Google service with HMS Core?

Not automatically. You must test each dependency on a standard Huawei device without GMS. Replace or provide fallbacks for any Google-dependent function that blocks core use, such as sign-in, maps, push, payments, or mandatory Play Store links.

What is the SHA-256 certificate fingerprint used for?

It lets AppGallery Connect and Huawei services verify the app’s signing identity. Add the production certificate fingerprint, not only a debug fingerprint, and keep the signing keystore protected for future updates.

How long does AppGallery review take?

There is no guaranteed duration for every app. First releases, regulated categories, incomplete qualifications, privacy inconsistencies, or failed reviewer access can extend review. Use the status and report in AppGallery Connect.

Can a website wrapper be published on AppGallery?

It may be eligible if it meets current quality and policy rules, but installation alone is not enough. Test login, notifications, maps, payments, external links, permissions, and offline behavior without GMS, and disclose all website and SDK data processing.