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
Since upgrading to 7.11.0, I'm observing duplicated breadcrumbs from custom-added log entries (with console.* statements replaced with bugsnag.notify, see below)
Steps to reproduce
Log various events in quick succession, the breadcrumbs prior to the reported log will end up duplicated.
Environment
Bugsnag version: 7.11.0
React-Native: 0.62.4
Device (e.g. iphonex): Android
Example code snippet
I'm intercepting console calls like this in prod/release modes:
Thanks for reporting. It does look like a bug has been introduced in v7.11.0 resulting in the duplicated breadcrumbs. The bug doesn't look related to how you're intercepting console log calls, it seems to affect breadcrumbs logged for handled errors in general.
We're just investigating the cause and will aim to release a fix in due course.
If it helps, I managed to work around it by disabling the "console" logs on the android native side configuration with the following settings (also applied this to the iOS side just to be sure).
Are there any drawbacks in using this configuration vs using the default one? I also noticed some flags like MANUAL and PROCESS are not documented in the docs (I had to find them in the actual source code / class info), which is a bit misleading.
There should be no issues with using this approach. Thanks for highlighting the missing breadcrumb type options, we will look to get the docs updated accordingly.
Describe the bug
Since upgrading to 7.11.0, I'm observing duplicated breadcrumbs from custom-added log entries (with console.* statements replaced with bugsnag.notify, see below)
Steps to reproduce
Log various events in quick succession, the breadcrumbs prior to the reported log will end up duplicated.
Environment
Example code snippet
I'm intercepting console calls like this in prod/release modes:
Here's an example of a log entry showing the same log statement twice (one with the unhandled variable, which is odd?)
Did anything change internally and bugsnag is also intercepting console log calls? This does NOT happen on iOS by the way.
Error messages:
The text was updated successfully, but these errors were encountered: