The security guard error codes listed in this article are applicable to both Android and iOS operating systems. The error codes are divided into the following three types according to different error types:
If an error occurs, error information SG ERROR: xxxx is displayed in the Xcode console. This topic describes related error codes.
Common error codes
Error code | Description |
101 | Incorrect parameter. |
102 | Main plug-in initialization failed. |
103 | Dependent plug-ins are not introduced. The system will provide the name of the missing plug-ins while printing the error code. Please introduce the plug-in as prompted. |
104 | Failed to load plug-ins that are introduced. Generally, this error code is printed when |
105 | The required plug-in is introduced, but its dependent plug-in is not. The system will provide the name of the missing plug-in while printing the error code. Introduce the plug-in as prompted. |
106 | The required plug-in is introduced, but its dependent plug-in does not meet the version requirement. The system will provide the required version number of the dependent plug-in while printing the error code. Introduce the dependent plug-in of the correct version as prompted. |
107 | The required plug-in is introduced, but it does not meet the version requirement. |
108 | The required plug-in is introduced, but its dependent resource is not. |
109 | The required plug-in is introduced, but its dependent resource does not meet the version requirement. |
121 | Image file error. Generally, this error code is printed when the bundle ID used for generating the image file is different from that of the App. |
122 | Image file not found. Ensure that the image file exists in the project directory. |
123 | Incorrect image file format. Generate the image file again. |
124 | The image version is earlier than required. |
125 | init with authcode Initialization error. |
199 | Unknown error. Try again. |
201 | Incorrect parameter. |
202 | Image file error. Generally, this error code is printed when the bundle ID used for generating the image file is different from that of the App. |
203 | Image file not found. Ensure that the image file exists in the project directory. |
204 | Incorrect image file format. Generate the image file again. |
205 | Incorrect image file content. Generate the image file again. |
206 | The key in the parameter is not found in the image file. Please use an existing key. |
207 | The input key is invalid. |
208 | Insufficient memory. Try again. |
209 | The key of the specified index does not exist. |
212 | The version of the image file is earlier than required. Upgrade it. |
299 | Unknown error. Try again. |
Static data encryption and decryption error codes
Error code | Description |
301 | Incorrect parameter. |
302 | Image file error. Generally, this error code is printed when the APK signature used for generating the image file is different from that of the App. Use the APK signature of the App to generate the image file again. |
303 | Image file not found. Ensure that the image file exists in |
304 | Incorrect image file format. Generate the image file again. A common scenario where this error occurs is that second-party images are used together with third-party images, while they are incompatible with each other and must be generated separately. |
305 | Incorrect image file content. Generate the image file again. |
306 | The key in the parameter is not found in the image file. Use an existing key. |
307 | The input key is invalid. |
308 | Insufficient memory. Try again. |
309 | The key of the specified index does not exist. |
310 | The data cannot be decrypted. |
311 | The data to be decrypted does not match the key. |
312 | The version of the image file is earlier than required. Generate an image file of a later version. |
399 | Unknown error. Try again. |
401 | Incorrect parameter. |
402 | Insufficient memory. Try again. |
403 | Failed to obtain system attributes. Ensure that no software blocks this operation. |
404 | Failed to obtain the key in the image file. Ensure that the format and content of the image file are correct. |
405 | Failed to obtain the dynamic encryption key. Try again. |
406 | The format of the data to be decrypted does not meet the decryption requirements. |
407 | The data to be decrypted does not meet the decryption requirements. Ensure that the data is generated after dynamic encryption by Security Guard on this device. |
499 | Unknown error. Try again. |
501 | Incorrect parameter. |
502 | Insufficient memory. Try again. |
503 | Failed to obtain system attributes. Ensure that no software blocks this operation. |
504 | Failed to obtain the key in the image file. Ensure that the format and content of the image file are correct. |
505 | Failed to obtain the dynamic encryption key. Try again. |
506 | The data cannot be decrypted. |
507 | The data to be decrypted does not match the key. Try again. |
508 | No value is found for the input key. |
599 | Unknown error. Try again. |
Security signature API error codes
Error code | Description |
601 | Incorrect parameter. |
602 | Insufficient memory. Try again. |
606 | When the top signature with a seed key is used, the corresponding seed secret is not found. |
607 |
|
608 | Image file |
609 |
A common scenario where this error occurs is that second-party images are used together with third-party images, while they are incompatible with each other and must be generated separately. |
610 |
|
611 | The key in the parameter is not found in the image file. Use an existing key. |
615 | The version of the image file is earlier than required. Generate an image file of a later version. |
699 | Unknown error. Try again. |