ApplicationInsights-JS: [BUG] Beacon API emitting warnings in console

Description/Screenshot

I am trying to use the Beacon API to send telemetry. However I am getting a warning from Edge:

Cross-Origin Read Blocking (CORB) blocked cross-origin response https://eastus2-3.in.applicationinsights.azure.com//v2/track with MIME type application/json. See https://www.chromestatus.com/feature/5629709824032768 for more details.

I do see my events in App Insights.

Steps to Reproduce

Initialize app insights with connection string, set isBeaconApiDisabled to false (to enable the api). Additionally, double-negatives are awful for developer experience.

  • OS/Browser: Windows 10
  • SDK Version [e.g. 22]: 2.8.11
  • How you initialized the SDK: NPM

Expected behavior

There are no warnings in the console.

Additional context

my setup code:

const appInsights = new ApplicationInsights({
  config: {
    connectionString: config.appInsightsConnectionString, // use connection string instead of just key
    disableAjaxTracking: true, // we don't use ajax
    disableFetchTracking: true, //don't auto-track fetch calls (too high usage)
    disableExceptionTracking: true, // don't auto-collect exceptions, they'll be sent manually
    disableXhr: true, // don't use XMLHttpRequest
    enableCorsCorrelation: true, // correlate requests with backend requests
    maxAjaxCallsPerView: -1, //track ALL calls from a single page view
    isBeaconApiDisabled: false, // use Beacon API
  },
});

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 15 (4 by maintainers)

Most upvoted comments

Although, now that I think about it, I didn’t close all applications (e.g. Outlook) which may have had an instance of the WebView active.

Sounds like a browser problem, but can be ignored?

Yes, that is our understanding. And as we don’t need to read the response the events will still be recorded.

Okay, that’s fine with me. If there’s nothing for you guys to do specifically, I am fine with closing this issue!