Between February 16 and February 28, 2026, Apple published new age requirements for apps in Australia, Brazil, Singapore, Utah and Louisiana, and Angular fixed an XSS in its i18n handling. Here is what changed and what it means for your app and the WordPress site behind it.
Below is a quick summary table, then a section for each release covering what shipped, what it means for you, how we use it in WordPress builds, what it means for mobile apps and what to do next.
At a glance
| Release | Date | Type | Who should care | Action |
|---|---|---|---|---|
| App Store age requirements | Feb 24 | Policy | iOS apps rated 18+ or with loot boxes | Check ratings |
| Angular security advisories | Feb 25 | Security | Angular, Ionic Angular and SSR front ends | Update Angular packages |
Apple age requirements for Australia, Brazil, Singapore, Utah and Louisiana
What shipped
On February 24, 2026, Apple announced new age requirements for apps. Apple's post states:
- Apps rated 18+ cannot be downloaded in Australia, Brazil and Singapore unless the user is confirmed to be an adult
- Apps with loot boxes are rated 18+ in Brazil
- In Utah (from May 6, 2026) and Louisiana (from July 1, 2026), Apple shares age categories with developers through the Declared Age Range API
What it means for you
If your app is rated 18+, some users in those countries will not be able to download it. If you serve users in Utah or Louisiana, you can now receive their age category from Apple.
How we use it in WordPress builds
No WordPress change is needed.
What it means for mobile apps
Most AppPresser apps carry lower age ratings, so the download block does not affect them. We check the rating answers in App Store Connect during each App Store submission review.
What to do next
- Check your app's age rating in App Store Connect
- Decide whether you need age category data for Utah or Louisiana users
- Ask us before changing your rating answers
Angular security advisories
What shipped
The Angular team published these security advisories in this period:
- CVE-2026-27970 (high): XSS in Angular i18n, in @angular/core
What it means for you
These flaws are in the Angular framework, not in WordPress. They matter if you run an Angular front end, an Ionic Angular app or server side rendering in front of WordPress.
How we use it in WordPress builds
On headless WordPress front ends built with Angular, we update the @angular packages to the fixed version for the project's major line and rerun rendering, login and form tests.
What it means for mobile apps
Ionic Angular apps ship Angular inside the app, so a fix for code that runs in the app needs a rebuild and a new store submission.
What to do next
- Update to Angular 21.2.0, 21.1.6, 20.3.17 or 19.2.19 or later.
- Ask our mobile app team to rebuild and resubmit an affected app.
How AlphaWeb handles updates for you
Platform releases like these rarely change WordPress itself, but they change the servers, databases and app stores your site and app depend on. Our support and maintenance plans cover tested updates on staging first, then in production, and our WordPress security and hosting service keeps PHP, web servers and databases current.
Request a custom development quote, or tell us about your project through our Mission Brief.
Brief Us on Your Mission
Want to talk about a website, mobile app, migration or AI project? Fill out the Mission Brief and a specialist will follow up to schedule a call and put together a free quote.
