#12
Read increased-limit entitlement from profile
What
MemoryReport.hasIncreasedLimit was a hardcoded true STUB. It now answers from embedded.mobileprovision: crate is always signed for development, so the profile ships in the bundle and lists each entitlement it grants. A byte scan for the entitlement name (it appears only in the profile's entitlement dictionary); no CMS decode.
Why
Issue #7's reporter signed with a re-signing tool that dropped the entitlements, got 2 GB / 128 MB, and the app's own Settings still claimed the increased limit was on. That mismatch is what sent them hunting for a limitation that doesn't exist in crate. With this, Settings shows the truth for any signing method.
Testing
- Whole-app IPA build on the repo's
ipaworkflow, run on my fork against this commit: success (Xcode 27.1 runner). - On-device verification pending; the only runtime surface is the Yes/No row in Settings > Memory.
Verified on iPhone Duo (iOS 27.3 Beta 2): signed with iloader (entitlements taken from the account's provisioning profile) and Settings > Memory shows Increased memory limit: Yes, VM limit 6 GB on an 11.3 GB device.