Apple says Consumer Reports' battery test had disabled Safari cache in developer settings, which triggered an obscure bug that has since been patched
Romain Dillet / TechCrunch :
Context & Ripple Effects
Apple is disputing Consumer Reports' battery test results rather than accepting them, arguing the tester's own configuration — a disabled Safari cache in developer settings — triggered an obscure browser bug, which Apple has now patched. It follows a 2016 Safari crash fix on iOS and OS X, so the browser keeps surfacing as the weak point when iPhones are pushed through non-standard usage.
The rebuttal also fits a recognizable Apple playbook: when third-party findings look bad, the company attacks the test methodology first, as it later did with an iPhone brute-force passcode report it dismissed as incorrect testing. Whether reviewers or vendors control the narrative after a bad benchmark is becoming the real contest.
First-order effects
- Consumer Reports' battery conclusions are undermined at the source: the tested configuration was non-standard, forcing the publication to re-examine its methodology before standing by any numbers.
- Apple ships a patch for the obscure Safari bug, closing the specific condition under which the disputed results were produced.
Second-order effects
- Testing labs face pressure to disclose and lock down device settings — developer toggles like cache state become audit points, since an unreported configuration change can invalidate an entire review.
- Each successful methodology rebuttal lowers the cost for Apple to contest future unfavorable findings, raising the evidentiary bar reviewers must meet before publishing.
Third-order effects
- If the pattern holds, smartphone reviews converge toward reproducible, vendor-verifiable test protocols, with disputed benchmarks resolved by patch notes and configuration logs rather than dueling press statements.
- Safari and WebKit repeatedly appear as the failure surface when devices are stressed outside normal use, keeping browser hardening on Apple's maintenance agenda independent of security disclosures.
The trend: Consumer hardware testing is shifting toward contested-benchmark dynamics, where a vendor's ability to attribute bad results to tester configuration shapes what evidence the public ultimately sees.