This topic describes only the error codes specific to this module. If an API call exception occurs when you use ArkUI APIs, refer to the error code information in this topic to locate the cause and take the corresponding measures. For 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 or @ohos.promptAction, this error code is reported when an internal error that you cannot rectify 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 the 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, UI instance internal state validation exception, failure to query the node because the component is not mounted to the component tree, or the screenshot size exceeding the hardware limit (which varies with the hardware platform).
For UIContext: failure to create a UI instance because 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).