Apple Asks Supreme Court to Review App Store Contempt Ruling
Apple has requested the U.S. Supreme Court to review a contempt ruling related to its App Store practices. The ruling stemmed from a legal dispute with Epic Games, which led to changes in Apple's linking rules and fees. Apple argues that the contempt ruling was inappropriate and seeks to limit any court orders to only affect Epic Games.
- ▪Apple formally asked the U.S. Supreme Court to review a series of rulings regarding its App Store.
- ▪The Ninth Circuit Court of Appeals found Apple in contempt for violating a previous injunction related to payment options.
- ▪Apple contends that the contempt ruling was based on the 'spirit' of the injunction rather than a clear violation.
3 outlets in our directory ran this story. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
MacRumors files mainly under tech. We currently carry 340 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | MacRumors |
| Canonical URL | https://www.macrumors.com/2026/05/21/apple-supreme-court-epic-games-case/ |
| Publication time | Thu, 21 May 2026 14:58:21 PDT |
| Retrieval time | 2026-05-21T22:01:35.754Z |
| Last seen | 2026-05-21T22:01:35.754Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | N_mmh7ezkOat · 3 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Apple Asks Supreme Court to Review App Store Contempt RulingThursday May 21, 2026 2:58 pm PDT by Juli CloverApple today formally asked the U.S. Supreme Court to review the series of rulings that led to changes to App Store linking rules and fees in the United States. In 2021, Apple largely won its legal dispute with Epic Games, but Judge Yvonne Gonzalez Rogers ordered Apple to relax its anti-steering rules and let developers link to alternate payment options in apps. Apple complied, but charged a 12 to 27 percent fee on link-outs instead of its standard 15 to 30 percent fee. When taking into account fees from payment processors, there was little to no discount to developers, and few opted in. Apple also restricted button design, limiting developers to a single plain text link.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at MacRumors.
Discussion
0 commentsMore from MacRumors
