Facebook's iOS app accesses the camera as users scroll their feeds; a workaround is to revoke the app's camera permissions; a patch is “already rolling out”
Context & Ripple Effects
The camera-access report extends a known pattern rather than starting one: back in 2015 Facebook's iOS app was already draining battery and using data in the background even with Background App Refresh off, and this week's finding shows sensor activity continuing while users simply scroll their feeds. The immediate remedies are user-side — revoke camera permissions — until Facebook's patch finishes rolling out.
What keeps this from being a one-off is how the same disclosure dynamics recur across Facebook's ecosystem: months later, Zoom would pull the Facebook SDK from its iOS app after its privacy policy failed to disclose SDK-driven data sharing, and Instagram would blame a mislabeled camera-indicator in iOS 14 Beta for reports that it was activating the camera. Each episode puts Apple's permission system in the role of referee.
First-order effects
- iOS users who scroll the feed get a concrete decision today: leave camera permissions granted and trust the rollout, or revoke them and lose in-app camera features until Facebook's patch lands.
Second-order effects
- Apps that embed Facebook's SDK inherit the reputational exposure — Zoom's removal of the SDK shows partners choosing to sever the integration rather than defend undisclosed data flows in their privacy policies.
Third-order effects
- If every sensor-access claim requires an app-vendor explanation, accountability migrates to the operating system itself — iOS 14's camera indicator, which Instagram blamed for a 'mistaken' report, previews a regime where the OS, not the developer, is the source of truth.
The trend: Mobile privacy enforcement is shifting from developers' self-disclosure toward OS-level signals that surface sensor use directly to users and force patches on the platforms caught.