Device & systemSecurity & malware
Installed Apps on iOS: applicationState.db and Logs
Which apps were installed or removed on an iPhone: applicationState.db, iTunesMetadata.plist, container metadata, mobile_installation.log and backup lists.
- Location
- /private/var/mobile/Library/FrontBoard/applicationState.db; /private/var/containers/Bundle/Application/<UUID>/iTunesMetadata.plist; /private/var/installd/Library/Logs/MobileInstallation/mobile_installation.log.*; backup Info.plist and Manifest.plist
- Evidence area
- Proves
- Which apps are installed, their bundle IDs, versions and container paths, who purchased them and when, and (from logs) install, update and uninstall events
- Timestamps
- Mixed: plist dates (UTC) in iTunesMetadata.plist and UninstalledApplications.plist; mobile_installation.log lines in device local time without an offset
- Acquisition
- A backup lists installed apps (Info.plist, Manifest.plist). applicationState.db, iTunesMetadata.plist and installation logs need a full file system extraction; logs also appear in a sysdiagnose
- Retention
- Current state only for applicationState.db and bundles; installation logs rotate and are sparse on recent releases; uninstall records are partial
- Collection
- idevicebackup2, Full file system extraction, sysdiagnose
Tools
Compare all toolsWhat it is
There is no single "installed programs" list on iOS. The answer comes from several sources, each with its own view:
- applicationState.db (FrontBoard): a SQLite key-value store with one entry per app, used by the system to track app state. It maps bundle IDs to their bundle and data container paths and holds snapshot metadata.
- iTunesMetadata.plist in each App Store bundle: purchase information, including the Apple Account that bought the app, the purchase date and the source app.
- Container metadata: every data and group container has a
.com.apple.mobile_container_manager.metadata.plistnaming the bundle or group it belongs to, which is how UUID folders are mapped to apps. - Installation logs:
mobile_installation.logfiles andUninstalledApplications.plistrecord install, update and removal events where present. - Backups:
Info.plistlists installed applications, andManifest.plistcarries anApplicationsdictionary.
Where it lives
| Source | Path | Notes |
|---|---|---|
| applicationState.db | /private/var/mobile/Library/FrontBoard/applicationState.db | Tables application_identifier_tab, key_tab, kvs |
| App bundles | /private/var/containers/Bundle/Application/<UUID>/ | iTunesMetadata.plist, BundleMetadata.plist, the .app |
| Data containers | /private/var/mobile/Containers/Data/Application/<UUID>/ | Metadata plist names the bundle ID |
| Group containers | /private/var/mobile/Containers/Shared/AppGroup/<UUID>/ | See app group container |
| Install logs | /private/var/installd/Library/Logs/MobileInstallation/mobile_installation.log.* | Also inside sysdiagnose archives |
| Uninstalls | /private/var/installd/Library/MobileInstallation/UninstalledApplications.plist | Not present on every device |
| Backup | Info.plist (Installed Applications), Manifest.plist (Applications) | Readable without decryption for Info.plist |
What it proves
- An app with a given bundle ID and version is installed, and where its containers are.
- The Apple Account that purchased or downloaded it and the purchase date (
iTunesMetadata.plist). - Whether it came from the App Store, TestFlight, an enterprise certificate or an alternative marketplace, as far as metadata shows.
- Install, update and uninstall events from logs, where they exist.
A current snapshot does not show apps deleted earlier. For those, check logs, DataUsage, crash reports, knowledgeC and Biome app install streams, and older backups.
Key fields
| Source | Field | Meaning |
|---|---|---|
| applicationState.db | application_identifier_tab.application_identifier | Bundle ID |
| applicationState.db | kvs.value for key compatibilityInfo | Binary plist with bundle and sandbox paths |
| iTunesMetadata.plist | com.apple.iTunesStore.downloadInfo > accountInfo, purchaseDate | Purchaser and date |
| iTunesMetadata.plist | sourceApp, bundleVersion, itemName | Installing app, version, name |
| mobile_installation.log | Made container live for <bundle ID>, Uninstalling identifier <bundle ID> style lines | Events (wording varies by release) |
| UninstalledApplications.plist | bundle ID to date | One date per removed bundle |
Timestamps
- Plist dates (
purchaseDate, uninstall dates) are UTC. mobile_installation.loglines carry a text timestamp without a time zone; iLEAPP's tests found them consistent with device local time. Establish the device's time zone before converting.- applicationState.db snapshot records contain dates inside archived objects; their meaning is still being validated by the community.
Retention
applicationState.db and container metadata reflect the current state. Installation logs rotate and have become sparse on recent releases. UninstalledApplications.plist was found on only a small share of tested images and holds one date per bundle. Absence of an uninstall record is not evidence that nothing was removed.
Collection
- From a backup: copy
Info.plistandManifest.plistfirst.Info.plistis not encrypted even in an encrypted backup, so its app list is readable without the password. - From a full file system: collect
FrontBoard, theBundle/Applicationmetadata files, all container metadata plists andinstalldlogs. - From a sysdiagnose: extract the installation logs it contains.
Parsing
- iLEAPP parses applicationState.db, iTunesMetadata, container manager metadata, installation logs and the uninstalled applications plist.
- MVT extracts the app list from the backup
Info.plistor fromiTunesMetadata.plistfiles, and flags apps not installed from the App Store and bundle IDs in indicator files. plutilandsqlite3for manual review.
Investigator tips
- Map every UUID folder you cite to a bundle ID through its metadata plist, and say so in the report.
- A purchaser Apple Account that differs from the owner's may mean a shared or another person's account. Compare with Accounts3.sqlite.
- Apps installed through enterprise certificates or MDM deserve a look at configuration profiles.
- Combine the app list with TCC.db to see what each app could access.