Install source and installer package
Apps can see which store installed them.
In one line
Can see which store installed it, like Google Play or a side loaded file
Apps can see which store installed them.
Shows sideloaded, beta or store installs. Used for fraud and update messaging.
What it can and can't do
What the user does: Nothing. It happens when the app starts up
It can
- Tell if it came from Google Play or another source on Android 11 or newer
- Check this to decide what to show you
- Learn a rough clue about the install source on iPhone
It cannot
- See which store installed other apps
- Know on iPhone with the same detail as Android
- Be sure the answer is true if the phone is tampered with
How it differs between platforms: Android 11 and newer names the installer. iPhone gives only a rough clue.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Supported | Partial |
| First version | Android 11 (API 30) | iOS 3.0 |
| Permission or entitlement | Not listed | none |
| Protection level | none | none |
| How access is granted | none | none |
| What the user sees | Not listed | Not listed |
| How long it lasts | Not listed | Not listed |
| How to take it back | Not listed | Not listed |
| Store policy | None listed | None listed |
| API | PackageManager.getInstallSourceInfo(): installingPackageName, initiatingPackageName, originatingPackageName | Environment production, sandbox or Xcode |
| Notes | API 30 | None |
Data you get
What comes back: Installer package or environment
Shape: string
How often: Static
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
installer | string | package ID | about 10 common values | exact |
Technical limits
- Low sensitivity
The story
What it is
Apps can see which store, or what other source, installed them.
For you
You never see it. An app knows if you got it from the official store, a beta, or a file. It may nag you to update from the store or refuse to run on a hacked copy.
For makers
Makers use it to spot sideloaded or repackaged apps and to decide which update message to show. It is useful for fraud and for cracked game copies.
Where you see it
| Type | Example | Apps |
|---|---|---|
| games | A paid game spots a cracked copy installed from a file and blocks it. | None named |
| banking | A bank app limits features if it was not installed from the official store. | None named |
| security | A security tool flags apps installed from unknown sources. | None named |
| developer | A team sees how many testers came from a beta channel. | TestFlight |
| ads | An ad network discards installs from unknown sources as fraud. | None named |
| media | A streaming app shows a store update link for the right store. | None named |
| enterprise | A company checks that a work app came from its managed store. | None named |
Risks
- Can block alternative stores
- Small tracking value
Android and iPhone in short
- Android: Android shows which package installed the app, from API 30.
- iPhone: Only partial. iOS exposes much less.
Good uses and abuse
Legitimate uses
- Detect sideloading
Known abuse
- Little
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 1 of 5 | How revealing the data is |
| Utility | 2 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 2 | Rough identifying entropy, when known |
History
- 2020-09, Android 11 (API 30): InstallSourceInfo with initiating package
Sources
How well checked: Based on official documentation.