Skip to content

Submission and Release: A Pitfall-Avoidance Guide to WeChat Review Rules ​

Search "WeChat Mini Program review" and the top results are either "guaranteed pass" ads from proxy agencies or help posts saying "rejected again." In fact, all the review rules are written in the official WeChat documentation: what to do at each step, what reviewers look at, and what situations are guaranteed rejections — all explicitly stated. In this lesson, you'll submit the app validated in the trial version for review and release it as the official version — no mysticism, just the official process, plus clearing out the most common rejection pitfalls in advance.

This is Lesson 4 of Route B (Building a Mini Program). At the end of B3, you had built a 14-day trial version and decided to run it long-term; this lesson turns the "validated thing" into an "official version everyone can use." The official version is the only one of the three tiers that requires WeChat review — for rules on review, filing, and the like, WeChat has the final say; WorkBuddy can only assist, not handle compliance for you.

What You'll Be Able to Do After This Lesson ​

  • Explain the complete chain of WeChat Mini Program review and release: upload code → development version → submit for review → after approval, manually click release
  • Submit the validated app as the official version in WorkBuddy, checking the three settings before release: filing, user privacy protection guidelines, and UGC declaration
  • Do a round of pre-submission self-check per the official operating guidelines: name, core features, completeness, content safety, privacy, payments
  • Master the test account rules: know why the first submission may be rejected and how to leave an entry point for reviewers on the second submission
  • Release and go live after approval, and know that updating the official version requires going through review again

Your Current Predicament ​

  • "My trial version is about to expire and I want to switch to the official version, but searching 'WeChat Mini Program review' turns up nothing but proxy agency ads"
  • "I hear reviews get rejected all the time — what do reviewers actually look at? Nobody can say"
  • "I don't understand terms like filing and privacy protection guidelines at all, and I'm afraid of getting stuck on the forms"

When to Use This Technique ​

When you need to:

  • Turn an app validated in the trial/experience version into an official version that all WeChat users can open
  • Make the mini program searchable and able to run long-term, instead of being automatically deregistered after 14 days

And you don't want to:

  • Go back and forth with review rejections — in WorkBuddy, each mini program can only submit 3 official-version reviews per week
  • Step on red lines that are spelled out clearly in the official operating guidelines

🎒 Preparation Before Starting ​

  • Completed B3 Build a Mini Program with WorkBuddy: the app has been generated and the core flow has been tested on a real device
  • Have your own WeChat Mini Program account (the one registered in B2), and have completed "Bind an Existing Mini Program Account" in the WorkBuddy share panel
  • The admin's WeChat is at hand: review result notifications are sent to the admin's WeChat
  • A cup of water ☕

Core Idea ​

WeChat Mini Program review isn't about code quality — it's about compliance. No matter how beautiful the AI-generated code is, a violating name, incomplete features, or overreaching privacy will still get rejected. First understand the official version system, and the process becomes smooth:

VersionWho Uses ItOfficial Definition
Development versionDevelopersCode uploaded from the tool; only the latest copy is kept per person and can be deleted
Experience versionExperience membersOne copy selected from the development versions and set as the experience version, for pre-launch acceptance testing
Version under reviewWeChat reviewersOnly one copy of code can be under review at a time
Online versionAll usersThe version used by all users after review approval and release

The mini program release process has four steps in total: preview → upload code → submit for review → release. Two key insights:

  1. Review approval ≠ automatic launch. Official statement: once the code review is approved, the developer must manually click release for the mini program to go live and provide service.
  2. Rejections aren't random. Commercial wording in the name, core features not on the home page, incomplete test versions, missing content safety mechanisms — the official operating guidelines spell out all the most common rejection points, so you can self-check in advance.

On the WorkBuddy managed path, code upload, review submission, and version release are handled with assistance by WorkBuddy as a WeChat third-party service provider; but account registration, verification, filing, and review rules follow WeChat's official requirements — the rules covered in this lesson apply to both paths.

Follow Along ​

Five steps in total: self-check → three settings → submit for review → test account → release. The example continues with the "Reading List" from B3.

Step 1: Pre-submission self-check — go through the most common WeChat Mini Program rejection points ​

Why: Review rejections aren't random; the official operating guidelines spell out the high-frequency rejection reasons. Moreover, in WorkBuddy each mini program can only submit 3 official-version reviews per week, and during review you can't submit new official-version updates — so passing on the first try is extremely worthwhile.

Check item by item:

Check ItemOfficial Requirement
Name/DescriptionMust not contain commercial wording like "free," "super cheap," or "clearance"; must not stuff keywords; must not ride on the "WeChat" brand; must not use banned advertising-law terms like "national-level"
Core featuresMust be reflected on the mini program home page; features must not be too simple
CompletenessMust be a finished product: it can open and run, must not be a test version, and has no serious bugs
Content securityIf the app has user-generated content or lottery-type features, you must call the content security detection API to check text/images
PrivacyYou must obtain user consent before collecting data; you may not force users to enter personal information such as a phone number in order to use a feature
PaymentsVirtual goods (feature unlocks, subscription content, tips) must use the Mini Program in-app virtual payment; you may not direct users to an app, Official Account, or H5 to complete payment
  • Go through all six self-check items one by one; if any issues are found, go back to the WorkBuddy conversation to fix them first

