FAQs
Failed to Find the Header File During Compilation or Running
Symptom
The message "usb/usb_ddk_api.h not found" or "hid/hid_ddk_api.h not found" is displayed during compilation or running.
Solution
- If an error is reported during compilation, check whether the OpenHarmony version is the latest.
- If an error is reported during running, check whether the device version is 4.1 Release or later.
Version Mismatch Displayed During HAP Installation
Symptom
The message "compileSdkVersion and releaseType of the app do not match the apiVersion and releaseType on the device" is displayed during HAP installation.
Solution
Check whether the system version of the device is correct according to the mapping provided in [Version Mapping](#version-mapping).Version Mapping
| API Type | Minimum API Version | OpenHarmony Version |
|---|---|---|
| Application development APIs (ArkTS APIs) | API10 | 4.0 Release or later |
| UsbDdk APIs | API10 | 4.0 Release or later |
| HidDdk APIs | API11 | 4.1 Release or later |
| USBSerialDDK APIs | API18 | 5.1 Release or later |
| ScsiPeripheralDDK APIs | API18 | 5.1 Release or later |
Failed to Parse the Local .so File During HAP Installation
Symptom
The message "code:9568347 error: install parse native so failed" is displayed during HAP installation.
Solution
According to the solution provided in What should I do if "code:9568347 error: install parse native so failed" is displayed during HAP installation or error message "TypeError: Cannot read property xxx of undefined" is displayed during HAP running? in application debugging, manually set abiFilters in buildOption/externalNativeOptions in the build-profile.json5 file.