4 ms·
> I'm not sure what you mean by "Without tooling". Well, I'd start with Xcode and static analysis. If that fails, Apple says this is triggered by ATS and ATSUI
by arcticbull 3y ago
> I'm not sure what you mean by "Without tooling".
Well, I'd start with Xcode and static analysis. If that fails, Apple says this is triggered by ATS and ATSUI so I'd probably start with something like grep to see if I could track down a recursive dependency. [1] I wouldn't start deleting code at random from my codebase.
Given this is just a nuisance I'd then file a radar.
[1] https://medium.com/nuclei-technology-blog/how-to-check-your-application-is-using-any-of-the-deprecated-apple-apis-2bf6ea67f47b https://medium.com/nuclei-technology-blog/how-to-check-your-...
- lapcat 3y ago> Apple says this is triggered by ATS and ATSUI That's what Apple says but unfortunately it's not entirely true: https://news.ycombinator.com/item?id=36660932 https://news.ycombinator.com/item?id=36660932 > Given this is just a nuisance I'd then file a radar. They're called Feedbacks now, and if you read to the end of the blog post, you'd see that Hockenberry did indeed file some. But filing a bug report isn't any kind of solution to a problem. Apple only fixes a small subset of all bug reports.
- arcticbull 3y agoI strongly suspect Apple will either change the alerting behavior, or change the documentation around it. Either way is fine, IMO. > They're called Feedbacks now. Yeah, I'm not going to stop calling them radars lol.
- lapcat 3y ago> I strongly suspect Apple will either change the alerting behavior, or change the documentation around it. Which is exactly the point of the submitted blog post: Apple needs to change this. But here in the commentary we have people talking down to the author and others, suggesting they're somehow ignorant and "not using the tools".