I released a new version 6 days ago. I see some crashes in iTunesConnect analytics, but none in the crashes organizer, nor does my release even appear in the "version" dropdown within the crashes organizer.
Normally it takes a day or two after a release for crash reports to make their way into the Xcode Crashes organizer, and anecdotally I've seen the crashes appear in the Xcode Crashes organizer about the same time as in the iTunesConnect analytics website.
Interestingly, the previous versions still show in the "version" dropdown and I can see reports continue to trickle in for them. There is a steep decline in crash reports for that previous version, presumably as most folks have moved to the latest version.
On a new machine, with a fresh XCode install (but linked to the same developer account) I see the same behavior. Maybe it's a problem with my developer account?
Update 2016.09.01: Two months later, new releases are still not showing up in the releases dropdown automatically. The workaround posted below to manually add them has been working great, but hopefully I don't have to do it forever. I have to assume this is a problem with my local setup as this can't be happening to everyone. Let me know if you figure out a long term fix.
Update 2016.10.13: The work around isn't working for my most recent release. I again see crashes in ITC, but after manually adding an entry for the release in Info.json, I see "No crash information is available for this release."
Update 2016.10.15: I guess the work around is continuing to work, the crash reports were just delayed by an extra 48 hours.
Update 2016.1.20: At some point, (maybe around mid december, XCode 8.2?), I started to see new releases appear automatically again, and no longer have the joy of manually editing my XCode config data every time I push a build. Other than updating XCode, I can't think of any way I might have "fixed" it.
As the name suggests, the Xcode Organizer Window is built directly into Xcode, which means all you have to do is navigate to the menu bar, go to "Window," and click "Organizer" to launch.
Open the Console app, from Applications > Utilities in Finder. Select Crash Reports. Locate crash reports for your app in the list. Logs are listed by your app's binary name.
Developers do not have to use the latest version of Xcode to develop and publish apps to the Mac or iOS App Stores. In fact, you don't necessarily have to use Xcode at all. Having said all that, the latest release version of Xcode (9.4. 1) requires macOS High Sierra 10.13.
It's likely a bug with Xcode/ITC services. I filed a radar (#27277793) yesterday and was on ITC tech support today. If you're having this issue please report it to Apple and reference the existing radar (#27277793) so Apple can recognize we're having the same problem and prioritize a fix.
A workaround to get the crash reports for my latest release was to manually add a new entry in the crash organizers Info.json.
In: $HOME/Library/Developer/Xcode/Products/<bundle.id>
edit the Info.json and add a new entry to the beginning of the "productVersions" array based on the existing entries, but change the build number to whatever build the crash reports are for.
You also must update the appStoreStatus field depending on whether your app is in TestFlight or in the AppStore. appStoreStatus: 1
for TestFlight and appStoreStatus: 3
for AppStore.
After relaunching Xcode and going to the crashes organizer I watched as the last 6 days of crash reports came in.
Yay for human readable configuration data!
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With