Use this directory to store user-generated content. However, iTunes does perform an initial sync of any apps purchased from the App Store. The contents of this directory are not backed up by iTunes or iCloud. For more information, see the Resource Programming Guide You can, however, gain read-only access to any resources stored in the apps bundle. Writing to this directory changes the signature and prevents your app from launching. To prevent tampering, the bundle directory is signed at installation time. This directory contains the app and all of its resources. Table 1-1 Commonly used directories of an iOS app This table also describes any additional access restrictions for each subdirectory and points out whether the directory’s contents are backed up by iTunes and iCloud. Table 1-1 lists some of the more important subdirectories inside the sandbox directory and describes their intended usage. In those cases, the system frameworks use helper apps to handle any file-related operations needed to read from or modify the appropriate data stores. One exception to this rule is when an app uses public system interfaces to access things such as the user’s contacts or music. Figure 1-1 An iOS app operating within its own sandbox directoryĪn app is generally prohibited from accessing or creating files outside its container directories. Figure 1-1 shows a representation of the sandbox directory for an app. These container directories constitute the app’s primary view of the file system. The app may also request access to additional container directories-for example, the iCloud container-at runtime. The data container directory is further divided into a number of subdirectories that the app can use to sort and organize its data. The bundle container directory holds the app’s bundle, whereas the data container directory holds data for both the app and the user. Each container directory has a specific role. During installation of a new app, the installer creates a number of container directories for the app inside the sandbox directory. iOS Standard Directories: Where Files Resideįor security purposes, an iOS app’s interactions with the file system are limited to the directories inside the app’s sandbox directory. To keep the system simple, users of iOS devices do not have direct access to the file system and apps are expected to follow this convention. The iOS file system is geared toward apps running on their own.
ISAFEPLAY HOW TO ORGANIZE CODE
Precisely where you put files depends on the platform, but the overarching goal is to make sure that the user’s files remain easily discoverable and that the files your code uses internally are kept out of the user’s way. Aside from the basic tenet that you cannot write files to directories for which you do not have appropriate security privileges, apps are also expected to be good citizens and put files in appropriate places. Although the basic directory structures are similar for iOS and macOS, there are differences in the way each system organizes apps and user data.īefore you begin writing code that interacts with the file system, you should first understand a little about the organization of file system and the rules that apply to your code. Because the number of files can easily be many millions, the file system uses directories to create a hierarchical organization. Regardless of the underlying format, all of the disks attached to the device-whether they are physically plugged in or are connected indirectly through the network-contribute space to create a single collection of files. macOS additionally supports a variety of other formats, as described in Supported File Systems. APFS replaces HFS+ as the default file system for iOS 10.3 and later, and macOS High Sierra and later. Therefore, the file system is one of the fundamental resources used by all processes.ĪPFS is the default file system in macOS, iOS, watchOS, and tvOS. A file system handles the persistent storage of data files, apps, and the files associated with the operating system itself.
0 kommentar(er)
