Skip to content

Adjusting report depth for handled errors has no effect #357

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

Closed
paulz opened this issue Jun 6, 2019 · 0 comments · Fixed by #363
Closed

Adjusting report depth for handled errors has no effect #357

paulz opened this issue Jun 6, 2019 · 0 comments · Fixed by #363

Comments

@paulz
Copy link
Contributor

paulz commented Jun 6, 2019

Description

Adjusting report depth as per documentation:
https://docs.bugsnag.com/platforms/ios-objc/reporting-handled-exceptions/#depth
has no effect

Issue

Incrementing number of stack traces to discard

void logError(NSError *error) {
    [Bugsnag notifyError:error block:^(BugsnagCrashReport *report) {
        // Increment the number of stackframes to discard
        report.depth -= 1;
    }];
}

does not cause them being discarded

Environment

Library versions:

  • Bugsnag version (from your Podfile, Podfile.lock, or elsewhere): 5.17.3
  • CocoaPods version (if any) (pod -v): 1.6.1
  • Carthage version (if any):
  • iOS/tvOS/macOS version(s) iOS 12
  • debug mode or production?: debug
  • How are you initializing Bugsnag? Can you share a snippet of your
    AppDelegate where Bugsnag is configured? as per Example app
Error messages:
bugsnag-example/ViewController.swift:58:17logError	
bugsnag-example/ViewController.swift:70:13sendAnError	
<compiler-generated>sendAnError
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant