Skip to content

Configuration, Review, and Release ​

Build the WeChat Mini Program with the AppId, service domains, and authorization settings for the deployment. Verify compilation and a trial build in WeChat before review and release. H5 can preview shared screens, but it cannot replace acceptance in WeChat.

1. Before You Start ​

ItemDetails
Entry pointThe mobile project in HBuilderX, WeChat DevTools, and the Mini Program administration console
PermissionsDevelopment, trial, review, or release permissions for the relevant AppId, plus a test account and device
What to prepareMini Program ID, test and production API and MQTT endpoints, privacy settings, notification templates, and submission version

2. Configure and Build ​

  1. Verify the WeChat AppId and privacy-related APIs in manifest.json, then point env.config.uts at the target API and MQTT service. Check development, trial, and production builds separately so a production build does not point at test services.
  2. In the administration console, verify request and WebSocket domains, certificates, and enabled capabilities. Backend WeChat login settings and alert templates must match the same AppId.
  3. Build the WeChat target in HBuilderX and import its output into WeChat DevTools. Confirm the AppId and main and subpackages, review package analysis and compile warnings, and use the checks reported by DevTools and the administration console.

3. Trial, Review, and Release ​

  1. Open the trial build in WeChat using an account with trial access. Verify first-time authorization, login, device queries, readings, and empty states. Verify scanning, provisioning, and command feedback separately on authorized devices. Do not enable capabilities that the test does not need.
  2. Follow Alerts, Notifications, and Permissions to check templates, user subscription, and server delivery. Opening the page in DevTools does not prove that a physical device receives notifications.
  3. Upload the accepted build and provide version and review information requested in the administration console. After approval, an authorized operator can release it. Then recheck the environment, login, and key device workflows with a regular user account.

3.1. Record Acceptance Results for Each Release Stage ​

StageMinimum checksIf a check fails
Development buildCheck AppId, source commit, target environment, and compile results. Observe requests with domain validation enabledUse the failed request to distinguish domain, certificate, authorization, and API issues
WeChat trial buildOn a physical device, follow a regular user's workflow for login, device viewing, and authorization. Record physical-device results for the features in scopeVerify that the trial build and DevTools use the same build before retesting
Review and releaseVerify that the candidate points to the intended release environment. Record the submission version, trial results, and a viable rollback planAfter changing settings or rebuilding, repeat the affected checks. Do not carry over results from the previous package

4. Verify the Result ​

ProblemWhat to check first
DevTools works but the trial build cannot make requestsTrial permissions, AppId, actual service domains, certificates, and build environment
The app remains unavailable after login or authorizationBackend Mini Program settings, account binding, and the API response
Alerts are visible but no subscription notification arrivesThe AppId owning the template, user authorization, and server delivery

Do not accept a release based on a test with domain validation disabled in DevTools. For client operations, see Login Authorization and Binding.