Where to Find TestFlight Crashes (Without Xcode)
Where do you see your TestFlight crashes before they cost you one-star reviews? In this tutorial, Appi opens App Health in Appalize and walks through all three tabs on a real app: Crashes, Tester feedback, and Performance & power. You'll see how to filter crashes by device and iOS version, open the full log, match a tester's note to its build, and compare hangs, launch time and disk writes between two builds.
Watch on YouTubeIn this video
Open in Appalize
The screens this lesson walks through (sign-in required).
Transcript
The narration, with timestamps. Select a time to jump there.
Where TestFlight crashes live
0:00 Where do you see your TestFlight crashes before they cost you one-star reviews? 0:04 Not in Xcode Organizer. 0:06 On this screen. 0:07 Crashes, tester feedback and performance, in three tabs. 0:11 First, pick the app you want to check.
Pick your app (App Store Connect API key)
0:13 Open App Health and click the app picker. 0:16 I'll pick Toddly, a kids learning app from our team. 0:20 Everything on this page comes through your App Store Connect API key. 0:24 You connect it once, and Appalize reads the rest. 0:27 Small app, or only a few testers? 0:29 Some tabs may stay empty. 0:31 That's normal, not a bug. 0:33 With the app selected, start with the crashes.
Crashes: device and iOS filters, View log
0:36 Open the Crashes tab. 0:37 These come from your TestFlight testers. 0:40 Filter by device, then by iOS version. 0:43 A crash on one iOS version? 0:45 Check what changed there. 0:47 Click View log. 0:48 Read the first lines under the crashed thread. 0:50 Your app's name marks your code. 0:53 Common mistake: fixing the newest crash first. 0:56 Fix the one that repeats. 0:58 The log shows where it broke. 1:00 Your testers tell you what they were doing.
Tester feedback: match the build number
1:02 Open Tester feedback. 1:04 Each card is something a tester sent from the TestFlight app. 1:07 You get a screenshot, their comment, the build number and the device. 1:11 Appi tip: match the build number here with the build in the crash list. 1:15 Same build, same device? 1:17 Now you have the steps behind the crash. 1:19 Crashes are loud. 1:21 Slow launches and hangs are quiet, so check them next.
Performance & power: hangs, launch time, disk writes
1:24 Open Performance and power, then click All builds and pick one. 1:29 This is Apple's own data for that build. 1:32 Hangs: the app freezes and stops responding. 1:35 Launch time: how long it takes to open. 1:37 Disk writes: how much it saves to storage. 1:40 Now pick the build before it and compare the two. 1:43 Look at the direction, not the decimals. 1:46 Did one number jump after a release? 1:48 Then start your search in that release. 1:50 Before you trust these numbers, know where each one comes from.
Where the data comes from (and why it's not real time)
1:54 Here's the rule. 1:55 This page has two sources. 1:57 Crashes and feedback come from your TestFlight testers. 2:00 Performance metrics come from devices that agreed to share data with Apple, and that includes App Store users. 2:07 Apple collects it and combines it on its servers first. 2:10 So it's not real time. 2:12 A new build needs some time before its data shows up. 2:15 No Appalize? 2:16 The same data lives in Xcode Organizer, and in App Store Connect under TestFlight, then Feedback. 2:23 Most of this starts in TestFlight, so that's our next stop.
Recap and next: TestFlight
2:27 If you only remember one thing: open this page before every release. 2:31 Read the crash log. 2:32 Match the tester note to its build. 2:34 Compare the new build with the last one. 2:37 Next, I'll show you TestFlight in Appalize. 2:39 All the tutorials are at appalize.com/tutorials.
Try it on your own app
Every tutorial shows a real Appalize screen. Sign up free and follow along with your own app.