Intelligent Assistant
Chat with our virtual assistant to get answers promptly.
Error Code | Description |
|---|---|
Failed to verify the app model of the package during an update to the same version. | |
Failed to verify the app model of the package during an update to a later version. | |
Failed to verify targetBundleName in the package. | |
Failed to verify targetPriority in the package. | |
Failed to verify module.name in the entry package during an update to the same version. | |
Failed to verify module.name in the entry package during an update to a later version. |
The updated package must use the same model (FA or stage) as the version that has been released.
For details, please refer to Application Package Fundamentals.
When the version that has been released uses the FA model, the updated package can use the same model or switch to the stage model. However, if the version that has been released uses the stage model, the updated package must also use the stage model.
For details, please refer to Application Package Fundamentals.
Whether the targetBundleName parameter needs to be set during the update should be consistent with its status in the package that has been released.
For details, please refer to app.json5 Configuration File.
Whether the targetPriority parameter needs to be set during the update should be consistent with its status in the package that has been released.
For details, please refer to app.json5 Configuration File.
For the same device type (specified by deviceType), the value of module.name in the entry package for an update must be the same as that in the package which has been released. Otherwise, the app cannot be submitted for review.
For details, please refer to module.json5 Configuration File.
For the same device type (specified by deviceType), the value of module.name in the entry package for an update must be the same as that in the package which has been released. If they are inconsistent, app submission for review and release will not be affected, but user data may be lost after the update.
For details, please refer to module.json5 Configuration File.