1e41f4b71Sopenharmony_ci# Updates (OpenHarmony 3.2 Beta1 -> OpenHarmony 3.2 Beta2) 2e41f4b71Sopenharmony_ci 3e41f4b71Sopenharmony_ci## Introduced Application Sandbox 4e41f4b71Sopenharmony_ci 5e41f4b71Sopenharmony_ciBased on the namespace mechanism, OpenHarmony introduces the application sandbox to enhance application data security and reduce the possible leakage of application data and user privacy information. 6e41f4b71Sopenharmony_ciIt also resolves user experience and concurrency stability problems in file management caused by directory disorder and adoption of multiple file access modes. 7e41f4b71Sopenharmony_ci 8e41f4b71Sopenharmony_ci**Change Impact** 9e41f4b71Sopenharmony_ci 10e41f4b71Sopenharmony_ciAfter the application sandbox is enabled, the access operations of all applications incubated by the appspawn process will be restricted by the application sandbox. 11e41f4b71Sopenharmony_ciIf an application does not adapt to the file access model of the application sandbox, it may not function in full. 12e41f4b71Sopenharmony_ciTo access files in the **/data** directory, the application must use the **Context** API, rather than a hard-coded path. For details, see [Adaptation Process](application-sandbox-adaptation-guide.md#adaptation-process). 13e41f4b71Sopenharmony_ci 14e41f4b71Sopenharmony_ci**Key API/Component Changes** 15e41f4b71Sopenharmony_ci 16e41f4b71Sopenharmony_ciOpenHarmony application sandbox component 17e41f4b71Sopenharmony_ci 18e41f4b71Sopenharmony_ci**Adaptation Guide** 19e41f4b71Sopenharmony_ci 20e41f4b71Sopenharmony_ciSee [Adaptation Guide for the Application Sandbox](application-sandbox-adaptation-guide.md). 21e41f4b71Sopenharmony_ci 22e41f4b71Sopenharmony_ci## Added Build Verification for the Struct of Custom Components 23e41f4b71Sopenharmony_ci 24e41f4b71Sopenharmony_ci**Change 1**: The lifecycle functions (such as **aboutToAppear**) in the struct of a custom component cannot be decorated using **private**. 25e41f4b71Sopenharmony_ci 26e41f4b71Sopenharmony_ci**Change Impact** 27e41f4b71Sopenharmony_ci 28e41f4b71Sopenharmony_ciBefore the change, only the editor performs verification. After the change, the compiler also performs verification. 29e41f4b71Sopenharmony_ci 30e41f4b71Sopenharmony_ci**Key API/Component Changes** 31e41f4b71Sopenharmony_ci 32e41f4b71Sopenharmony_ciNone 33e41f4b71Sopenharmony_ci 34e41f4b71Sopenharmony_ci**Adaptation Guide** 35e41f4b71Sopenharmony_ci 36e41f4b71Sopenharmony_ciIf any of the following situations occurs, remove **private**. 37e41f4b71Sopenharmony_ci 38e41f4b71Sopenharmony_ci 39e41f4b71Sopenharmony_ci 40e41f4b71Sopenharmony_ci 41e41f4b71Sopenharmony_ci 42e41f4b71Sopenharmony_ci**Change 2**: The member property name in the struct of a custom component cannot be the same as the built-in property or method name. 43e41f4b71Sopenharmony_ci 44e41f4b71Sopenharmony_ci**Change Impact** 45e41f4b71Sopenharmony_ci 46e41f4b71Sopenharmony_ciIf the member property name in the struct of a custom component is the same as the built-in property or method name, the verification fails. 47e41f4b71Sopenharmony_ci 48e41f4b71Sopenharmony_ci**Key API/Component Changes** 49e41f4b71Sopenharmony_ci 50e41f4b71Sopenharmony_ciNone 51e41f4b71Sopenharmony_ci 52e41f4b71Sopenharmony_ci**Adaptation Guide** 53e41f4b71Sopenharmony_ci 54e41f4b71Sopenharmony_ciIf any of the following situations occurs, change the property name: 55e41f4b71Sopenharmony_ci 56e41f4b71Sopenharmony_ci 57e41f4b71Sopenharmony_ci 58e41f4b71Sopenharmony_ci 59
