Android error reporting delayed

Describe the bug

It appears that error reports from Android devices are delayed compared to reports from an iOS device for the exact same bug (in some cases, by up to 3 hours). I have an error boundary set up (following this guide) in my React Native app, and purposefully crash the app via a button click, which tries to render some text outside of a Text component (this causes a crash and triggers the error boundary). I set up Bugsnag by following the docs and using @bugsnag/react-native-cli, and besides the Error Boundary, there is no extra config I’ve added to my project that would affect Bugsnag. The reports do come through, so that part is not an issue—but why does it take so much longer than for iOS?

This is essentially what my test component looks like:

const BugsnagTest = () => {
  const [element, setElement] = useState(<></>)

  return (
    <View>
      {element}
      <Button
        text='Send error to Bugsnag'
        onPress={() => {
          setElement(<>Send error to Bugsnag!</>)
        }}
      />
    </View>
  )
}

Here you can see the reports from my Bugsnag dashboard, hours apart:

Steps to reproduce

Trigger the Bugsnag error boundary in both an iOS and Android device, i.e. by trying to render text outside of a Text component, and you should notice that the Android report takes much longer to show up in the dashboard.

@bugsnag/react-native: 7.17.4 React: 17.0.2 React Native: 0.66.3 Device: the Android device I tested on is a Galaxy S10, the iOS device is an iPhone XS

[clr182]

Hi @Twinbird24 - As discussed on the support ticket, this is a known issue. Delivery for React render errors on Android devices are delayed until the application is relaunched.

Our engineering team is looking to fix this, however I don’t have an ETA on this at the moment. We will make sure to keep this thread updated 👍

[johnkiely1]

Hi @Twinbird24, would you mind sending some links to those errors as they appear on your Bugsnag dashboard? You can send those to [e-mail] to avoid posting them publicly.

Additionally is this still reproducible now? I’m currently trying to rule the possibility that there may just have been a significant backlog on our android report queue at the time meaning it was delayed in processing.