All Blog News

Apple’s Indian supplier Electronics announced on Tuesday that the state pollution control board has dropped its scrutiny of the company’s iPhone components plant after the firm addressed concerns over contamination.

The Tamil Nadu pollution control authority had earlier warned of a potential forced shutdown unless it explained government findings that wastewater discharge from the plant had contaminated open wells in adjacent agricultural lands, Reuters reported on Saturday.

Reuters:
‎

On Tuesday, told Reuters in a statement that the Tamil Nadu Pollution Control Board had confirmed that the company “has satisfactorily addressed all queries mentioned” in the warning notice and “dropped any further course of action on this ‌issue.”

said in its ​statement ​that the pollution board has confirmed “that the reports of ​its own analysis of recently collected water ‌samples from Electronics’ manufacturing facility in Hosur, Tamil Nadu do not indicate any contamination”.

added that it had commissioned an independent analysis through an accredited laboratory, the results of which indicated that all the parameters were within prescribed limits, and it submitted a formal response including those results to the pollution authority.

‎

‎

.

Source link: https://macdailynews.com/2026/06/16/india-pollution-board-drops-scrutiny-of-apple-supplier-tatas-iphone-parts-plant/

Apple’s first developer betas are rarely known for their polish, but iOS 27 (and macOS 27) appear to be breaking that rule. In this personal account, Ben Lovejoy explains why he took the unusual step of installing the initial betas on his daily-driver iPhone and MacBook Air — and how their unexpected stability tells a bigger story about Apple’s extended internal testing and the long road to delivering on its ambitious Apple Intelligence promises.

Ben Lovejoy for 9to5Mac:
‎

What has struck me about both betas is their remarkable stability. I haven’t yet encountered a single app that either crashes or significantly misbehaves, and the number of bugs I’ve discovered to date are both few in number and entirely innocuous. I’ve found way more significant bugs in far later dot versions of previous developer betas.

I’m absolutely not advocating that anyone else should follow my example – it remains a bad idea as a matter of principle – but I do think it tells a story.

Specifically, it suggests that Apple has been using iOS 27 for a far more extended period of time within the company than is typical before the first developer release. That gels with the idea that the company genuinely believed it would be ready for release not long after the launch of the iPhone 16.

Apple was accused at the time of advertising vaporware, but it now looks much more likely that it did have working versions of the features it advertised, but decided they were too buggy to be released on the planned schedule. Of course, if it was too buggy to be released even as a developer beta, then the company should never have advertised the features, but it does put rather a different complexion on the situation. This was over-optimism, not deception.

‎
Do not install beta operating systems on mission critical hardware, but, by all means, if you have a testing device that’s supported have at the betas. More info: beta.apple.com

‎

.

Source link: https://macdailynews.com/2026/06/16/apples-initial-ios-27-and-macos-27-betas-are-remarkable-stable/