You should see: every item matches your own Mini Program; the item you can't clearly explain is the one the reviewer will zero in on.

Step 2: Check the three settings of ICP filing, privacy protection guidelines, and UGC declaration ​

Why: These three are compliance settings that the official version cannot get around — the trial version doesn't need to worry about them, but if the official version is missing even one, it may be rejected or have access affected.

In the WorkBuddy share panel, click "Mini Program Settings" and check in turn:

SettingHow to handle
Mini Program ICP filingMini Programs in mainland China should complete ICP filing; if filing is not completed, WeChat may restrict access for new users or suspend the service
User privacy protection guidelinesIf user personal information is processed, fill in the information types, collection purposes, change notification method, and the developer's contact phone number and email according to the actual situation
UGC information security declarationIf the submission category includes user-generated content scenarios such as community, forum, notes, or Q&A, fill it in on the WeChat Official Accounts Platform under "Management > Account Settings > Basic Settings > Service Content Declaration"

You should see: all three settings match your Mini Program's actual situation — the reading list uses WeChat login, so the privacy guidelines must clearly state which user information will be processed.

💡 Where do I file for ICP registration?

Mini Program ICP filing follows WeChat's official filing operation guide — there is an entry point in the ICP filing section of "Mini Program Settings." Like review, filing is a compliance requirement of the WeChat platform, and the WorkBuddy documentation clearly states: account registration, verification, filing, and review rules all follow WeChat's official standards.

Step 3: Submit the WeChat Mini Program for review ​

Why: The official version is for public release and needs to be submitted for WeChat review — this is the only one of the three tiers that requires review; neither the trial version nor the experience version does.

Option A (recommended): WorkBuddy hosted path ​

  1. In the share panel, check "Official Version"
  2. Click "Publish" to submit for WeChat review
  3. After submitting, check the review progress in the share panel

You should see: the share panel shows the review progress. When the review has a result: if it passes, the administrator's WeChat receives a notification (detailed in step 5); if it fails, the share panel displays the complete review reasons returned by WeChat.

Option B: WeChat Official Accounts Platform backend ​

The prerequisite is that the code has been uploaded — use the "Upload" button in the top action bar of WeChat DevTools, filling in the version number and project notes (these two fields are for the administrator to check versions). Then:

Log in to the WeChat Official Accounts Platform Mini Program → Version Management → Development Version (the uploaded code is here) → click "Submit for Review" and fill in the relevant information as prompted by the page.

You should see: after submission, the "Review Version" module on the Development Management page shows the review progress.

⚠️ Two frequency limits

Under the WorkBuddy hosted path, you cannot submit a new official version update while an official version review is in progress; each WeChat Mini Program can submit official version reviews 3 times per week, with the remaining count as shown in the panel. The official reminder also says: please test the version thoroughly before submitting for review — too many failed reviews may affect subsequent timing.

Step 4: Leave a test account for the reviewer and fill in the review information properly ​

Why: The reviewer must be able to experience all your features — a review stuck at the login page will most likely be rejected.

Two official rules — knowing them in advance keeps you calm:

  • Test account: If the Mini Program involves account relationships or paid content, you must provide a test account (username + password) to ensure the reviewer can experience all features. The official mechanism is: for Mini Programs that require a test account to complete the review experience, the first review submission will be rejected, and the entry for providing a test account will open on the second submission — this is not making things difficult, it's process design: after the first rejection, just fill in the test account on the second submission.
  • Feature pages: The submission form in the official backend requires configuring feature pages — fill in the categories and tags of important business pages, with no more than 5 groups of important business pages. Pick the pages that best showcase the core features, and don't exceed 5 groups.

You should see: you have prepared a test account in advance (username + password) and know it needs to be filled in on the second submission.

Step 5: After the review passes, click "Publish" to go live officially ​

Why: Passing the review does not mean going live automatically — the official documentation states: after the code review passes, the developer must manually click publish for the Mini Program to be released online and provide service.

  • Official backend path: The administrator's WeChat receives a notification that the Mini Program passed review; log in to Version Management - Review Version and click "Publish." Publishing has two modes: full release (all users get the new version immediately; ordinary Mini Programs choose this) and phased release (also called gray release, letting some users get the new version in stages, suitable for apps with large user bases to control risk)
  • WorkBuddy hosted path: Version release is handled with the assistance of the hosted process — after the review passes and the release is completed, it can be accessed and shared via the official version Mini Program code

You should see: the official version Mini Program code can be opened in any WeChat — no longer "only users with experience permission can access," and no 14-day validity period.

  • Release completed; scan the code with a phone that has no experience permission and it opens normally

Checkpoint ✅ ​

  • All six self-check items (name, core features, completeness, content security, privacy, payments) gone through one by one
  • The three settings of ICP filing, user privacy protection guidelines, and UGC declaration match the actual situation
  • After submitting for review, review progress is visible in the share panel or the Development Management page
  • For Mini Programs with account relationships or paid content, the test account is prepared (username + password)
  • After the review passes, publishing is completed and any user can scan the code to open it

