The developer fails to open the HTML5 application after completing the basic access, and the container page displays the error message “NoSuchKey. The specified key does not exist…”, as shown in the following figure.
<Message>The specified key does not exist.</Message>
The direct cause of this type of problem is that the address accessed by the mPaaS Nebula container points to a file, which does not exist on the MDS server. For this reason, the process that triggers the problem is generally as follows. The client tries to access a resource that does not exist in an offline package. The client misses locally, and the online fallback address also misses. So the MDS server returns this error.
Based on the cause analysis, the troubleshooting method is described as follows:
- Whether the page address of the H5 app opened by the client is correct.
- Whether the related resources in the offline package are packaged correctly.
There are three types of situations:
Actively open the H5 app and confirm whether the input URL parameter is correct.
According to the logic of the H5 app page redirection, confirm whether the opened page address is correct, including the target URL setting of the redirection form such as
- When uploading the offline package, developers must configure the default entry URL of the H5 app. Problem may occur: If the URL is not configured or the configured entry URL is incorrect, the container cannot provide the correct page address when opening the H5 app.
.amrfile on the console, modify the suffix to
.zipand decompress it. Unzip the
.tarfile in the folder, and then you can see the resource files in the offline package.
Then confirm whether the page resource file to be opened is contained in this folder.
Confirm whether the environment configuration of current app is consistent with the environment of current offline package.
Check the App ID in
meta.configin the app project:
Check the App ID on the console where the target H5 app offline package is located: