API Call Error Codes

NOTE

This topic describes only module-specific error codes. For details about universal error codes, see Universal Error Codes.

100001 Internal Error

Error Message

When used for @ohos.animator: "The specified page is not found or the object property list is not obtained."

When used for @ohos.promptAction or UIContext: "Internal error."

When used for @ohos.router: "Internal error. UI execution context is not found."

When used for the Navigation routing framework: "Internal error. Create NavDestination failed, probably caused by wrong UIContext."

When used for @ohos.arkui.componentSnapshot: "The builder is not a valid build function."

When used for @ohos.arkui.componentUtils: "UI execution context not found."

Symptom

For @ohos.animator and @ohos.promptAction, this error code is reported when an internal error that cannot be rectified by developers occurs, with specific details included in the error message.

For @ohos.router, this error code is represented as a string type.

For the Navigation routing framework, this error code is represented as a number type.

For @ohos.arkui.componentSnapshot, this error code is triggered when the internal state is abnormal.

For UIContext, this error code is reported when an internal error that cannot be rectified by developers occurs.

Possible Cause

For @ohos.animator, @ohos.router, or Navigation routing framework: failure to obtain the rendering engine or parse parameters.

For @ohos.promptAction: failure to obtain the rendering engine or parse parameters, or unclear UI context.

For @ohos.arkui.componentSnapshot: failure to obtain a valid UI instance, null pointer exception, failed internal state validation of the UI instance, inability to query the node (because the component is not added to the tree), or snapshot size exceeding hardware limits (which may vary by hardware platform).

For UIContext: failure to create a UI instance because the color picking parameters are not set as required by the API or in invalid types, the memory is insufficient, or the JS VM is abnormal.

Solution

For issues related to the issue of ambiguous UI context, use the APIs provided in UIContext. For details, see Using the UI Context API for UI Operations (UIContext).