Instabug / Instabug-React-Native

In-app feedback and bug reporting tool for React Native
https://instabug.com/platforms/react-native
MIT License
311 stars 99 forks source link

Warning on 13.3.0: "IBG-RN: The response body for the network request with URL..." #1268

Closed leonardorib closed 2 months ago

leonardorib commented 2 months ago

After upgrading to 13.3.0, I'm getting this warning (console.warn) in the development build on both Android and iOS every time Instabug is initialized:

IBG-RN: The response body for the network request with URL http://192.168.1.141:8081/symbolicate has been omitted because the content type  isn't supported.

Is this expected?

It didn't affect functionality. It's just annoying. Feels like a console.warn that shouldn't be there I guess?

Steps to Reproduce the Problem

  1. Upgraded to 13.3.0
  2. Run the development build of the app and init instabug

Expected Behavior

Shouldn't repeatedly see this warning or should be able to hide it based on the log levels.

Actual Behavior

Warning keeps showing up.

Instabug integration code

I made sure all instabug features are commented out. So it really comes down to the initialization:

Instabug.init({
    token: config('instabug.token'),
    invocationEvents: [
      config('env') === 'dev'
        ? InvocationEvent.twoFingersSwipe
        : InvocationEvent.shake,
    ],
  });

Simply initializing it will trigger the warn. I also tried using debugLogsLevel: LogLevel.none but still getting the warn.

SDK Version

13.3.0

React Native, iOS and Android Versions

RN 0.73.8 / iOS 17.5.1 / Android 14

Device Model

iPhone 13 / Samsung Galaxy m52

stale[bot] commented 2 months ago

This issue has been automatically marked as pending feedback because we need additional information to be able to investigate it further. It will be closed in 7 days if it remains inactive. Thank you for your contributions.

stale[bot] commented 2 months ago

This issue has been automatically closed since we haven't heard back from you. Please feel free to re-open the issue if you have more information to add.

xanderdeseyn commented 1 month ago

Have you found a solution to this? We are running into the same problem.

gcottrell1 commented 1 month ago

also seeing this. anyone able to take a look?

bobinrinder commented 1 month ago

@xanderdeseyn @gcottrell1 We reported it to support and they "added it to their backlog".