Document Crashlytics hang reporting and OTel event reporting in README#46
Merged
Conversation
Add a "Crashlytics Integration" section covering enableWithCrashlyticsSupport, CrashlyticsHangsSettings (reporting modes, hang reason, type formatter), the fatal/non-fatal hang reporting lifecycle, and the crashlyticsEnabledInDebug escape hatch. Surface both built-in reporting integrations (Crashlytics for hangs, OpenTelemetry for all events) in the feature list with cross-links. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Fatal hangs in .fatalHangsAsCrashes mode capture all threads, not just the main thread. Remove the redundant hangs-only blockquote. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Replace the full in-README Crashlytics and OpenTelemetry sections with short blurbs that link to dedicated wiki pages, matching the project's existing convention of keeping detailed docs in the Wiki. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Minimum allowed line rate is |
pilot34
added a commit
that referenced
this pull request
Jun 25, 2026
Follow-up to #46 (those commits landed after the squash-merge): - WatchDogTerminationsReceiver -> WatchdogTerminationsReceiver - Add link target for "Screen identifiers" (#screen-identifiers) - TTI sample: in-scope `screen` + `.milliseconds` (was undefined `performanceScreen` and sub-second-truncating `.seconds`) - Bump example CocoaPods tag to current release (1.10.1) - Drop the long descriptions after the Crashlytics/OTel wiki links Co-authored-by: Gleb Tarasov <gleb.tarasov@booking.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Documents the two built-in reporting integrations in the main README:
Changes
PerformanceSuiteCrashlytics/ CocoaPodspod 'PerformanceSuite/Crashlytics'), usage viaenableWithCrashlyticsSupport(...), the fatal/non-fatal hang reporting lifecycle,CrashlyticsHangsSettingscustomization (.fatalHangsAsCrashesvs.fatalHangsAsNonFatals,hangReason,hangTypeFormatter), and thecrashlyticsEnabledInDebugescape hatch.Docs-only change, grounded in
PerformanceSuite/Crashlyticssources,Package.swift, and the podspec.🤖 Generated with Claude Code