React-native: Async function swallowing console error

Describe the bug

When an exception occurs in a component function with the async keyword in the signature, the error is not being logged to the console.

Steps to reproduce

1. Pull down this repo’s master branch and run (linked below). This is a clone of the rn063example folder with the changes in App.js to reproduce what I am experiencing.
2. When the app is running, click the red text button.
3. Doing this is when I did not see the console error.

Environment

• Bugsnag version: 7.3.0-alpha.12 (originally experienced on 7.5.2)
• Browser framework version (if any):
  • React: 0.63.0 (originally experienced on 0.63.2)
• Device (e.g. iphonex): iPhone 11 (13.2.2) and Pixel 3 XL (API 29)

Example Repo

https://github.com/ShawnCholeva/bugsnag-async-func-error

Example code snippet

Error messages:

[xljones]

Hey @ShawnCholeva, thanks for raising providing the repro. Confirmed the behaviour you’re seeing. We’ll take a look into this.

When running without Bugsnag enabled, we’d expect to see a warning when a possible unhandled rejection occurs:

With Bugsnag enabled, this unhandled rejection error does get reported to Bugsnag, but it’s hidden from the console.

[evelant]

@mattdyoung this seems like it was improved in v7.6.0 but not really fixed. There is now a console log for Possible Unhandled Promise Rejection (id: 1): and a (not so useful bugsnag internals) stack but it still swallows the error message. That means you need to log into bugsnag to read any async error messages which isn’t ideal. Can this be reopened until error messages are no longer being swallowed in development?