What to do if the WeChat mini program fails the review

Recently, many developers have devoted themselves to the development of WeChat mini programs, and these developers always need to face the last problem: how to pass the official WeChat review in an elegant manner. This article is based on a summary submitted for review a few days ago. There are some inappropriate things in the writing. Please correct me.

Problem Description

First, let’s look at the documentation on common rejection situations on the WeChat Mini Program platform. Since the mini program I submitted contained a "Share Group" button, the review failed. The reasons for failure are as follows:

3.2.1 There are inducing behaviors in the page content of the mini program, including but Not limited to inducing sharing, inducing adding, inducing following public accounts, inducing downloading, etc., programs that require users to share, add, follow or download before they can be operated, and contain copywriting, pictures, buttons, overlays, pop-ups that explicitly or implicitly indicate or imply user sharing. Mini programs such as windows, mini programs that induce users to share and spread through profit temptations, mini programs that use exaggerated words to coerce and induce users to share, and those that force or induce users to add mini programs will all be rejected;

Is the small program that you have worked so hard to develop aborted before it was even launched? It’s simply unbearable!

Solution

I once heard a sentence: "Since I can't move you, then I choose to let myself go." So, since we can't change the constraints of official norms, then avoid Conflict with him. So the solution is roughly as follows:

• The first step is to add a judgment mechanism to the entry file of the mini program to control the version of the mini program.

• The second step is to write a simple version to be submitted for review.

• The third step is to wait for the review to pass, and then switch back to the official version through the judgment mechanism set in the first step.

Next, let’s talk about how to operate it.

1. First, I created a QuickStart project, as shown below:

2. The next step is to create the entry file, which is index. Add a judgment mechanism to wxml to control the version of the mini program. The specific code is as follows:

   hello       获取头像昵称    {{userInfo.nickName}}    {{motto}}   

Then the next step is to set the version value in index.js. The specific code is as follows:

data: { motto: 'Hello World', userInfo: {}, hasUserInfo: false, canIUse: wx.canIUse('button.open-type.getUserInfo'), version: 0 }

The running result is as follows:

3. Seeing this, the second step of writing a simple version to be submitted for review has been completed. But this is only for testing. The actual version to be submitted for review should not be too simple. I suggest that you put in a simple version that you have made before.

4. Control version switching. It can be seen from the code that the version switching depends on the value of version. Therefore, a version field can be added to the interface of the version to be submitted for review to meet the requirement of dynamically switching versions. As long as the version to be submitted for review can be approved, change the version field to a non-0 number to switch back to the official version.

Conclusion

Although this method can be used to avoid review, it is still recommended that the mini programs developed are healthy and progressive, and everyone is responsible for jointly creating a green mini program environment haha.

Related recommendations:

Chart style function implementation method of WeChat mini program process progress

Detailed explanation of the life cycle of WeChat mini program

WeChat applet realizes the sharing of methods to dynamically set page titles

Detailed example of WeChat applet uploading pictures to the server

How to build a WeChat applet server locally