Urgent.News

What's breaking now, across thousands of outlets.

Tech

iOS 27.3’s redesigned Apple Health app requires newer iPhone model

iOS 27.3 will introduce an all-new Apple Health experience when it ships next month, but you’ll need an AI-compatible iPhone to get it. Here’s why. more…

iOS 27.3’s redesigned Apple Health app requires newer iPhone model

Apple has unveiled a major redesign for its Health app with the upcoming release of iOS 27.3, but users will need to be running an AI-compatible iPhone to access the new features. The revamped Health app, first announced in September alongside new Apple Watch models, brings several enhancements designed to provide a more personalized and informative user experience. These include a dedicated Insights tab, a Longevity tab, educational videos, and advanced at-home movement evaluations.

However, the new Health app experience is contingent upon Apple's Intelligence features, which necessitates the use of an iPhone equipped with AI capabilities. In practical terms, this means that users will require an iPhone 15 Pro or a newer model to take advantage of the revamped Health app. Users with older iPhone models or those who have disabled Apple Intelligence on their devices will find that the new Health features remain inaccessible.

Moreover, these forthcoming Health upgrades will initially be rolled out in select languages, further limiting the immediate availability of the upgraded experience. As Apple continues to integrate Apple Intelligence across its suite of applications, the Health app stands as a notable example of the company's commitment to leveraging AI to enhance user interaction and data insights.

Written by urgent.news from 9to5Mac's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Also reported by 1 other outlet

Every outlet that reported this, and when →

Read the original at 9to5mac.com →

More in Tech

Handle Empty Vector Search Results: Fresh Lexical and Web Recovery

The page says duplicate_detection_gap : to handle empty vector search results, the help center should fall back instead of accepting a record with no evidence.

  • System implements fallback methods for empty vector search results
  • Semantic search finds near-duplicates, rejects low-evaluation candidates
  • Keyword retrieval prioritizes recent information, web search as last resort

Fast Disks, Slow WAL Sync: Finding Linux Writeback Throttling

As described in the previous post , the primary now uses a high-I/O Ultra disk. Reads and writes took fractions of a millisecond, yet PostgreSQL WAL synchronization averaged 25-30 ms.

  • PostgreSQL WAL synchronization takes 25-30 milliseconds on ultra high-I/O disk
  • Linux writeback throttling causes delay despite disabling synchronous standby waits
  • HorizonDB avoids Linux throttling issue, achieving higher throughput

Cloud CI Email Tests Need an AWS Boundary

Email verification tests often fail for reasons that have nothing to do with the application. A shared inbox is slow, an old message is read by the wrong test, or a CI retry consumes a token that the first attempt already used. The result is a red pipeline and very little evidence about what really happened.

  • Email verification tests fail due to slow inboxes, wrong message recipients, or CI token reuse.
  • Proposed AWS boundary separates control, delivery, and evidence for test emails.
  • Fixture identity and run ID are given to CI job; fixture expires with job completion.

More from Tuesday 17 November →