When an Android application opens the mPaaS mini program and “Network is not available, please try again later” is displayed, how should I troubleshoot the problem?

In our integrated mPaaS plug-in and use in the process of small programs, many developers will met can’t open the problem of small programs, for example, today * * developers, after fulfilling the basic access and try to open the small program, if the container page shows the error message “not to network, please try again later”, how should * *.

Cause analysis,

Before opening an applet application, the mPaaS needs to obtain basic information about the applet package.

So the client will take the initiative to alipay through mPaaS RPC interface. The client. To pull getUnionResource offline package information. If the applets fail to get information (RPC is abnormal), the applets will display the error “Network is down, please try again later”.

Troubleshooting Procedure

1. Filter logs

Log Log information RPC Exception.

2. Query the description of the exception code

As mentioned in common reasons.

The client needs to proactively pull the offline package information. The pull process depends on RPC requests. If the RPC link is faulty, the client cannot obtain the offline package information and the loading fails. To confirm the RPC request if there is a problem, need to search AS the console alipay. Client. GetUnionResource to see whether it has returned to normal RPC requests. If there is an error, common error codes include the 7XXX or 3XXX series, for example:

3. Resolve RPC exceptions based on different exceptions

7000-7002.

If there is a problem with the image generation, please connect to Android and generate the image again. If there is a private cloud environment, contact professional service personnel for further troubleshooting.

7003, 7007,

The validity problem may be caused by the difference between the mobile phone time setting and the gateway service time exceeding 30 minutes. Check the mobile phone time.

7014

The APK signature uploaded to the mPaas console is inconsistent with the application packaging signature. Procedure

Troubleshooting for common problems RPC7014:

  • Check whether the DEBUGGING environment for uploading Apk package signatures to the mPaas console is configured

Add debug and release information in gradle package configuration information of APP. Under normal debug environment of mobile phone running, you need to configure debug information.

  • Check whether the Package Name information and the APK file uploaded in the Android configuration information of the mPaas console are consistent with the APP project

The repair order to assist

If the problem still cannot be solved, please prepare a duplicate Demo project of the relevant problem and contact mPaaS after-sales technical support through Ali Cloud work order system.

Article: Liu Qiyang, Sting stomach

END

read

  • Troubleshooting guide for vendor push failure
  • Log in! Let’s Start Coding
  • Hard worked App being copied? MPaaS help you to reinforce the lock on APK

Click on “mPaaS applets” for more information