ThePain/Swiftgram
1
0
Fork 0
mirror of https://github.com/Swiftgram/Telegram-iOS.git synced 2025-07-16 08:19:23 +00:00
Code Issues Packages Projects Releases Wiki Activity

Improve crash reporting troubleshooting documentation

Browse Source
This commit is contained in:
Andreas Linde 2012-08-06 17:14:05 +02:00
parent 6d79351364
commit 7af9c7861f
2 changed files with 22 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
docs/Troubleshooting-Crashes-Dont-Appear-template.md → docs/Troubleshooting-Troubleshooting-Crash-Reporting-Not-Working-template.md
View File

@ -1,14 +1,26 @@
## Crashes Don't Appear
## Crash Reporting is not working
This is a checklist to help find the issue if crashes do not appear in HockeyApp:
This is a checklist to help find the issue if crashes do not appear in HockeyApp or the dialog asking if crashes should be send doesn't appear:
1. Check if the `BETA_IDENTIFIER` or `LIVE_IDENTIFIER` matches the App ID in HockeyApp.
2. Check if CFBundleIdentifier in your Info.plist matches the Bundle Identifier of the app in HockeyApp. HockeyApp accepts crashes only if both the App ID and the Bundle Identifier equal their corresponding values in your plist and source code.
3. Unless you have set `[BITCrashManager setCrashManagerStatus:]` to `BITCrashManagerStatusAutoSubmit`: If your app crashes and you start it again, is the alert shown which asks the user to send the crash report? If not, please crash your app again, then connect the debugger and set a break point in `BITCrashManager.m`, method `startManager` to see why the alert is not shown.
4. Check if the code is really executed by adding an `NSLog` statement.
5. If you are using `#ifdef (CONFIGURATION_something)`, make sure that the `something` string matches the exact name of your Xcode build configuration. Spaces are not allowed!
6. Remove of at least disable any other exception handler or crash reporting framework.
7. If there an older version of PLCrashReporters framework `CrashReporter.framework` added to the project, remove it.
6. If it still does not work, please [contact us](http://support.hockeyapp.net/discussion/new).
2. Check if CFBundleIdentifier in your Info.plist matches the Bundle Identifier of the app in HockeyApp. HockeyApp accepts crashes only if both the App ID and the Bundle Identifier equal their corresponding values in your plist and source code.
3. Unless you have set `[BITCrashManager setCrashManagerStatus:]` to `BITCrashManagerStatusAutoSubmit`: If your app crashes and you start it again, is the alert shown which asks the user to send the crash report? If not, please crash your app again, then connect the debugger and set a break point in `BITCrashManager.m`, method `startManager` to see why the alert is not shown.
4. Enable the debug logging option and check the output if the Crash Manager gets `Setup`, `Started`, returns no error message and sending the crash report to the server results in no error:
[[BITHockeyManager shareHockeyManager] setDebugLogEnabled: YES];
5. Make sure Xcode debugger is not attached while causing the app to crash
6. If you are using `#ifdef (CONFIGURATION_something)`, make sure that the `something` string matches the exact name of your Xcode build configuration. Spaces are not allowed!
7. Remove of at least disable any other exception handler or crash reporting framework.
8. If there an older version of PLCrashReporters framework `CrashReporter.framework` added to the project, remove it.
9. If it still does not work, please [contact us](http://support.hockeyapp.net/discussion/new).

2
docs/index.md
View File

@ -32,4 +32,4 @@ The main SDK class is `BITHockeyManager`. It initializes all modules and provide
## Troubleshooting
- [Symbolication doesn't work](Symbolication-Doesnt-Work) (Or the rules of binary UUIDs and dSYMs)
- [Crashes do not appear on HockeyApp](Troubleshooting-Crashes-Dont-Appear)
- [Crash Reporting is not working](Troubleshooting-Crash-Reporting-Not-Working)