Property 'error' doesn't exist when passing custom error metadata

[roni-castro-shipt]

Steps to reproduce

Add this to a react-native project and tap that button in debug mode.

import Bugsnag from '@bugsnag/react-native';
import { Button, View } from 'react-native';

export default function App() {
  return (
    <View style={{ flex: 1, alignItems: 'center', justifyContent: 'center' }}>
      <Button
        title="simulate error"
        onPress={() => {
          try {
            throw new Error('custom error is not logged');
          } catch (error) {
            Bugsnag.notify(new Error('Failed to initialize SDK'), event => {
              event.severity = 'warning';
              event.addMetadata('Additional Info', { originalError: error }); // this is throwing an error and not being included in metadata in debug mode
            });
          }
        }}
      />
    </View>
  );
}

 ERROR  [bugsnag] Error occurred in onError callback, continuing anyway…
 ERROR  [bugsnag] [ReferenceError: Property 'error' doesn't exist]

This does not seem to happen in production, though, and it keeps passing originalError as an AdditionalInfo. Just in debug mode, it throws that error and ignores that property.

[roni-castro-shipt]

Changing the scope of originalError up solves that error from Bugsnag. Why does the lib throw that error in debug mode for the example above?

...
} catch (error) {
    const metadata = { originalError: error }; // moved the metadata up
    Bugsnag.notify(new Error('Failed to initialize SDK'), event => {
      event.severity = 'warning';
      event.addMetadata('Additional Info', metadata);
    });
}