content: Error in invocation of contentFilterPrivate.isURLBlocked (Opera GX only)

Environment


  • Operating System: Windows_NT
  • Node Version: v16.15.0
  • Nuxt Version: 3.0.0-rc.4
  • Package Manager: npm@8.5.5
  • Builder: vite
  • User Config: modules
  • Runtime Modules: @nuxt/content@2.0.1
  • Build Modules: -

Reproduction

npx nuxi init content-app -t content
cd content-app
npm install
npm run dev

or use: https://stackblitz.com/github/nuxt/starter/tree/content

Describe the bug

image

See image.

Additional context

No response

Logs

[vite] connecting...
client.ts:53 
[vite] connected.
filter_content.js:202 Uncaught (in promise) TypeError: Error in invocation of contentFilterPrivate.isURLBlocked(string url, contentFilterPrivate.ElementType type, string sitekey): No matching signature.
    at FilterContent.isUrlFiltered_ (filter_content.js:202:44)
    at FilterContent.filterAssetsIfNeeded_ (filter_content.js:85:16)
    at FilterContent.filter_ (filter_content.js:78:10)
    at FilterContent.initialize_ (filter_content.js:181:10)
    at filter_content.js:30:46
isUrlFiltered_ @ filter_content.js:202
filterAssetsIfNeeded_ @ filter_content.js:85
filter_ @ filter_content.js:78
initialize_ @ filter_content.js:181
(anonym) @ filter_content.js:30
Promise.then (async)
(anonym) @ filter_content.js:30
runtime-core.esm-bundler.js:1331 <Suspense> is an experimental feature and its API will likely change.

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 7
  • Comments: 27 (1 by maintainers)

Most upvoted comments

It is caused by a fault in the Opera GX tracking blocker. You can fix this by disabling the tracking blocker until Opera releases a fix.

I’ve reported this bug to the developers at Opera Software a couple of days ago already:

https://opera.atlassian.net/servicedesk/customer/portals

Unfortunately, I cannot link to the issue, since their bugtracker is not public.

I solved it by disabling “Block ads” and “Block Trackers” under Settings>Privacy Protection

FIX (opera gx):

Turn off adblocker and tracking blocker. Works fine now.

Disable privacy protection on localhost page, it’s works normally.

I thought this was an issue on my website but yea seems that it’s opera

Issue is now fixed with Opera 89.0.4447.38.

It is caused by a fault in the Opera GX tracking blocker. You can fix this by disabling the tracking blocker until Opera releases a fix.

Definitely a problem with Opera. Also a fault in Opera for desktop’s tracking blocker.

I came here after encountering this issue in a create react app dev server after importing a react-query custom data fetch hook when I had not yet declared state from the hook. ie:

Error encountered when useForecasts imported into App…

function useForecasts({ lat, long }) {
const fetchForecasts = async () => {
    ...
    try ...fetch(someData
    ...return data
  };
const { isLoading, error, data, isFetching } = useQuery(
    "forecasts",
    fetchForecasts
  );
return {
    forecasts: data ?? [],
    isForecastLoading: isLoading,
    error,
    isFetching,
  };
}

Error not encountered when below code is also included in App

  const { forecasts, isForecastLoading } = useForecasts(
   geoLocation.coordinates
  );

i have the same problem and i am using Opera 88.0.4412.53