Archive for May 19, 2025

Monday, May 19, 2025

Epic Files Motion to Enforce Injunction

Epic Games:

Yesterday afternoon, Apple broke its week-long silence on the status of our app review with a letter saying they will not act on the Fortnite app submission until the Ninth Circuit Court rules on the partial stay. We believe this violates the Court’s Injunction and we have filed a second Motion to Enforce Injunction with the US District Court for the Northern District of California.

We’ve been transparent with Apple about our intentions while they’ve used app review and notarization as a pretext to circumvent the Court’s injunction and the EU Digital Markets Act. Apple’s “solution” required us to submit two versions of Fortnite, in violation of their guideline that developers shouldn’t submit multiple versions of the same app. That’s not the standard Apple holds other developers to and it’s blocking us from releasing our update in the EU and US.

Tim Hardwick (ArsTechnica):

Epic claims Apple is in contempt of the judge’s April order that restricted Apple from rejecting apps over their use of outside payment links. Epic argues that Apple’s refusal to review its Fortnite submission until after a pending Ninth Circuit ruling amounts to retaliation for its legal challenges.

According to a letter from Apple shared by Epic, Apple stated it “won’t take action on the Fortnite app submission until after the Ninth Circuit rules on our pending request for a partial stay of the new injunction.” Epic contends this delay violates Apple’s previous assurances to both Epic and the court that it would approve Fortnite if the app complied with Apple’s guidelines.

The motion (PDF):

On May 1, 2025, Epic notified Apple of its intent to avail itself of the Injunction and the new Guidelines. Specifically, Epic notified Apple that Epic would use the same developer account that it uses to distribute the Epic Games Store and Fortnite in the European Union to submit Fortnite for App Review in the U.S. Epic invited Apple to provide it with further direction if Apple preferred that Epic submit Fortnite for review another way (e.g., through a different developer account). On May 2, 2025, Apple—through its outside counsel— stated that if Epic wanted to submit using the process Epic had outlined, it should do so.

On May 9, 2025, Epic submitted for review a build of the Fortnite app that fully complies with all applicable App Review Guidelines, through a developer account in good standing. […] Apple did not act on Epic’s submission for five full days, despite representations that it generally reviews 90% of app submissions within 24 hours. Then on May 15, 2025, Apple informed Epic via a letter that it “has determined not to take action on the Fortnite app submission until after the Ninth Circuit rules on [Apple’s] pending request for a partial stay of the [Contempt Order]”. […] In the letter, Apple did not suggest that any version of Fortnite submitted for review was in any way non-compliant with any of Apple’s policies, rules or Guidelines.

Mark A. Perry (PDF):

As you are well aware, Apple has previously denied requests to reinstate the Epic Games developer account, and we have informed you that Apple will not revisit that decision until after the U.S. litigation between the parties concludes. In our view, the same reasoning extends to returning Fortnite to the U.S. storefront of the App Store regardless of which Epic-related entity submits the app.

[…]

I understand that the recent submission by Epic Sweden included a proposed Fortnite app for the U.S. storefront of the App Store as well as for alternative distribution in other geographies. To prevent our discussions surrounding the U.S. storefront of the App Store from impacting Fortnite in other geographies, please withdraw that submission and resubmit the app without including the U.S. storefront of the App Store (this can be accomplished by unchecking the relevant box).

M.G. Siegler:

I believe that Sweeney knew that Epic wouldn’t and couldn’t win their legal claims against Apple, at least not in full. But in just filing them, they started a process which has snowballed into a blizzard for Apple. Both around the world and now at home as well. While that has largely been political, it’s also increasingly moving down the chain.

Apple developers having long been annoyed with the company about various elements of App Store development, and now Epic’s lawsuit, and political fallout, gives them more cover and hope for real change. I don’t believe this has yet translated to consumers in any meaningful way, but that doesn’t mean that it won’t. If every single headline turns into yet another thing Apple is doing to say, keep Fortnite off the App Store, years later, these things tend to have a cumulative effect. Even if Apple is in the right in that particular case, legally. The public doesn’t care about that. All they see is that Apple continues to block a developer from the App Store.

[…]

Apple’s actual stance on the matter – via lawyers – also sounds fairly reasonable. They simply would wish to not rule on allowing Epic (and thus, Fortnite) back in the US App Store until all legal proceedings between the two are final. Epic was trying to use a loophole created because of the unique situation in the EU with regard to the DMA and third-party app stores, but it was never going to fly in the US. It’s pretty black and white. Epic – and all their affiliates – are banned.

There are sort of two tracks to this story: what Apple has said and done and what its legal rights are.

On the first, Apple kept saying, in public and directly via Tim Cook in court, that if only Epic would submit an app that followed the rules, that Apple would approve it. At some point, it changed its mind and added the stipulation that this would only be after all the appeals were over. Then we have Epic saying that on May 2 Apple suggested that Epic submit Fortnite for the US App Store via its Swedish account. And on May 15 Apple asked that this submission be withdrawn. Apple considers Epic to still be banned from the developer program in the US.

