Cross-Origin Read Blocking (CORB) blocked cross-origin response

Upgraded to Premium plan yesterday to utilize re-ranking. Followed this guide (Send Insights Events | Building Search UI | Guide | Algolia Documentation) but keep running into CORB issue.

InstantSearch.js 4.14.0
algoliasearch-lite.umd.js | 4.8.5

What I did:

  1. Loaded search-insights library via jsdelivr by including it in .
  2. Created insights middleware and set useCookie: true.

Every time I refine results, Chrome’s console logs a warning with the following message:
Cross-Origin Read Blocking (CORB) blocked cross-origin response<APP_ID>&X-Algolia-API-Key=<API_KEY>&X-Algolia-Agent=insights-js%20(2.0.0) with MIME type application/json. See Cross-Origin Read Blocking (CORB) - Chrome Platform Status for more details.

I passed the onEvent event handler to insightsMiddleware and insightsMethod, payload, widgetType, eventType are all properly set. It’s only when I call aa(insightsMethod, payload) to send event to Algolia that the CORB issue pops up.

Have you resolved it?
I have the same problem when trying to call aa.

even i keep getting the CORSB error, but the click event was getting tracked properly. It usually appears after 4-5 minutes

I didn’t get it resolved. Stopped trying to make it work after a while. Changed plan from Premium back to Standard.

The CORB message in the console is only a warning, not an error, and is related to the fact that the network response is empty, you can read more information here: CORB is fired by Chrome when an event is requested · Issue #253 · algolia/search-insights.js · GitHub