1# Updates (OpenHarmony 3.2 Beta1 -> OpenHarmony 3.2 Beta2) 2 3## Introduced Application Sandbox 4 5Based 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. 6It also resolves user experience and concurrency stability problems in file management caused by directory disorder and adoption of multiple file access modes. 7 8**Change Impact** 9 10After the application sandbox is enabled, the access operations of all applications incubated by the appspawn process will be restricted by the application sandbox. 11If an application does not adapt to the file access model of the application sandbox, it may not function in full. 12To 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). 13 14**Key API/Component Changes** 15 16OpenHarmony application sandbox component 17 18**Adaptation Guide** 19 20See [Adaptation Guide for the Application Sandbox](application-sandbox-adaptation-guide.md). 21 22## Added Build Verification for the Struct of Custom Components 23 24**Change 1**: The lifecycle functions (such as **aboutToAppear**) in the struct of a custom component cannot be decorated using **private**. 25 26**Change Impact** 27 28Before the change, only the editor performs verification. After the change, the compiler also performs verification. 29 30**Key API/Component Changes** 31 32None 33 34**Adaptation Guide** 35 36If any of the following situations occurs, remove **private**. 37 38 39 40 41 42**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. 43 44**Change Impact** 45 46If 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. 47 48**Key API/Component Changes** 49 50None 51 52**Adaptation Guide** 53 54If any of the following situations occurs, change the property name: 55 56 57 58 59