As to the legal rights, I think there two questions. First, does the judge’s order that Apple must immediately comply with the anti-steering also imply that Epic gets to take advantage of such? On the one hand, I didn’t see anything in the order saying that. On the other hand, it would be ironic if Epic ended up ensuring these rights for everyone but themselves. And second, does Epic Sweden, with an account in good standing, albeit perhaps only due to DMA threat, have rights as a European company to submit apps to the US App Store? Or is it, as the US court found, subject to the lawful ban of Epic US?

The other interesting question is, what exactly did Apple say to Epic on May 2?

Jeff Johnson (Mastodon):

Epic’s May 16 court filing includes a declaration from Epic’s lawyer, who recounts a phone conversation with Apple’s lawyer:

On May 2, 2025, Mark A. Perry, counsel for Apple, called me about the Fortnite submission. Mr. Perry stated that because of the litigation between Epic and Apple, the submission had been escalated to his attention. He told me that Apple could not comment on whether the proposed Fortnite build would be accepted because Apple had not yet received it for review, but that if Epic wanted to submit the build using the Epic Games Sweden AB account, Epic should go ahead and do so.

I want to emphasize two crucial parts of that conversation:

  1. “Apple could not comment on whether the proposed Fortnite build would be accepted”
  2. “if Epic wanted to submit the build using the Epic Games Sweden AB account”

Apple did not unqualifiedly suggest that Epic go ahead and submit Fortnite for the US App Store. Epic had already stated their intention to do so, and Apple was simply approving (or at least not objecting to) that specific action, without giving any indication of whether the submission would be approved for the App Store.

In other words, Epic was implying that Apple reneged again, but it appears that Apple just told them to submit the app without giving any specific assurances.

One way to interpret this is that if Apple says, “We can’t promise anything, but <hint> you should submit it,” there’s an implication that it would be worth your while to try. That’s how normal conversations work. If I knew it would just waste your time, I would tell you not to submit it.

But there is also a reading that’s more legalistic than pragmatic, where Epic asked a question and Apple replied with two independent settlements that are true but useless: “Yes, it’s possible for you to submit. We won’t say what will happen if you do.” This is, by the way, pretty much what they say to normal developers all the time. If you ask whether something that want to do is allowed under the guidelines, Apple says to write the app, submit it, and then find out.

Previously:

Slow TestFlight Beta App Review

Craig Hockenberry:

We’ve entered day 10 of waiting for a TestFlight beta app review on macOS. Have tried all the tricks, like submitting new builds, but there has been absolutely no movement.

While Apple is doing everything it can to maintain the tight control it has over the App Stores and a huge revenue stream, we’re out here just trying to get some volunteers to test our software. And failing.

This is bullshit that no developer on any platform should have to deal with. Bureaucracy for its own sake.

Previously:

Rust at 10

Graydon Hoare (Slashdot):

Rust turns 10 today, or at least it’s been 10 years since the 1.0 release. In this decade (and the near-decade of development before!) it has undergone growth and change I can barely comprehend the scale of. To say I’m surprised by its trajectory would be a vast understatement: I can only thank, congratulate, and celebrate everyone involved. It is deeply inspiring to have watched all that’s happened over that time and reflect on it from today’s vantage point.

While it’s tempting to talk about Rust’s journey in terms of the growth of “an idea” – perhaps starting from my amusing frustration with a broken elevator in 2006, as chronicled in this MIT technology review article – I think doing so misses the bigger picture.

In my view, Rust is a story about a large community of stakeholders coming together to design, build, maintain, and expand shared technical infrastructure.

[…]

Importantly: since all of this was done in the post-1.0 environment, every single change passed an exhaustive testsuite, and every release was regression-tested against a significant fraction of the public crate ecosystem, and with very few exceptions any change that broke existing code was rejected. As the 1.0 release announcement promised, Rust remained stable without stagnating. Existing code, in almost all cases, just kept humming along, like good infrastructure should.

The Rust Release Team:

Thank you to the myriad contributors who have worked on Rust, past and present. Here's to many more decades of Rust! 🎉

Niko Matsakis:

As part of RustWeek there was a fantastic celebration and I had the honor of giving some remarks, both as a long-time project member but also as representing Amazon as a sponsor. I decided to post those remarks here on the blog.

Steve Klabnik:

I’d instead like to reflect a bit on a comment I saw on the internet the other day:

[Rust is] not a great hobby language but it is a fantastic professional language, precisely because of the ease of refactors and speed of development that comes with the type system and borrow checker.

Patrick Walton, one of the earliest contributors to Rust, had this to say:

I never thought I’d live to see the day when someone would say this. The first 5 years of Rust were all “this is interesting for hobby projects but nobody will ever adopt this in industry”.

Kobzol (via Dominik Wagner):

The widget below visualizes how the error messages evolved over time.

[…]

But I think that ultimately, the most interesting thing about this is the evolution process of these messages itself, which demonstrates that a lot of effort has to be put into the messages to make them really good. To someone, it might seem like these messages are somehow automatically derived from the compilation process, and we get them “for free”, but that couldn’t be further from the truth. It is the result of a continuous design, implementation, review and testing effort that has been performed by hundreds of individual contributors over the span of more than ten years.

Previously: