Extended virtual addressing
Lets an app use a much larger virtual address space.
In one line
Can use a larger memory address range on iPhone, but not on Android
Lets an app use a much larger virtual address space.
Not about people, but part of the entitlement tier: some capabilities are just a switch in the app.
What it can and can't do
What the user does: Nothing. The developer turns on a setting before the app ships
It can
- Map more memory than the default limit on iPhone
- Handle very large files or models in heavy apps
- Use it with no prompt after Apple approves the setting
It cannot
- Turn it on from Android; 64 bit apps already have a large range, with no switch
- Use more actual memory than the phone has
- Gain extra access to your data
How it differs between platforms: This setting exists only on iPhone. On Android it is not needed.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Not supported | Supported |
| First version | Not available | iOS 15 |
| Permission or entitlement | Not listed | com.apple.developer.kernel.extended-virtual-addressing |
| Protection level | none | entitlement |
| How access is granted | not-exposed | entitlement |
| What the user sees | Not listed | No prompt; capability in Xcode |
| How long it lasts | Not listed | Tied to provisioning |
| How to take it back | Not listed | n/a |
| Store policy | None listed | None listed |
| API | Not listed | Xcode capability |
| Notes | 64 bit processes already have a large address space; no switch | Enables address space beyond default limits |
Data you get
What comes back: Address space limit
Shape: none
How often: static
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
limit | integer | bits | default 47 bits larger with entitlement | Not listed |
Technical limits
- Capability only; no user prompt
The story
What it is
A switch that lets a big app use much more memory address space.
For you
You will never see it. It simply helps big apps like large games, video editors or maps load huge files without crashing.
For makers
It is a technical switch in the app's settings. Makers turn it on when their app maps big files or large worlds into memory. It does not collect any data about you.
Where you see it
| Type | Example | Apps |
|---|---|---|
| games | An open world game maps a huge world file into memory so it can stream it smoothly. | None named |
| creative | A video editor opens a very large project without running out of address space. | None named |
| maps | A map app loads a large offline map file as one piece. | None named |
| ar-vr | An AR scene app holds big 3D scans in memory while you scan a room. | None named |
| developer | A developer who gets random memory errors tries this switch first. | None named |
Risks
- No privacy impact
- Can mask poor memory use
Android and iPhone in short
- Android: Android has no matching entitlement.
- iPhone: Needs an Apple entitlement, with no prompt to you.
What the platform says
- Apple: Extended Virtual Addressing entitlement. Developer rule: apps with large memory needs can ask for a bigger virtual address space.
Good uses and abuse
Legitimate uses
- Large games
Known abuse
- None
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 | 1 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2021-09, iPhone iOS 15: Extended virtual addressing introduced
Related capabilities
Related
- Increased memory limit. Can ask for more working memory for heavy tasks, with no prompt
Sources
How well checked: Inferred from related behavior.