You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The depth property on BugsnagEvent appears to have been removed in #498, which listed depth as unused. However, it was deliberately added to BugsnagCrashReport and documented in #110 (based on request in #109), and our app used it to hide its own central error handling stack frames. This appears to have been a mistake; please add it back.
Steps to reproduce
Have a project that uses Bugsnag 5.23.0
Replace version in Podfile with 6.2.2
pod install
Observe that calls to +[Bugsnag notifyError:block:] in which the event (formerly report) in the block parameter had a depth adjustment now result in a compile error: Value of type 'BugsnagEvent' has no member 'depth'. All other errors in our app due to deprecations and renames seem to have workarounds or equivalents, but not the loss of depth.
Describe the bug
The
depth
property onBugsnagEvent
appears to have been removed in #498, which listeddepth
as unused. However, it was deliberately added toBugsnagCrashReport
and documented in #110 (based on request in #109), and our app used it to hide its own central error handling stack frames. This appears to have been a mistake; please add it back.Steps to reproduce
pod install
+[Bugsnag notifyError:block:]
in which the event (formerly report) in the block parameter had a depth adjustment now result in a compile error:Value of type 'BugsnagEvent' has no member 'depth'.
All other errors in our app due to deprecations and renames seem to have workarounds or equivalents, but not the loss ofdepth
.Environment
Example code snippet
Error messages: Value of type 'BugsnagEvent' has no member 'depth'
The text was updated successfully, but these errors were encountered: