Different teams in our company use Xcode crash statistics.
OK. I recommend that, in future, you coordinate your efforts internally. Posting many copies of the same question is a waste.
With regards your technical question, I discussed this issue with DTS’s crash report specialist and we have a few points to share. Let’s start with this:
we can get the detailed crash data in a specific app version and on a
certain day through the path Xcode/.../crashes/Appstore/***.xcrashpoint/distributioninfo/.../info.json
To be clear, the format of an .xcrashpoint document is not considered API. Those documents are created by Xcode for the benefit of Xcode. If you build tools that rely on their format, problems like this will crop up from time to time.
It sounds like you’re building some sort of diagnostic automation system. Doing that by piggybacking on top of Xcode’s .xcrashpoint files is not something we recommend. It would be better to get that information from the source, via the App Store Connect API.
The only fly in that ointment is that this API does not have a mechanism for returning crash reports. We have a bug on file asking for that (r. 40950129) but I have no info to share as to when that’ll happen.
Pending that, you have a couple of potential workarounds:
-
You can collect crash reports on device using MetricKit. One nice feature here is that, starting with iOS 15, MetricKit delivers such reports promptly. See WWDC 2021 Session 10181 Ultimate application performance survival guide for more on that.
-
You can continue to rummage around in .xcrashpoint documents but build your code more defensively. For example, rather than look at detailed info in the document, you could instead look for all crash reports and then do your own aggregation.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
