Ah, I see what you're saying. The thing is if it is a cut and dry violation it ought to be in principle possible to say so. And there have been features that were delayed and released and which function the same in the EU as elsewhere. So presumably the implementation is legal but plausibly wasn't.
Now there's a difference between building a feature and building interoperability. You have to actually work at it. And if you rush to do so on every feature:
1. You may modify features you didn't need to
2. You open yourself up to other countries demanding specific software changes
The simplest thing is just to make one version for the world, and wait for an ok. Big downsides to either rushing to release as is or rushing to make a change you may not need to make.
Well the question as to whether it’s a “cut-and-dried” violation depends on information Apple probably isn’t willing to share: is there a specific technical reason this technology can’t be enabled on third party headphones? If there’s a good reason (e.g. the AirPods have a chip in them that does processing on the signal without which it wouldn’t work), then it’s probably fine. If it’s just `if (headphones !== “AirPods)`, then that’s probably not