Like @Max suggested, it definitely happens around guard utilizing the same outer scope var name for the local scope. It's incredibly difficult to reproduce though. I've ran into this a few times now, and it's always around refactor changes, specifically variable name changes around these scopes. It feels as if precompiled/cached/magic fails to recognize the change and then is unable to bust the cache. The stack trace seems to drop you off somewhat near recent changes that have been done, but doesn't give you any other hints. Compiler isn't going to give you any hints either, sounds like a brute force trial and error where you start looking for your wallet in the microwave, or debugging purely off superstition. So thanks and sorry to ya'll who were able to track this down.

It has to be something trivial in the headers. If you look, snapchat.com fails, facebook.com succeeds. If you look at curl -v https://facebook.com/.well-known/apple-app-site-association Snippet of headers from facebook < HTTP/2 200  < content-disposition: inline;filename=apple-app-site-association < content-type: application/json Snippet of my own headers (failing), you can see my load balancer is also injecting charset in content-type < HTTP/2 200  < server: awselb/2.0 < date: Wed, 15 Sep 2021 21:54:35 GMT < content-type: application/json; charset=utf-8 Snap's content-type is just wrong < HTTP/2 200  < date: Wed, 15 Sep 2021 21:58:09 GMT < expires: Sun, 14 Nov 2021 21:58:09 GMT < cache-control: public, max-age=5184000 < etag: "AHj-xA" < x-cloud-trace-context: 90deb7ca85c66e719276245d1263ea3a < content-type: application/octet-stream < server: Google Frontend Reddit is passing with < HTTP/2 200  < retry-after: 0 < content-type: application/json