Mini Program
取消
Development
中文
EN
取消
  • Guide

    • # Mobile Number Billing Error Troubleshooting Guide

    Using the Mobile Number Quick Verification Component / In the process of real-time verification of the mobile phone number, if there is an error in the number of official billing times and the number of Mini Program reports, you can refer to this article for investigation.

    # 1. Check the Mini Program report statistical caliber

    It is recommended to use the Mini Program officially provided We Analysis report If you use other methods of escalation, please make sure that the escalation network requests within the statistical time range are normal, and if there is correct retry logic when the escalation fails.
    In addition, please pay attention to whether other anomalies may occur in the Mini Program during the period from obtaining the mobile phone number to initiating the report, causing the report to be interrupted and causing statistical errors.
    use We The specific method of analyzing and reporting the mobile phone number of the Mini Program is as follows:

    • Get into[ we Analysis platform](https://wedata.weixin.qq .com /mp2/Login)。
    • Under [Data Management-Release Management], according to their own business needs, create corresponding buried point reported events.
    • In the Mini Program logic, the corresponding buried point is reported to the Mini Program mobile phone number authorization callback event.
    • After the Mini Program is released, go to [Data Analysis-Behavioral Analysis-Event Analysis] to create a corresponding event analysis.
    • Open the Data Kanban to view the curve.

    Detailed operations can be found in[Event Analysis Documentation](https://developers.weixin.qq.com/miniprogram/analysis/Wedata /DataAnalysis.html) 。
    If the reporting statistical caliber is confirmed to be correct, it can enter the 2 Step.

    # 2. Check Mini Program mobile number button logic

    Check the phone number authorization button logic, trigger bindgetphonenumber Immediately after the callback, whether the phone number button component is hidden, or set to disabled stateIf not, the user may continue to click the button, resulting in additional mobile number authorization and billing.
    If confirmed, you can enter No. 3 Step.

    # 3. Check the Mini Program jump logic

    Check the Mini Program code logic, whether it is called during the authorization of the Mini Program mobile phone number wx.reLaunch，[wx.navigateTo ](https://developers.weixin.qq.com/miniprogram/dev/api/Route/wx.navigateTo .html) ，wx.redirectTo，[wx.navigateBack ](https://developers.weixin.qq.com/miniprogram/dev/api/Route/wx.navigateBack .html) Etc. Jump class interface. If this interface is invoked during the mobile phone number authorization popup, it may result in incorrect receipt of the bindgetphonenumber Callback.
    If confirmed, you can enter No. 4 Step.

    # 4. Still unresolved

    If the cause is still not determined, it can be found inWeChat Open CommunityMini ProgramplatePost to contact us.
    Please provide a full day of yesterday's mobile phone number authorization report data in the following format:

    timestamp,openid
1702036265,o7esq5LyxOBDdEwP4hY4oVgwSjTE
1702036277,oACo74-LaazkCVfp8c9cihawu91E
...

    The timestamp is a second Unix timestamp, and we will compare and analyze the data provided.