Shulou(Shulou.com)05/31 Report--

MPaaS-iOS Mini Program can not open the solution to the problem is what, many novices are not very clear, in order to help you solve this problem, the following editor will explain in detail for you, people with this need can come to learn, I hope you can gain something.

In the process of integrating the mPaaS plug-in and using Mini Program, many developers encountered the problem that they could not open Mini Program. Today, for example, after completing the basic access, the developer tries to open the H5 application, but the container page displays the error prompt "set tag".

Common reasons

Before opening an H5 application, the mPaaS framework first needs to know the basic information of the offline package of the application.

Therefore, the client will actively pull the offline packet information through the RPC interface alipay.client.getUnionResource. If the acquisition of offline package information fails, or does not hit the target application to be opened, the container will prompt the error "the system is busy, please try again later."

In view of this kind of problem, the troubleshooting direction includes checking whether the RPC request is normal, checking whether the environment and offline package release match, and so on.

Troubleshooting steps

(1) check whether the RPC request is normal

The client needs to actively pull the offline packet information, and the pull process depends on the RPC request. If there is a problem with the RPC link, the offline packet information can not be obtained normally, resulting in loading failure. To confirm whether there is a problem with the RPC request, you need to search the Xcode console for alipay.client.getUnionResource to see if the RPC request returns normally. If there is an error, the general error code includes 7XXX or 3XXX series, for example:

Normal return sample (result-status is 1000):

Demo [83767 APMobileNetwork alipay.client.getUnionResource resp 2555863] [mPaaSLog] APMobileNetwork alipay.client.getUnionResource resp: {"Content-Encoding" = gzip; "Content-Type" = "text/plain;charset=UTF-8"; Date = "Tue, 11 Aug 2020 05:01:37 GMT"; Vary = "Accept-Encoding"; "mgw-traceid" = 0a1cfd401597122097726853822435; "result-status" = 1000; "server-time" = 159122097739;}

Sample error return (result-status is not 1000):

Demo [83383 APMobileNetwork alipay.client.getUnionResource resp 2546279] [mPaaSLog] APMobileNetwork alipay.client.getUnionResource resp: {"Content-Length" = 0; "Content-Type" = "text/plain;charset=UTF-8"; Date = "Tue, 11 Aug 2020 04:50:08 GMT"; memo = "% E9%AA%8C%E7%AD%BERPC%E6%8E%A5%E5%8F%A3%20%E5%8A%A0%E7%AD%BE%E6%95%B0%E6%8D%AE%E4%B8%BA%E7%A9%BA" "mgw-traceid" = 0a1d7667159712140890222728553; "result-status" = 7014; "server-time" = 1597121408902 tips = "% E9%AA%8C%E7%AD%BERPC%E6%8E%A5%E5%8F%A3%20%E5%8A%A0%E7%AD%BE%E6%95%B0%E6%8D%AE%E4%B8%BA%E7%A9%BA";}

The handling method of RPC 7XXX Series error

7XXX errors are all related to the signature verification process of RPC requests. Common error codes and reasons are as follows:

The error code indicates that example 7000 does not set the public key mobile APP. There is no key corresponding to appId in the wireless bodyguard, or the gateway cannot obtain the corresponding signature key of appId. 7001 the parameters for signature verification are not enough for the gateway server to verify that the signature fails. 7002 signature verification failed at the gateway server. 7003 Verification-timeliness failed API request input parameter ts timestamp exceeds the time validity set by the system. You need to check whether the client time is system time. 7007 signature verification-missing ts parameter API request missing signature verification ts parameter. 7014 signature verification-missing sign parameter API request missing signature verification sign parameter. In general, it is the client signature data failure, resulting in the missing sign parameter. Please check whether the client wireless bodyguard picture is correct.

(2) basic investigation actions

1. Check whether the Bundle ID set on the mPaaS console is exactly the same as the iOS project, including:

The Bundle ID set on the mPaaS console (console > Code configuration > iOS):

Bundle "Indentifier of the project:

Bundle Indentifier of Info.plist in the project:

two。 Whether the contents of the .config file downloaded by the console are exactly the same as the meta.config in the project:

The .config file downloaded by the mPaaS console:

Meta.config file in the project:

3. Whether the time of the client device is the current time, the time error must be less than 8 hours.

4. If there is any information inconsistency in the above inspection, the inspection will not pass. It is recommended:

Modify the information in the project to ensure consistency with the mPaaS console.

If the mobile phone time information is incorrect, please correct the time configuration.

Download the latest .config file from the console and re-import it through the mPaaS Extension plug-in:

After confirming that all the information is correct, uninstall the installed App, repackage and compile, and debug to see if the RPC 7XXX class error has been resolved.

(3) check whether the H5 App information and release status are correct.

The client needs to actively pull the offline package information. Under the premise that the RPC request returns normally, if the server does not return the information of the target offline package, it will also lead to the error of loading failure. The error reason is that the offline package AppNotExist does not exist.

Basic check action:

1. Confirm the alipay.client.getUnionResource according to the instructions to check whether the RPC request is normal

Whether the RPC request can be returned normally.

two。 Search the Xcode console for the error keyword AppNotExist, and confirm that the root cause of the problem is that the target H5 App cannot be found, for example:

3. Cross-confirm the following information in the mPaaS console and the iOS project, including:

WorksapceId, appId, mpaasapi and other metadata: the relevant configurations in the console and meta.config should be exactly the same. If they are inconsistent, you need to download the .config file again and import it.

Target offline package ID: the offline package ID in the offline package management page should be the same as the offline package ID to be opened in the project code

Check the release status of the offline package and confirm that there is a release version of the offline package:

Check the release status of the offline package and confirm the resource type of the offline package: it must be a "normal resource package"; the "global resource package" cannot be opened directly.

Check the offline package release status and confirm the offline package version of the release: it must be greater than the offline package version installed by the client

Check the release status of the offline package and confirm the scope of the client version covered by the release: the current version number of the test App must be overridden. Note: in the iOS project, the client version number depends on the Produc Version field in info.plist instead of the Xcode project version. Developers need to synchronize manually here.

Work order assistance

If you still can't solve the problem, please be ready to repeat the Demo project and contact mPaaS after-sales technical support through Ali Cloud ticket system.

Is it helpful for you to read the above content? If you want to know more about the relevant knowledge or read more related articles, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.