wx.getLocation interface application

1. Reasons for rejection: The usage scenario of the applet interface you described does not currently meet the requirements for accessing wx.getLocation (access to the current geographic location and speed interface open range)

Solution: 1. First check whether the category of the applet meets the open range of wx.getLocation

(WeChat Public Platform--Homepage--Small Program Category)

If the category also matches, it depends on the usage scenario. If the audit thinks that chooseLocation can be used instead, it will not be approved. For example, if an e-commerce platform user chooses the delivery address, chooseLocation can be used instead. In this case, the audit will not be accepted. will pass.

Common getLocation requirements: such as takeaway/errands/punching, this kind of demand cannot be replaced by chooseLocation, the application description is clearly written, and major changes can be passed

 2. Reason for failure: The reason/auxiliary picture/webpage/video content provided by you cannot confirm the usage scenario of the application interface

In this case, it is your description that cannot clearly show your scene

Solution: In the description, write your usage scenario as concisely and clearly as possible. Where the interface is used, you must show it. Do not summarize it in one sentence, otherwise there is a high probability of rejection

In terms of pictures, you can add some text explanations on the pictures, so that the review can be clearly understood

Put the content of my application for reference

 Just describe it according to your needs

Guess you like

Origin blog.csdn.net/m0_60317712/article/details/128497406