From 8653b0ba42a4896ef9d69f4fcfb3afec308fea33 Mon Sep 17 00:00:00 2001 From: Gloria Date: Thu, 11 May 2023 19:46:03 +0800 Subject: [PATCH] Update docs against 17244 Signed-off-by: wusongqing --- .../v3.2-beta2/application-sandbox-adaptation-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/en/release-notes/changelogs/v3.2-beta2/application-sandbox-adaptation-guide.md b/en/release-notes/changelogs/v3.2-beta2/application-sandbox-adaptation-guide.md index eecc9cebc8..d32a42dd94 100644 --- a/en/release-notes/changelogs/v3.2-beta2/application-sandbox-adaptation-guide.md +++ b/en/release-notes/changelogs/v3.2-beta2/application-sandbox-adaptation-guide.md @@ -14,7 +14,7 @@ 1. Check whether the identified exception is caused by an incorrect access path of the application source code. You can check the correctness of an access path against [Sandbox File Access Specifications](#sandbox-file-access-specifications). 2. If the application source code accesses an incorrect path, change the path access policy. Specifically, use the **Context** API rather than the absolute path to access the **/data** directory. For details about the **Context** API, see the following documents: - https://gitee.com/openharmony/docs/blob/master/zh-cn/application-dev/application-models/application-context-stage.md + https://gitee.com/openharmony/docs/blob/master/en/application-dev/application-models/application-context-stage.md 3. If the exception is caused by a third-party module invoked by the application and the application source code does not use an absolute path to access files, proceed as follows: - Request the third-party module to access the file path through the **Context** API instead of using the absolute path. - If the third-party module is a common module used by both appspawn incubated processes and native processes, abstract the third-party module as a service and access the service in IPC mode. -- GitLab