This section describes only module-specific error codes. For details about universal error codes, please refer to Universal Error Codes.
Message
The arrays of pageIndices and matrices do not match.
Description
The lengths of the pageIndices and matrices arrays are different.
Possible causes
The lengths of the pageIndices and matrices arrays are different.
Solution
Ensure that the length of the pageIndices array is the same as that of the matrices array.
Message
Invalid page number.
Description
The page number in pageIndices is not within the valid range.
Possible causes
Solution
Ensure that the page number specified by pageIndices is greater than or equal to 0 and less than the total number of pages, and the total number of pages does not exceed 16.
Message
The number of pixels in the bitmap exceeds the upper limit.
Description
The number of pixels in the bitmap exceeds the upper limit.
Possible causes
The number of pixels corresponding to the bitmap size (bitmapWidth × bitmapHeight) exceeds 250 MB.
Solution
Ensure that the number of pixels corresponding to the bitmap size (bitmapWidth × bitmapHeight) does not exceed 250 MB.
Message
Failed to create a bitmap.
Description
Failed to create a bitmap.
Possible causes
System resources are insufficient.
Solution
Message
Failed to render the bitmap.
Description
Failed to render the bitmap.
Possible causes
The PDF document is incomplete.
Solution
Message
The PDF document is not loaded.
Description
The PDF document is not loaded and cannot be accessed.
Possible causes
The document has not been loaded through the initialization process or the loading process is interrupted.
Solution
Call loadDocument to trigger the loading process again.
Message
Invalid page number.
Description
The value of initPageIndex passed to loadDocumentFromMemory is not within the valid range.
Possible causes
Solution
Ensure that the value of initPageIndex is a natural number.
Message
The loaded document has not been freed.
Description
A loaded document is not released.
Possible causes
After the loadDocumentFromMemory API is called to successfully load the binary data stream of a document, the releaseDocument API is not called to release the document. Instead, the binary data stream of the document is loaded again in the same controller.
Solution
Call the releaseDocument API to release the binary data stream of the document loaded by the current controller.
Message
The input ArrayBuffer is empty or exceeds the maximum limit.
Description
The binary data stream loaded by the loadDocumentFromMemory API is empty or exceeds the maximum size supported by the API.
Possible causes
Solution
Message
The rendering thread is busy.
Description
Rendering is busy.
Possible causes
The interval between the current call and the last call of this API is less than 300 ms.
Solution
Wait for 300 ms before calling this API again.
Message
Unknown rendering mode.
Description
The rendering mode is invalid.
Possible causes
The value passed to setRenderMode is out of the specified range.
Solution
Reset the parameter constraints to allow only predefined enumerated values.
Message
Another document is being loaded.
Description
The current document cannot be loaded because there is an unfinished asynchronous loading task.
Possible causes
The asynchronous loading API is concurrently called within a short period of time.
Solution
Check the calling logic to avoid consecutive calls of the asynchronous loading API.