Pitfall reminders ​

❌ Sitting back and waiting to go live after the review passes ​

Symptom: You receive the pass notification, but the Mini Program still can't be found in search and new users can't open it by scanning the code.

Cause: Passing the review ≠ going live automatically; the official requirement is that the developer must manually click publish for the Mini Program to be released online.

Correct approach: Go click publish immediately after receiving the notification — in the official backend it's under "Version Management - Review Version"; on the WorkBuddy path, confirm the release is completed before distributing the Mini Program code.

❌ Resubmitting as-is after rejection and hoping for luck ​

Symptom: After being rejected, you change nothing and immediately submit again, hoping a different reviewer lets it through.

Cause: The official statement says "too many failed reviews may affect subsequent timing"; in WorkBuddy, each Mini Program only has 3 official version review submissions per week, and you can't submit new official version updates while a review is in progress.

Correct approach: The share panel contains the complete review reasons returned by WeChat — fix the issues based on the reasons, release an experience version for real-device verification first, then resubmit the official version for review. For item-by-item fixes of high-frequency rejection reasons, see B5 What to do if the review is rejected.

❌ Stuffing "free" or "clearance" into the name and description ​

Symptom: The name contains words like "free buffet" or "super cheap women's clothing" and is rejected outright.

Cause: The operating guidelines clearly state: the name must not contain commercial language, must not pile up keywords, must not ride on the "WeChat" brand (e.g., "WeChat Assistant"), and must not use advertising-law-prohibited terms such as "national-level" or "top-level."

Correct approach: Just make the name clearly state "what you do"; spend your effort making the core features visible on the home page.

❌ Rushing to distribute before ICP filing is completed ​

Symptom: The review passes and the release succeeds, but new users scanning the code are restricted from access, or see "Mini Program suspended."

Cause: Mini Programs in mainland China should complete ICP filing; if filing is not completed, WeChat may restrict access for new users or suspend the service.

Correct approach: Complete the filing before release. If you've already encountered "suspended," go to the WeChat Official Accounts Platform "Management > Account Settings > Account Information," click "Resume Service" in the "Service Suspended" section, and after resuming, scan the code again to confirm.

Advanced tips (optional) ​

🔧 How long does the review take? (optional) ​

The official documentation makes no unified commitment on review timelines — anyone promising you "guaranteed approval in X days" is most likely using agent sales talk. After submitting, check progress in the sharing panel (the WorkBuddy path) or in the "Review Versions" module of the development management page (official backend); review results will be notified via the administrator's WeChat.

🔧 Updates and Offline Removal After Launch (Optional) ​

After you modify the app, the online version will not sync automatically: click "Update" in the sharing panel; updating the official version requires resubmitting for WeChat review. Until the new version passes review and publishing is completed, users will continue using the currently live version. To stop the service, only the official version supports "going offline" — once offline, the official mini program will no longer be accessible.

🚀 Review Is Not Unique to Mini Programs ​

Publishing a Chrome extension to the app store also requires passing review: the complete workflow of registering as a developer, packaging, and submitting for review is covered in C6 Publishing to the Chrome Web Store. Build the habit of "self-checking before submission" with mini programs first, and it will serve you well on any other platform.

Lesson Summary ​

✅ WeChat mini program review checks compliance, not code quality. You have completed the last mile from verification to launch:

  • Pipeline: upload code → development version → submit for review → manually click publish after approval
  • Self-check: name, core features, completeness, content safety, privacy, payments — defuse six items in advance
  • Settings: ICP filing, user privacy protection guidelines, UGC declaration — three compliance settings for the production version
  • Submit for review: WorkBuddy select "official version" to publish, or submit via version management in the official backend — the WorkBuddy path gets 3 chances per week
  • Publish: full rollout or gray release; the production mini program QR code can be scanned by anyone
StageWhat You DidKey Points
Self-checkGo through the six high-frequency rejection points one by oneRejections are not random; all the rules are in the operations guidelines
SettingsICP filing + privacy guidelines + UGC declarationMissing any one item may lead to rejection or affect access
Submit for reviewSubmit for WeChat mini program reviewWorkBuddy: no new production version can be submitted during review, 3 times per week
ReviewPrepare a test account and monitor review progressAfter the first rejection, open the test account entry for the second submission
PublishManually click publish for full rolloutApproval ≠ automatic launch

Next Lesson Preview ​

A review rejection is not the end — it's a remediation checklist. In the next lesson B5 What to Do When Review Is Rejected: High-Frequency Rejection Reasons and Remediation, you will learn:

  • A point-by-point breakdown of high-frequency rejection reasons: induced sharing, virtual payments, category mismatch
  • The cost of fighting review: escalating cumulative penalties, up to permanent removal
  • How to read rejection notices, remediate by cause, and resubmit
  • The process and boundaries of appeals

If you get rejected, don't panic — go to B5 →

gaodong.aiAboutPrivacyContact

Independent tutorials, not affiliated with any product mentioned. Product names and trademarks belong to their owners. Check official pages for prices and policies.