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
It looks like Airbrake is logging the error itself just fine, but not attaching any of the parameters to the environment section on the website.
After doing some further research, it looks like in ABNotifier.m under logException:withParameters we do not add the exceptionParameters to the final dictionary we pass to Airbrake. The dictionary only contains the exception name, reason, and call stack. It is missing the exception parameters and current view controller.
Overview
I am trying to log custom exceptions using Airbrake to pair with our existing web client integration.
Usage
I am performing custom logging like so:
It looks like Airbrake is logging the error itself just fine, but not attaching any of the
parameters
to theenvironment
section on the website.After doing some further research, it looks like in
ABNotifier.m
underlogException:withParameters
we do not add theexceptionParameters
to the final dictionary we pass to Airbrake. Thedictionary
only contains the exception name, reason, and call stack. It is missing the exception parameters and current view controller.Specifically,
Expected Behavior
I would expect that the parameters properly get passed up and then I can view them in
Environment
unless I am not looking in the right place.The text was updated successfully, but these errors were encountered: