Yesterday I told you that Pod2G published on his blog an article asking for our help in developing a jailbreak solution for the new iOS 5.1. He asked users to email him information about crashes encountered when using iOS, but unfortunately he did not receive what he requested. Pod2G emphasized the fact that we send crashes for nothing if we don't also send the method by which that crash was obtained and decided to close the entire project for the time being. Pod2G will resume the idea in an article that it will publish in the near future and will explain in detail everything it needs to speed up the development process of a jailbreak solution.
Crash reports are useless without explanations on how to reproduce them !!! 🙁
OK, let's forget this crash report idea. My mail box is flooded with useless stuff 😉 My bad, I'll write a more detailed article.
Thanks to all who reported me bugs. I'll specify what is a good crash and what is not. Sorry for wasting your time.
Chronic Dev Team received over 10 million crash reports from users, but unfortunately he failed to use them because he did not have the described method by which those crashes were obtained. In the end, Pod2G's idea is good, but with hundreds of thousands of users in front of them who don't know how to deal with the situation, things can easily get out of control.
