beforeInteractive not working on 404 page

[shut spoke]

Hi everyone.
Im having issue with OSANO cookie consent. It is added into Root layout with strategy="beforeInteractive" :
<Script
strategy="beforeInteractive"
src={OSANO_URL}
/>
But it is not being initialized on first load (when we go directly to 404 url on incognito mode).

I even created repository to reproduce:
https://github.com/kacyee/before-interactive-2
When we add function "notFound()" on page, we cant see
console.log("I should be beforeInteractive"); <- this is script initialized with strategy "beforeInteractive" on root layout.
But when we remove "notFound()" from page, everything works fine.

It is super crucial for me to have OSANO on every page ,even on 404.

[sudden onyx]

Post created!

🔎 This post has been indexed in our web forum and will be seen by search engines so other users can find it outside Discord

🕵️ Your user profile is private by default and won't be visible to users outside Discord, if you want to be visible in the web forum you can add the "Public Profile" role in id:customize

✅ You can mark a message as the answer for your post with Right click -> Apps -> Mark Solution
(if you don't see the option, try refreshing Discord with Ctrl + R)

[sinful sky]

Hi there, please don’t delete old posts only to repost them. You can bump old posts.

See also:

[quiet bolt]

Why your post might not have received answers.

People who help here are all volunteers, they are not paid so not required to attend to any forum posts. So if a post doesn’t have a response, there are four possible cases:

1. People who may help have not been active yet or did not find the question. In this case you can bump the question later to make it float up the channel so those people might be able to see it. Don’t do it more than once per day.

2. No one can answer, usually because the question concerns technologies that are too niche or the question is too hard. For example, many people are not able to help with questions about hosting on very niche platforms.

3. The question is bad. Following the “resources for good questions” in https://discord.com/channels/752553802359505017/1138338531983491154 will help you avoid this third scenario.

4. The question is too long. Keep it concise please, people who help may not have sufficient spare time and energy to read through a help request that is too long.

Requested by joulev

[shut spoke]

Alright 🙂

[shut spoke]

bump