Upgrade library from 2.5.6 to 3.0.0 got this error:

Invalid regular expression: invalid group specifier name
no stack

(@microsoft/applicationinsights-web version is 2.8.6)

• OS/Browser: android
• React-Native Version: 0.69.3

Update to the latest version of React Native to address dependent component security issues and keep this plugin up to date.

Is your feature request related to a problem? Please describe.

Looking through the code for the react-native plugin, I didn't find much that would preclude support for Expo. The main issue I saw is the peer dependency on react-native-device-info, but if the plugin allowed the consumer to inject something which meets that same interface at run time(e.g. something like IDeviceInfo), I couldn't see a reason that expo would not work. Expo exposes all the data needed to satisfy that interface using libraries which are Expo-compatible.

Is there something I have missed?

I'd be excited to open a PR or create a separate extension and share code between the two if a separate extension or alternative approach was preferred to avoid a breaking change.

Describe the solution you'd like

Consumers of this library for RN can inject their own service to provide the device info at initialization, removing need for peer dependency on react-native-device-info. This would be a breaking change for current consumers.

Describe alternatives you've considered

I'd like to use this package for expo and it is explicitly noted that expo will not work. The other option would be to create a separate plugin, however, the two would be nearly identical with the exception of how device info is initialized.

Additional context

I've installed app insights web and the react native plugins, but I can't seem to get the automatic logging of exceptions to work when I throw an Error in my code; is there additional configuration needed?

@microsoft/applicationinsights-react-native: 1.0.3
@microsoft/applicationinsights-web: 2.2.2
react-native-device-info: 2.3.2

React native version 0.60.4

Set up is standard, as per documentation:

const RNPlugin = new ReactNativePlugin();
const appInsights = new ApplicationInsights({
    config: {
        instrumentationKey: 'my key',
        extensions: [RNPlugin],
    },
});
appInsights.loadAppInsights();

I've noticed when I set enableDebugExceptions: true then manually trigger a call to appInsights.trackException({exception: new Error('some error')});, I get an error which I can only assume is stopping this being logged?

AI (Internal): 35 message:"trackException failed, exception will not be collected: " props:"{exception:[object Object]{\messageId\:0,\message\:\AI (Internal): 0 message:\\\Browser does not support local storage. Session durations will be inaccurate.\\\\}}"

Thanks!

Description/Screenshot
"Disabling automatic device info collection" documentation says disableDeviceCollection needs to be initialized on ApplicationInsights config. However, ApplicationInsights config does not recognize this property.

If disableDeviceCollection is initialized on ReactNativeManualDevicePlugin the Android bundling tasks still fails on exception "Unable to resolve 'react-native-device-info'"

If then installing react-native-device-info' you'll end up to exception "NativeModule.RNDeviceInfo is null".

Steps to Reproduce

• React-Native Version: 0.72.3
• SDK Version [e.g. 22]:
  "@microsoft/applicationinsights-react-native": "^4.0.0",
  "@microsoft/applicationinsights-web": "^3.0.2",
• How you initialized the SDK:
  const RNMPlugin = new ReactNativeManualDevicePlugin({ disableDeviceCollection: true, }) const appInsights = new ApplicationInsights({ config: { instrumentationKey: 'YOUR_INSTRUMENTATION_KEY_GOES_HERE', extensions: [RNMPlugin], }, }) appInsights.loadAppInsights()

Expected behavior
Device info collection would be ignored

Additional context
This might be just documentation issue which needs to be clarified more.

Description/Screenshot
Hi

We're trying to integrate our React Native app with Applications Insight but we're facing multiple issues. Mainly, it's not setting correlation headers (Request-Id, Request-Context etc.).

Steps to Reproduce

OS/Browser:

• "react-native": "0.63.3",

SDK Version [e.g. 22]:

• "@microsoft/applicationinsights-react-native": "^2.3.5",
• "@microsoft/applicationinsights-web": "^2.6.5",

How you initialized the SDK:

import { ApplicationInsights } from '@microsoft/applicationinsights-web';
import { ReactNativePlugin } from '@microsoft/applicationinsights-react-native';
import { applicationInsightsKey } from 'react-native-dotenv';

let appInsights;

export function setupApplicationInsights() {
  var RNPlugin = new ReactNativePlugin();
  appInsights = new ApplicationInsights({
    config: {
      instrumentationKey: applicationInsightsKey,
      disableAjaxTracking: false,
      extensions: [RNPlugin],
      samplingPercentage: 100,
      loggingLevelTelemetry: 2,
      diagnosticLogInterval: 100,
      disableFetchTracking: false,
      disableCorrelationHeaders: false,
      enableCorsCorrelation: true,
      enableRequestHeaderTracking: true,
      enableResponseHeaderTracking: true,
    },
  });

  appInsights.loadAppInsights();

  var telemetryInitializer = envelope => {
    if (envelope.baseData.name != null && envelope.baseData.name.includes('heartbeat')) {
      return false;
    }

    envelope.tags['ai.cloud.role'] = 'courier-app';
    envelope.tags['ai.cloud.roleInstance'] = 'courier-app';
  };

  appInsights.addTelemetryInitializer(telemetryInitializer);
}

Expected behavior

We thought this would add the necessary headers to each fetch request and also send the necessary tracking data to the AI backend but it seems we're only getting some data in to AI which is not being correlated with our other services.

Additional context
We managed to get the application to send correlation data by adding this hack before we initialize AI.

  global.fetch.polyfill = false;

But this feels like a bad thing to do and it still didn't correlate the requests in the application map.

We're using react-navigation v5 and are sending appInsights.trackPageView(/*data*/) on each screen change. These page views does show in AI.

So our biggest issues right now are:

1. Data isn't being correlated correctly in the Application Map view.
2. Transactions aren't being grouped in a sane way in the end-to-end transactions view. They all seem to fall under the same operation id which we're not sure how to fix.

Description
Same as this issue microsoft/applicationinsights-react-js#32

Tried with the following versions:

• @microsoft/applicationinsights-react-native v3.0.3
• @microsoft/applicationinsights-web v3.0.2

and

• @microsoft/applicationinsights-react-native v4.0.0-nightly.2306-02
• @microsoft/applicationinsights-web v3.0.3-nightly3.2306-01

Steps to Reproduce

import { ApplicationInsights } from '@microsoft/applicationinsights-web';
import { ReactNativePlugin } from '@microsoft/applicationinsights-react-native';

var RNPlugin = new ReactNativePlugin();
var appInsights = new ApplicationInsights({
    config: {
        instrumentationKey: 'YOUR_INSTRUMENTATION_KEY_GOES_HERE',
        extensions: [RNPlugin]
    }
});
appInsights.loadAppInsights();