Public Crash Information

[Sherlouk]

Now that we have had a few crashes 😢 I wonder if there's a way we could make the information shared in GitHub? I know there are services out there, but would require further SDKS 👎

Just looking at the network requests Xcode makes when you request them internally, and wonder if we could use it?

Root: https://crashwebservices.apple.com

GET /api/v2/crashes/top/1252320249/com.whoisryannystrom.freetime/1.12.0/1137/iOS?sortedBy=uniqueDevicesCount&isBeta=false JSON response returns an array of crashes (topCrashes) which each have an ID (crashPointId)

GET /api/v2/crashpoint/1252320249/com.whoisryannystrom.freetime/1.12.0/1137/iOS/{{crash id}}?isBeta=false&startDate=2017-10-21&endDate=2017-11-04 JSON response contains OS numbers, stack trace, other info

Obviously can then use the GitHub API to auto-post, and all those requests need to be authorised with access tokens but I believe fastlane have a lot of work around the iTC APIs so believe it should be doable

🤔 Feel like it would be a nice tool for open source communities, a possible new repo in the GitHawk org if it becomes functional?

[BasThomas]

I want to look into this. Stay tuned :)

[Sherlouk]

FWIW with Crashlytics this might not be 100% necessary

[BasThomas]

I know, still curious 😇

[BasThomas]

I have some news regarding this - we've open sourced crep, a tool to create crash newsletters. I want to look into the possibility of adding iTunesConnect as a crash source, as well as a plugin or similar to post to GitHub!

[rnystrom]

@BasThomas oh man if we could make a GitHawk status report automated, that’d be incredible. Imagine pulling download numbers, impressions, crashes, and daily users and spitting out a weekly report. Automatically gen a blog post maybe?

_{Sent with GitHawk}