How to Stop Symbolicate Adding "<Redacted>" Pieces to iOS Crash Log

How to stop symbolicate adding redacted pieces to iOS Crash Log

I had the same problem and got rid of messages by deleting all iOS 6.0 (including beta) data from ~/Library/Developer/Xcode/iOS DeviceSupport.

Now, symbolicate uses the symbol data stored at /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport/6.0 (10A403)/
instead of the stored symbol data in user library.

iOS Crash Symbolication

It turns out that I didn't have the system framework symbols for iOS 11.0.3 locally, so symbolicatecrash wasn't able to symbolicate the system framework symbols.

I was able to see that I didn't have the necessary symbols by referencing the answer to this question: Atos does not symbolicate system frameworks/libraries properly

Once I installed iOS 11.0.3 on my device and connected my device to Xcode, the symbols for iOS 11.0.3 were automatically downloaded and symbolicatecrash started working for the entire crash log.

Application crashes after install from Appstore. Google Analytics sent me crash report of instaces redacted

Since the debug symbols (dSYM) are removed from the released version of app, and Google Analytics don't have the dSYM, so they could only provide the redacted crash reports.

One possible solution is to check the crash report on iTunes Connect, if there's some reports available, you can download and re-symbolicate them by yourself.

For detailed instruction of re-symbolication, check http://aasims.wordpress.com/2011/05/10/how-to-symbolicate-iphone-crash-reports/ this.

Basically, you will use symbolicatecrash command, and you will need dSYM of the released app. You should be able to find the dSYM folder in the archived app (APP_NAME.xcarchive/dSYMs).

--

And you can consider integrating with TestFlight SDK which supports auto-symbolication if you provide the dSYM in your next release.

iOS App Error: I screwed up somewhere in date calculation

It's definitely a bug. You can crash the iPad's calendar app with the following:

1. Create an event, recurring every day with recurringEnd some days in
   future.
2. Change the location of the second occurrence and save it for
   all future events.
3. Delete first occurrence and do select only this event. BAM!

This does not happen, when the location change starts with an occurrence after the second OR when delete all future events was chosen.
When you do the steps in code, your app crashes with the wounderful "I screwed up..."

A short work around is:

[eventStore removeEvent:firstEvent span:(firstEvent.isDetached ? EKSpanFutureEvents : desiredSpan) commit:YES error:nil];

---

Related Topics