Custom Node Error Codes
NOTE
This topic describes only module-specific error codes. For details about universal error codes, see Universal Error Codes.
100021 FrameNode Not Modifiable
Error Message
The FrameNode is not modifiable.
Description
This error code is reported when the current FrameNode is unmodifiable, preventing the requested operation, for example, setting properties, adding or removing child nodes, or binding controllers.
Possible Causes
An attempt is made to modify a declarative node.
Solution
Avoid modifying unmodifiable nodes. Use try-catch to handle errors and prevent impact on other logic.
100022 Cross-Language Attribute Configuration Not Supported
Error Message
The FrameNode cannot be set whether to support cross-language common attribute setting.
Description
This error code is reported when the target FrameNode does not support cross-language attribute configuration.
Possible Causes
An attempt is made to adjust the cross-language attribute permission of the target FrameNode.
Solution
NA
100023 Parameter Error
Error Message
Parameter error. Possible causes: 1. The component type of the node is incorrect. 2. The node is null or undefined. 3. The controller is null or undefined.
Description
This error code is reported when the parameters passed to the API are incorrect.
Possible Causes
- The component type of the provided node is incorrect.
- The provided node is null or undefined.
- The provided controller is null or undefined.
Solution
Adjust the passed parameter values or perform pre-checks.
100024 No Common Ancestor Node Between Nodes
Error Message
The current FrameNode and the target FrameNode do not have a common ancestor node.
Description
This error code is reported when the current node and the target node do not share a common ancestor node.
Possible Causes
A common ancestor node between the current node and the target node could not be found.
Solution
Modify the value of the passed parameter.
100025 Invalid Parameter Value
Error Message
The parameter is invalid. Details about the invalid parameter and the reason are included in the error message. For example: "The parameter 'targetNode' is invalid: it cannot be disposed."
Description
This error code is reported when the provided parameter value is invalid.
Possible Causes
See the error information.
Solution
- For null or undefined value errors: Provide a valid FrameNode instance.
- For ancestry errors: Check whether the target node is an offscreen node before passing it, and modify the target node accordingly.
- For errors due to other causes, refer to the error message for detailed correction guidance.
100026 The Instance Object Used to Call the API Has Been Unbound from the Backend Entity Node
Error Message
The current item has been disposed.
Description
This error code is reported when the instance object used to call the API has been unbound from the backend entity node.
Possible Causes
The disposeNode API has been previously called using this instance object, for example, item.dispose().
Solution
- To continue using this instance object, avoid performing the dispose operation on it.
- To check whether the instance object is available, call the isDisposed API.
100027 The Current Node Has Been Adopted as a Child Node
Error Message
The current node has been adopted.
Description
This error code is reported when the current node has been adopted as a child node and does not support the requested operation.
Possible Causes
The current node has been adopted as a child node and does not support the requested operation.
Solution
Cancel the adoption of the current node before performing the operation.
100028 Current Node Is Not on the Main Node Tree
Error Message
The current FrameNode is not on the main tree.
Description
The current node is not on the main node tree.
Possible Causes
The current node is not on the main node tree.
Solution
Mount the current node to the main node tree before performing the operation.
100029 State Management V2 Does Not Support Component Reuse in the BuilderNode
Error Message
Reuse/Recycle not implemented for ViewV2, yet.
Description
In the BuilderNode, state management V2 does not support component reuse.
Possible Causes
State management V2 does not support component reuse in the BuilderNode.
Solution
When using state management V2, do not use component reuse in the BuilderNode. Since API version 26.0.0, custom components in the BuilderNode support V2 component reuse.
106103 Operation Not Allowed on Nodes Created by ArkTS
Error Message
The corresponding operation does not support nodes created by ArkTS.
Description
This error code is reported when the operation does not support nodes created by ArkTS.
Possible Causes
The current operation is incompatible with nodes created by ArkTS.
Solution
Pass nodes not created by ArkTS.
106203 Passed Node Not Mounted to Component Tree
Error Message
The node not mounted to component tree.
Description
This error code is reported when the passed node is not mounted to the component tree.
Possible Causes
The passed node is not mounted to the component tree when the API is called.
Solution
Adjust the API call timing to ensure the node is mounted to the component tree.
106204 Operations on the Provided Node Not Supported on Non-UI Threads
Error Message
Operation on passed in nodes in non UI threads is not supported.
Description
This error code is reported when an attempt is made to manipulate nodes on a non-UI thread.
Possible Causes
- The API can be called only on the UI thread.
- The API supports multi-thread calling, but the node operated by the API is in the attached state.
Solution
- Adjust the API call timing to ensure the API is called from the UI thread.
- Ensure that the node is created by the multi-threaded createNode API.
- Remove all non-convertible attached components from the component tree where the component is located by referring to Multi-threaded NDK API Set Specifications.