Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't report error coming from Android(React Native) release build #2230

Closed
cloudy-ninja opened this issue Oct 17, 2024 · 6 comments
Closed

Comments

@cloudy-ninja
Copy link

Describe the bug

Reporting an error on debug mode is working as expected and we can find it on the Bugsnag dashboard, but not on the release build. It looks like sending bugs to bugsnag works but can't see those on bugsnag dashboard only in release mode.

Steps to reproduce

The following is the code block to notify an error

<Button
  title="Report error to Bugsnag"
  onPress={() => {
    const estDate = new Date().toLocaleString('en-US', {
      timeZone: 'America/New_York',
    });
    Bugsnag.notify(
      new Error(
        `Test error coming from ${ENVIRONMENT}: ${pkg.version} - ${estDate}`,
      ),
    );
  }}
/>

Environment

  • Bugsnag version: 7.25.1

  • React Native version: 0.72.6

  • Android Gralde version: 8.0.1

  • Device

    • Android Emulator
    • S22 Ultra

Android Studio Logs when clicking on the Report error to Bugsnag button

Screenshot 2024-10-17 at 11 02 34

@cloudy-ninja
Copy link
Author

cloudy-ninja commented Oct 18, 2024

I was able to reproduce this issue with a fresh project.
The steps to reproduce

  1. @react-native-community/cli@latest init AwesomeProject
  2. Added @bugsnag/react-native 8.0.0
  3. For Android, we can receive incoming errors in debug mode on the Bugsnag dashboard but not in release mode.

I'm looking forward to your quick response
Thank you!

@RobertoSmartBear
Copy link

HI @cloudy-ninja,

I see you are already in contact with our support with the same request. I have reported your last comment to our engineers but, just to avoid confusion, we will go on with the troubleshooting on the ticket and then publish the result here, once resolved.

@RobertoSmartBear RobertoSmartBear added the needs discussion Requires internal analysis/discussion label Oct 18, 2024
@andrei-tofan
Copy link

Hello,

I'm having a similar issue, checked the documentation and everything is configured correctly, any idea why this is happening?

@andrei-tofan
Copy link

I think there is an issue with the latest version of bugsnag-android had to downgrade 1 version and use v6.9.0.

While debugging, found that the latest version when the native code is called to configure it returns an object with all properties undefined, including the api key.

@mclack
Copy link
Contributor

mclack commented Nov 25, 2024

Hi @andrei-tofan

The latest version of our React Native SDK is not yet compatible with bugsnag-android v6.10.0. Due to this, we would recommend not overriding the version of bugsnag-android within your build.gradle, and instead let the dependency resolve to v6.6.1, as defined in the bugsnag-js package:

api "com.bugsnag:bugsnag-android:6.6.1"

If you continue to have issues after using the latest compatible version of bugsnag-android, please feel free to open a ticket with us directly by contacting [email protected], along with any relevant information for our further investigation (such as your version of bugsnag-js + bugsnag-android, any error messages, code snippets of BugSnag config + build.gradle dependencies etc), and we'll be happy to look into it for you.

@hannah-smartbear
Copy link

Hi @cloudy-ninja,

I see you are already in contact with our support with the same request. I have reported your last comment to our engineers but, just to avoid confusion, we will go on with the troubleshooting on the ticket and then publish the result here, once resolved.

We haven't received a response on the support ticket for a while, so we are closing this GitHub issue alongside the support ticket. If you are able to get back to us on the support ticket then we'd be happy to reopen this.

@mclack mclack removed the needs discussion Requires internal analysis/discussion label Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants