Mobile Platform as a Service:mPaaS Mini Program stuck on loading page at startup

Issue description

When an app starts an mPaaS Mini Program, the program gets stuck on the loading page.

Common causes

Possible causes for this issue include the following:

• The home page path of the Mini Program is incorrect.

• The kernel is missing.

• The public resource package for the Mini Program is not initialized.

Integrating the mPaaS kernel into your Android application resolves browser compatibility issues across different vendors. It also provides a lower crash rate and better performance than the system browser. The mPaaS kernel provides security support to promptly address vulnerabilities. Using the mPaaS kernel enables your Mini Program to use same-layer rendering capabilities, such as embedding webviews and maps, for an improved rendering experience. To use Mini Programs, you must request an mPaaS kernel. Submit a request to obtain a key for the mPaaS kernel and configure the related parameters in the AndroidManifest.xml file.

Troubleshooting steps

1. Check if the mPaaS kernel is active. Run the .apk package on a mobile phone and check the logs to verify that the kernel is active. In the Android Studio logcat, filter for webview version . The results are typically one of the following:

   • A version number that starts with 0.11. indicates the mPaaS kernel. For example: webview version : 0.11.0.241023201746.

   • A version number that starts with Chrome indicates the system kernel. For example: webview version : Chrome/74.8.3729.136.

   • If you previously used the UC kernel, a version number that starts with 3 or 5 is also acceptable. For example: webview version : 3.21.8.82.200108164219.

2. Check if the main entry path of the Mini Program is correct. The main entry path for the Mini Program must match the main entry path configured in the mPaaS console. You can set the main entry in the location shown in the following figure:

   The default main entry URL in the mPaaS console is pages/index/index.

3. Check if the public resource package for the Mini Program is initialized in the Application class. The public resource package must be initialized to use Mini Programs.

   

If the issue persists, prepare a demo project that reproduces the issue. You can also search for and join the DingTalk group 145930007362 for assistance.