And after all that, my bug is closed as a duplicate of a newer bug: "Engineering has determined that your bug report (29280854) is a duplicate of another issue (29517144) and will be closed."
Sigh. > On Nov 23, 2016, at 13:48 , Rick Mann <rm...@latencyzero.com> wrote: > > >> On Nov 23, 2016, at 05:24 , Daniel Jalkut <jal...@red-sweater.com> wrote: >> >> Hi Rick - >> >>> On Nov 23, 2016, at 5:11 AM, Rick Mann <rm...@latencyzero.com> wrote: >>> >>> Anyway, thanks for helping me troubleshoot this. If I can come up with a >>> sample project, I will, but I'm currently swamped implementing throttling, >>> and once that's done, I'll have much less incentive to do the sample. >> >> I’m so sorry you’re suffering from this bug. I know it’s really frustrating >> especially when it seems obvious the problem lies outside your own code. >> >> I have had, many times, to reduce a problem to a smaller test case in spite >> of my assumption that “it would be obvious” to anybody who tested against my >> shipping app. At least half the time, however, the process of reducing the >> test case points to an “aha” caveat that reveals a problem in my own code. >> >> I’m not saying this is your own code, and Quinn even acknowledges that it’s >> probably in NSURLSession, but the issue appears to be unique enough to your >> own configuration (possibly a combination of client and server behavior) >> that it appears you are probably uniquely incentivized to push progress on >> the issue. >> >>> For once, Apple is going to have to reproduce a bug on its own. >> >> I think if you reconsider, you’d realize that reproducing this bug on their >> own would be far from the first time Apple had done such a thing. Remember >> that the teams at Apple are struggling to get through a massive amount of >> work, with tight deadlines, and onerous obstacles as well. > > In my experience, Apple automatically asks for a reproducible test case. In > my experience, most of those that I've provided have indeed been trivial. And > in my experience, the result of that is usually to be told my bug is a > duplicate of another, and then to not see it fixed even a year later. > > In this case, it is definitely more challenging, but I've outlined a way to > test it. Apple has a hundred billion dollars at its disposal. I have only me, > and a deadline. > > If Apple were to sincerely give it a try, then get back to me saying they > can't reproduce the problem, I'd be much more willing to do the work. But > honestly, after more than a decade of professional iOS development, it seems > my efforts are largely wasted. So you'll forgive me if I'm reluctant to spend > the time. > > > -- > Rick Mann > rm...@latencyzero.com > > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Macnetworkprog mailing list (Macnetworkprog@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/macnetworkprog/rmann%40latencyzero.com > > This email sent to rm...@latencyzero.com -- Rick Mann rm...@latencyzero.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/archive%40mail-archive.com This email sent to arch...@mail-archive.com
