Error Message
No HAP signing tool found in the SDK.
Symptom
The signing tool cannot be found in the SDK.
Possible Causes
The signing tool is not included in the SDK.
Solution
Check whether the signing tool exists in the corresponding directory. If not, re-download DevEco Studio from the official website.
Error Message
The SDK version configured for the current project is too low.
Symptom
The SDK version is outdated.
Possible Causes
The SDK version is outdated.
Solution
Download the latest DevEco Studio from the official website.
Error Message
Unsupported SDK version for using AOT compiling. Current SDK version is XXX, but the lowest SDK version which support AOT compiling is XXX.
Symptom
The current SDK version does not support the AOT compilation mode.
Possible Causes
The SDK version is outdated.
Solution
Download the latest DevEco Studio from the official website.
Error Message
Current version of SDK has a bug when using AOT compiling. The compiling will continue with AOT compiling function disabled. Current SDK version is XXX, but the lowest fixed SDK version is XXX.
Symptom
The current SDK version does not support the AOT compilation mode.
Possible Causes
The SDK version is outdated.
Solution
Download the latest DevEco Studio from the official website.
Error Message
byteCodeHar not supported when below API version 12.
Symptom
Bytecode HARs are not supported if the API version is earlier than 12.
Possible Causes
Bytecode HARs are not supported if the API version is earlier than 12.
Solution
Ensure that compileSdkVersion and compatibleSdkVersion in the build-profile.json5 file are not earlier than API version 12.
Error Message
The oh-package.json5 file cannot be found in the remote HSP XXX. Check whether the oh-package.json5 file exists in YYY.
Symptom
The oh-package.json5 file cannot be found in HSP XXX.
Possible Causes
The HSP is damaged.
Solution
Check whether the oh-package.json5 file exists in the HSP in a specific directory. If the file does not exist, the package is damaged. In this case, download the package again or contact the author.
Error Message
Cannot find the .hsp file in the remote HSP. Check whether the .hsp file exists in the XXX directory.
Symptom
The .hsp file cannot be found in the HSP.
Possible Causes
The HSP is damaged.
Solution
Check whether the .hsp file exists in the HSP in the XXX directory. If the file does not exist, the package is damaged. In this case, download the package again or contact the author.
Error Message
The local dependency below in module XXX invalid. It may cause an ohpm install error when being integrated.
Symptom
The local dependency of module XXX is invalid. ohpm may fail to be installed during integration.
Possible Causes
The local dependency configured for the module is not in the current module directory.
Solution
Ensure that all local dependencies configured in dependencies and dynamicDependencies in the module-level oh-package.json5 file are in the current module directory.
Error Message
The useNormalizedOHMUrl settings of packages XXX and the project useNormalizedOHMUrl:XXX do not match.
Symptom
The value of useNormalizedOHMUrl in package XXX is different from that in the project.
Possible Causes
The value of useNormalizedOHMUrl in the project-level build-profile.json5 file is different from that in package XXX.
Solution