Testflight Crash Reports don't show up
I released an app to test users via testflight on iTunes Connect. One of my testers told me the app crashed, but I do not see any crashlog being generated that I could view in my organizer nor in itunes Connect. How can I debug this issue properly? I uploaded the archive with symbols and the correct version is being tested. Still there is not a report being sent to me.
Here's what I see on my side for a project I recently updated and pushed onto TestFlight.
The Xcode Organizer will show a "Crashes" tab along with Archives.
And in that Crashes tab, you can choose versions to look at from a popup menu.
Here's more information about the Crashes organizer from Apple.
As you can see, I couldn't find a version of my app with any crashes. Not to say that my code is perfect (ha ha), but I'm not 100% certain the TestFlight crash log downloading system is foolproof. Perhaps this is the reason why so many developers choose to use more explicit Crash Reporting frameworks like Crashlytics or Fabric.
- Math.Sin() gives incorrect value
- How to run my python script when the sunOS is start booting
- Express-session: not resetting cookie expiration on each request
- Getting a stack overflow exception when normalizing a vector
- Edit default summary function in R gives error for multiple variables
- What was a For loop? Why isn't it needed in R?
- How to use download button in shiny and save results in various formats (csv, texte, pdf, spss...)?
- Why are there two assignment operators, `<-` and `->` in R?
- lm()$assign: what is it?
- How to get the value of list(...) in R and S functions
- Design matrix for MLM from library(lme4) with fixed and random effects
- how to generate elements not included in my sample
- Create a matrix with gradually changing values without a for loop
- Emacs ESS and S-plus ( S+ ) 8.1 compatability
- How to lag date-index in a time-series in R?
- Nonlinear regression in R / S
- Calling R from S-Plus?