This topic describes only module-specific error codes. For details about universal error codes, see Universal Error Codes.
Error Message
The system ability works abnormally.
Description
This error code is reported when the system ability is abnormal.
Possible Causes
The possible causes are as follows:
Solution
Try again later or restart the device.
Error Message
The specified token or callback is not registered.
Description
This error code is reported if the token or callback used in an API of continuationManager is not registered when the API is called.
Possible Causes
The specified token or callback is not registered.
Solution
Register the token or callback before calling the API.
Error Message
The number of token registration times has reached the upper limit.
Description
This error code is reported when the number of times that the continuationManager.registerContinuation API is called has reached the upper limit (600).
Possible Causes
The number of token registration times has reached the upper limit.
Solution
Use a registered token. Do not register the token too frequently.
Error Message
The specified callback has been registered.
Description
This error code is reported when the continuationManager.on API is called with a callback the same as a previous one.
Possible Causes
The same callback is used for repeated registration.
Solution
Use a different callback for registration.
Error Message
The system ability works abnormally.
Description
This error code is reported when the system ability is abnormal.
Possible Causes
The possible causes are as follows:
Solution
Try again later or restart the device.
Error Message
Failed to get the missionInfo of the specified missionId.
Description
This error code is reported when calling the distributedMissionManager.continueMission API fails.
Possible Causes
The possible causes are as follows:
Solution
Verify the mission ID.
Error Message
The application is not installed on the remote end and installation-free is not supported.
Description
This error code is reported if the application is not installed on the remote end and the installation-free feature is not supported when the distributedMissionManager.continueMission API is called.
Possible Causes
The application to continue is not installed on the remote end, and the installation-free feature is not supported.
Solution
Error Message
The application is not installed on the remote end and installation-free is supported. Try again with the freeInstall flag.
Description
This error code is reported if the application is not installed on the remote end and installation-free is supported when the distributedMissionManager.continueMission API is called.
Possible Causes
The application to continue is not installed on the remote end, and installation-free is supported. However, the freeInstall flag is not carried.
Solution
Try again with the freeInstall flag.
Error Message
The operation device must be the device where the application to be continued is currently located or the target device.
Description
This error code is reported if the operation device is not the device where the application to be continued is currently located (source device) or the target device when the distributedMissionManager.continueMission API is called.
Possible Causes
The operation device is not the source or target device.
Solution
Use the source or target device for the operation.
Error Message
The local continuation task is already in progress.
Description
This error code is reported if the local continuation task is in progress when the distributedMissionManager.continueMission API is called.
Possible Causes
The continuation task has been initiated and is not complete yet.
Solution
Wait until the continuation task is complete.
Error Message
Failed to get the missionInfo of the specified bundle name.
Description
This error code is reported when calling the distributedMissionManager.continueMission API with bundleName specified fails.
Possible Causes
The possible causes are as follows:
Solution
Verify the bundle name.
Error Message
The number of registrations has reached the upper limit.
Description
This error code is reported when the number of times that the continuationManager.register API is called exceeds the upper limit.
Possible Causes
The number of device registration times has reached the upper limit.
Solution
Restart the service and avoid frequent registration.
Error Message
The token is not registered.
Description
This error code is reported when an API of continuationManager is called with an unregistered token.
Possible Causes
The token is not registered.
Solution
Register a token and use it in the API.
Error Message
The callback has been registered.
Description
This error code is reported when the continuationManager.on API is called with a callback the same as a previous one.
Possible Causes
The specified callback has been registered.
Solution
Use a different callback for registration.
Error Message
The callback is not registered.
Description
This error code is reported when the off, updateConnectStatus, or startDeviceManager API of continuationManager is called with a callback that has been not registered by calling on.
Possible Causes
The specified callback is not registered.
Solution
Register a callback and use it in the API.
Error Message
Failed to connect to the ability.
Description
This error code is reported if connection to the specified ability fails when the startDeviceManager API of continuationManager is called.
Possible Causes
The specified token is invalid or the target ability is not working properly.
Solution
Check whether the token is valid and whether the corresponding ability is normal. Restart the service or device when needed.
Error Message
The type of callback is not supported.
Description
This error code is reported when the callback parameter in the on or off API of continuationManager is set to an incorrect type.
Possible Causes
The callback type is not supported.
Solution
Pass a supported type for the callback parameter.
Error Message
Invalid connection state.
Description
This error code is reported when the status parameter in the updateConnectStatus API of continuationManager is invalid.
Possible Causes
The status parameter is invalid.
Solution
Use a valid value for the status parameter.
Error Message
Invalid continuation mode.
Description
This error code is reported when the ContinuationExtraParams.continuationMode parameter in the register or startDeviceManager API of continuationManager is invalid.
Possible Causes
The ContinuationExtraParams.continuationMode parameter is invalid.
Solution
Use a valid value for the ContinuationExtraParams.continuationMode parameter.