Filename Breaks iOS, and That's Boring Now

A filename bug in Apple's iOS 26+ asset catalog system causes images named `highjump.png` to fail to appear in apps, because a function called `IBHashImageName` hashes asset filenames and returns `0` for `highjump`. The blogger behind the finding said that in late 2026 an LLM can now solve such closed-source binary bugs on request, and that this may mark the end of the dense technical write-ups on the site.

This Filename Breaks iOS, And That's Boring Now You can’t use an image named highjump.png in an iOS app. Go ahead, try it As long as you’re using the standard asset catalog system, on iOS 26+, highjump won’t appear. This post would normally be a long technical dive with a very tiny scrollbar, where we figure out how asset compilation works on Apple platforms, trace through three different binaries, and eventually run into the cause, after way more reverse engineering than you’d expect. But it’s late 2026, and if you ask an LLM to just solve the bug for you, they’ll do so, even in Apple’s closed-source binaries - eventually finding a function called IBHashImageName , which hashes asset filenames, and happens to return 0 for highjump , when then breaks things elsewhere. More than that, it’ll walk you through exactly how you can find that information yourself, if you want - filling in whatever gaps of knowledge you in particular happen to have. I think there’s still value to long technical posts, but if I wrote this one up… I’m actually not sure I’d read it myself anymore. I think there’s still a lot of interesting things to do on iOS, and that those things are more accessible than ever. But after some delightful years of really dense technical posts - it might be the end of tiny scrollbars on this site.