Symptom
During the hot reload process, if the current code changes are not supported by hot reload, the console will display an error message, requesting reinstallation and restart.
Solution
This issue occurs when the code changes exceed the supported range. For details about the range of supported code changes, see Constraints.
Common unsupported code scenarios
- Addition or modification of member variables and functions in struct Index decorated by @Entry
- Addition of class member functions in the @Entry file
- Modification of the enums in the @Entry file
- Addition and modification of a module that is not imported
If a code file is not imported at the start of the hot reload, adding imports for this file during hot reload is not supported. For example, if TestC.ets is not imported in Index.ets at the start of the hot reload, adding import xxx from './TestC.ets'; will not be supported during hot reload.
If an import statement is dimmed before hot reload, the file will not be compiled and will be treated as an unloaded module.
- Modification of top-level closure variables (though addition and deletion are supported)
- Placement of class inheritance classes and inherited classes in the @Entry file. You are advised to write class in a non-@Entry file.
- Modification of most decorators in the @Entry file
Currently, hot reload does not support the modification of most decorators. The @Styles decorator can be added and modified in the @Entry file. The @Builder decorator can be modified but cannot be added. The @State decorator cannot be added or modified.
Addition and modification of custom components in other structs inside the @Entry file
It is recommended that you import these components instead.
- Addition and modification of classes or functions with the same name as @State decorated variables in the @Entry file
- Modification of non-ETS or non-TS code files
- Modification of Worker thread files
