I read the comments before the link and thought this was a bit harsh, but reading that response I now feel the same way you do.

The reporter ALREADY provided a minimal example and Apple is like "yup we're going to keep changing things and you need to keep rerunning the code you sent us and reporting here because we won't bother to run your minimal example ourselves".

Just wow.

▲

tonyedgecombe an hour ago | parent [-]

Giving the Apple engineer (but not Apple) the benefit of the doubt I guess their policy is not to make any promises or announcements in that channel. They have probably said as much as they are allowed.

▲

voakbasda an hour ago | parent [-]

Forward looking statements can come from anyone and become sticky when considering security laws. Imagine everyone at Apple was sharing their full triage and timeline for every issue; one can then make informed decisions about their stock price, and investors could sue if those statements turned out to be misleading. At a certain point, the risk is too great.

	▲	marky1991 35 minutes ago \| parent [-]
		Ok, but even if that were true , it costs nothing to say "we'll let you know when we think we have fixed the issue so you can then retest" "Idk lol, it'll probably be fixed one day, keep testing and find out" is a pretty crappy response.