This section describes only module-specific error codes. For details about universal error codes, please refer to Universal Error Codes.
Message
Permission denied.
Symptom
Permission verification failed.
Possible causes
The HAP has not obtained the ohos.permission.USE_FRAUD_MESSAGES_PICKER, ohos.permission.USE_FRAUD_CALL_LOG_PICKER, or ohos.permission.USE_FRAUD_APP_PICKER permission.
Solution
Only apps that meet the application scenario requirements can apply for these permissions. To use the fraudulent message picker in the fraudulent message reporting scenario, you need to apply for the ohos.permission.USE_FRAUD_MESSAGES_PICKER permission. To use the fraudulent call log picker in the fraudulent call reporting scenario, you need to apply for the ohos.permission.USE_FRAUD_CALL_LOG_PICKER permission. For details about how to apply for a restricted permission, please refer to Requesting Restricted Permissions.
Message
Parameter error.
Symptom
Parameter check failed.
Possible causes
A mandatory parameter is missing, or the parameter type or specifications are invalid.
Solution
Make sure all the mandatory parameters are passed and the parameter types and specifications are valid.
Message
Unknown error.
Symptom
Internal error.
Possible causes
An exception occurred when other system APIs are called in the API execution process.
Solution
Try again later. If the error persists, submit a ticket online.
Message
The device type is not supported.
Symptom
The device type is not supported.
Possible causes
The device is not a phone or tablet.
Solution
Use a phone or tablet to send the request again.
Message
Unknown error.
Symptom
An internal error occurred in the fraudulent app picker.
Possible causes
An exception occurred when other system APIs are called in the API execution process.
Solution
Try again later. If the error persists, submit a ticket online.
Message
The device type is not supported.
Symptom
The device type is not supported by the fraudulent app picker.
Possible causes
The device is not a phone or tablet.
Solution
Use a phone or tablet to send the request again.
Message
Parameter verification failed.
Symptom
Failed to check the AntifraudPicker API parameters.
Possible causes
A mandatory parameter is missing, or the parameter type or specifications are invalid.
Solution
Make sure all the mandatory parameters are passed and the parameter types and specifications are valid.