Four Checks Before Submitting for Review
A developer delivering their first Mini Program wrote this down: finished code does not mean it can go live; the review materials must be filled in item by item according to what the app actually does. The key to passing the first time is these four items:
1. Features complete and working: reviewers really do tap around. Empty pages, "coming soon," and buttons that do nothing are all rejection reasons.
2. Category matches: the category you pick must match what the Mini Program actually does. A to-do list picks "Tools → Productivity."
3. Privacy protection guidelines: in the admin console, declare which user information you use and what for.
4. No test content: test data, "test" buttons, and debug output from development all get removed.
How to Fill In the Privacy Protection Guidelines
In the Mini Program admin console: "Settings → User Privacy Protection Guidelines." There is only one principle: declare what you use, and nothing you do not.
The to-do list uses Cloud Development and only uses openid to separate data. No avatar or nickname, no location, no photo album. So declare only "processes the user's openid to distinguish user data." Declare one extra camera permission, and the reviewer will ask where you use it.
让 AI 帮你核对：
「读一遍整个项目代码，列出实际调用过的所有微信 API 里涉及用户信息或设备权限的（如 getUserProfile、chooseImage、getLocation、getStorage）。我要按这份清单填隐私保护指引，只填真实用到的。」Submit, Wait, Handle a Rejection; and the Assignment
DevTools "Upload" → admin console "Version Management" → Submit for review, filling in screenshots of the feature pages and a description. Review usually takes a few hours to a few days.
Rejection is not scary. The rejection notice states the reason; send it to the AI verbatim: "Review rejected, reason: (exact text). List what needs to change; I will confirm before you edit." Fix it and resubmit. Being rejected once or twice the first time is normal.
自测 · 学完检查一下
想真正动手做题、记进度、攒连胜？到互动课里练。
Xiao Zhou's to-do Mini Program has a "Settings" page containing only one line: "Feature under development." What should be done before submitting?
答案：Remove the page and its entry point from app.json; add it back when it is done
"Feature under development" is the classic rejection reason, and "coming soon" is the same thing. A fake feature, if discovered, counts as deceiving review. Lesson 3's "not this time" means here: if it is not finished, it should not appear.
The to-do list uses only the cloud database and local storage. What should go in the privacy protection guidelines?
答案：Declare only the openid used to distinguish user data; leave every other permission out
Over-declaring gets you asked to explain the purpose, and if you cannot, you are rejected. Declaring nothing contradicts the fact that you use openid. Copying someone else's saddles you with the permissions they use. Have the AI scan the code for real calls and fill it in from that list.
True or false: the more you declare in the privacy protection guidelines, the safer you are; users will not read it closely anyway.
答案：False
Reviewers read it closely. Declare the camera permission with no camera call in the code and it is judged as inaccurate information. The guidelines exist to inform truthfully, not as a disclaimer.
Review was rejected with the reason "the Mini Program's category does not match its actual features." What is the right response?
答案：Re-select the category based on the actual features (a to-do list goes under Tools) and resubmit
The category is a label describing the features; if the label is wrong, fix the label, not the features. A new AppID means starting from scratch; resubmitting unchanged bets luck against rules, and the rules do not change.
Before submitting, which check is the easiest to overlook and the most likely to cause a rejection?
答案：Test data and debug buttons left over from development were not removed
Things like "test," "test to-do 1," and "print log" become invisible to the developer, but a reviewer sees them and immediately concludes "feature unfinished." Name, icon corners, and comments are not review criteria. Before submitting, have the AI scan the project and list every leftover test artifact.