• Home
  • Line#
  • Scopes#
  • Navigate#
  • Raw
  • Download
1# Pushing Files to an Application Sandbox Directory
2
3During the development and debugging process of an application, you may need to push files to the application sandbox directory for intra-application access or for testing purposes. You can use either of the following methods to push files:
4
5- Use DevEco Studio to push the files to the application installation directory. For details, see [Application Installation Resource Access](../quick-start/resource-categories-and-access.md#resource-access).
6
7- Use the hdc tool to push files to the application sandbox directory on the device, which is described below.
8
9The directories displayed in the hdc shell in the debugging process are different from the application sandbox paths visible to the application. You need to understand the mappings between them.
10
11## Mappings Between Application Sandbox Paths and Physical Paths
12
13The read and write operations performed on an application sandbox directory are eventually performed on the files in the physical directory after address conversion. The following table lists their mappings.
14
15<USERID> has a fixed value of **100**.
16
17| Application Sandbox Path| Physical Path in hdc| Description|
18| -------- | -------- | -------- |
19| /data/storage/el1/bundle | /data/app/el1/bundle/public/&lt;PACKAGENAME&gt; | Application installation package directory.|
20| /data/storage/el1/base | /data/app/el1/&lt;USERID&gt;/base/&lt;PACKAGENAME&gt; | Application directory of encryption level 1.|
21| /data/storage/el2/base | /data/app/el2/&lt;USERID&gt;/base/&lt;PACKAGENAME&gt; | Application directory of encryption level 2.|
22| /data/storage/el1/database | /data/app/el1/&lt;USERID&gt;/database/&lt;PACKAGENAME&gt; | Database directory of the application under **el1/**.|
23| /data/storage/el2/database | /data/app/el2/&lt;USERID&gt;/database/&lt;PACKAGENAME&gt; | Database directory of the application under **el2/**.|
24| /data/storage/el2/distributedfiles | /mnt/hmdfs/&lt;USERID&gt;/account/merge_view/data/&lt;PACKAGENAME&gt; | Distributed data directory of the application under **el2/**.|
25
26## Development Example
27
28The following uses the bundle **com.ohos.example** as an example. If the application sandbox path is **/data/storage/el1/bundle**, the physical path is **/data/app/el1/bundle/public/com.ohos.example**.
29
30Run the following command to push a file:
31
32```
33hdc file send ${Path of the local file to send}/data/app/el1/bundle/public/com.ohos.example/
34```
35
36After the file is pushed, set **user_id** and **group_id** of the file to **user_id** of the application. You can run the following command to query **user_id** of the application, which is the value in the first column of the process.
37
38```
39hdc shell ps -ef | grep com.ohos.example
40```
41
42Run the following command to set **user_id** and **group_id** of the file based on **user_id** of the application process:
43```
44hdc shell chown ${user_id}:${user_id} ${ file_path}
45```
46
47## Switching to the Application View
48
49During the debugging process, if the required permission is unavailable or the file does not exist, you need to switch from the process view to the application view and further analyze permission and directory problems. To switch to the application view, run the following commands:
50
51```
52hdc shell                         // Switch to shell.
53ps -ef|grep [hapName]             // Obtain the process identifier (PID) of the application.
54nsenter -t [hapPid] -m /bin/sh    // Enter the application sandbox environment based on the PID.
55```
56
57Now the application view is in use, and the paths you see are the application sandbox paths.
58