Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue symbolication doesn't work #4549

Open
igordrljic opened this issue Nov 18, 2024 · 0 comments
Open

Issue symbolication doesn't work #4549

igordrljic opened this issue Nov 18, 2024 · 0 comments

Comments

@igordrljic
Copy link

Platform

iOS

Environment

Other

Installed

Swift Package Manager

Version

8.40.1

Xcode Version

16.1

Did it work on previous versions?

No response

Steps to Reproduce

Hello,

I'm having troubles with Sentry issue report symbolification.

I created an iOS beta ad-hoc app build, uploaded dSYM files to the company self-hosted Sentry server, but when an issue appears in the Issues section there is an "A required debug information file was missing" warning and stack trace contains caption where method names should be.

I tried to upload dSYM files in 3 different ways:

  1. Run script at the end of the app building process
  2. Using sentry-cli from terminal
  3. Using fastlane sentry_debug_files_upload after successfull app build

All 3 ways successfully uploaded dSYM files, but unfortunatelly nothing helped with the symbolicating events.

With each test I created a new event by calling: SentrySDK.capture(error: error) with different NSError domain and code, but all of them had the same symbolication issue.

This is the Sentry configuration we use:

SentrySDK.start { options in

    options.dsn = "..."

    switch buildConfiguration {
    case .debug:
        options.debug = true
        // Set tracesSampleRate to 1.0 to capture 100% of transactions for performance monitoring.
        // We recommend adjusting this value in production.
        options.tracesSampleRate = 1.0

        // Sample rate for profiling, applied on top of TracesSampleRate.
        // We recommend adjusting this value in production.
        options.profilesSampleRate = 1.0
    case .beta, .release:
        options.debug = false
        options.tracesSampleRate = 0.25
        options.profilesSampleRate = 0.25
    }
}

This is how issue report stack trace looks like:
Image

Do you have some advice on how to troubleshout this or an idea what could be wrong?

Expected Result

Symbolicated issue reports.

Actual Result

Unsymbolicated issue reports.

Are you willing to submit a PR?

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Waiting for: Product Owner
Status: Needs Discussion
Development

No branches or pull requests

1 participant