After App-manager restarted the DEC APP installation process, the DEC APP was not started about cyfs HOT 3 CLOSED

This is due to the fact that the previous developer handled the startup status repair logic in parallel with the command execution logic:

Since in the old code, the startup status repair was fast, just set to Failed, in most cases, the startup status was repaired before the first command was executed

However, in the new logic, the action indicated by the startup status will be executed again, which may be more time-consuming. If the Start command is executed in the startup state repair, this Start command will be skipped because DecApp is still in the wakeup state

from cyfs.

When App Manager starts, instead of executing the corresponding repair logic directly, the corresponding command is inserted into the internal cmdlist from the front end

This will make DecApp's state repair time longer, but will not cause the state error problem caused by parallel execution of repair

from cyfs.

This Issue has been fixed in Nighlty 1.1.0.754

from cyfs.