Skip to content

[skill-drift] fix(sentry-cocoa-sdk): app start limit + SentryObjC docs#149

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
skill-drift/sentry-cocoa-sdk-skill-drift-fix-sentry-cocoa-sdk-app-sta-1780325408
Open

[skill-drift] fix(sentry-cocoa-sdk): app start limit + SentryObjC docs#149
github-actions[bot] wants to merge 1 commit into
mainfrom
skill-drift/sentry-cocoa-sdk-skill-drift-fix-sentry-cocoa-sdk-app-sta-1780325408

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot commented Jun 1, 2026

Warning

Auto-generated from external SDK content. Review all links and code suggestions before acting on them.

Summary

  • Fix incorrect app start duration limit: changed from 5 seconds to 180 seconds (3 minutes) in tracing.md
  • Add documentation for experimental SentryObjC wrapper SDK (introduced in 9.16.0-alpha.1, PR #7918)

Changes

1. App Start Duration Limit Fix

File: skills/sentry-cocoa-sdk/references/tracing.md

Corrected the maximum app start duration from "5 seconds" to "180 seconds (3 minutes)" to match the actual SDK implementation (SentryAppStartTracker.maxAppStartDuration = 180.0). The warning note correctly stated that this limit is skipped for standalone app start tracing.

2. SentryObjC Documentation

File: skills/sentry-cocoa-sdk/SKILL.md

Added Option 4 documenting the new experimental SentryObjC wrapper SDK. This is for pure Objective-C/C++ projects that cannot enable Clang modules (e.g., with -fmodules=NO). The documentation includes:

  • When to use SentryObjC vs. regular Sentry
  • SPM installation instructions
  • Migration steps from regular Sentry
  • Link to xcframework download
  • Clear experimental status warning

PRs Reviewed

  • #7918: feat(objc): SentryObjC wrapper SDK (merged 2026-05-29)
  • #7949: feat: skip max app start duration limit for standalone tracing (merged 2026-05-27)
  • #7936: feat: Add extendAppLaunch/finishExtendedAppLaunch API (merged 2026-05-27, already documented)

Verification

  • Confirmed 180-second limit by reading SentryAppStartTracker.swift source at merge SHA bbb8fdc7
  • Verified SentryObjC feature details from PR #7918 and CHANGELOG.md
  • Checked that extended app launch API (PR #7936) is already documented in tracing.md lines 171-236

Source PRs

Automated drift-fix run.

Co-Authored-By: Claude (claude-sonnet-4-5) <noreply@anthropic.com>
| Initial Frame Render | `didFinishLaunchingNotification` → first CADisplayLink callback (v9+) |

> Warning: If more than **5 seconds** elapse between transaction start and app-start end, app start spans are **not attached** to avoid misassociation. This limit is skipped when standalone app start tracing is enabled.
> Warning: If more than **180 seconds** (3 minutes) elapse between transaction start and app-start end, app start spans are **not attached** to avoid misassociation. This limit is skipped when standalone app start tracing is enabled.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: The documentation for the app start duration threshold is inconsistent. The warning note states a 180-second limit, but the troubleshooting table still refers to the old 5-second limit.
Severity: LOW

Suggested Fix

Update the troubleshooting table in skills/sentry-cocoa-sdk/references/tracing.md to reflect the new 180-second threshold. Change the text "exceeded 5 seconds" to "exceeded 180 seconds" to align with the updated warning note.

Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: skills/sentry-cocoa-sdk/references/tracing.md#L169

Potential issue: The documentation in `skills/sentry-cocoa-sdk/references/tracing.md`
contains conflicting information regarding the app start duration threshold. While the
warning note on line 169 was updated by this pull request to state a 180-second limit, a
troubleshooting table at the end of the same file was not updated and still references
the old 5-second limit. This inconsistency can lead to confusion for developers or AI
models consulting the documentation, as they might receive incorrect guidance when
diagnosing why app start spans are not being attached.

Did we get this right? 👍 / 👎 to inform future reviews.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants