Cookie banner keeps showing during development

Shopify CLI and Libraries
1

Is anyone else experiencing the cookie banner appearing on every page load during theme development on localhost, even after accepting it? This wasn’t happening before, so I’m curious if anyone else has run into this.

Note: happens on legacy as current CLI. So I assume this might be because of an update to the cookie banner, not the CLI.

2

Hi Dries - I’m not seeing any other reports of this, can I get more info on your set up, eg: running mac vs windows, browser, etc?

3

@Dries_Pieters for what it’s worth, could it be built into the theme to show within design mode?

I have seen themes where there are data collection forms (like newsletter) coming up on every page load simply because it was in design mode.

4

I also have this problem: the cookie banner is displayed every time the page is reloaded when developing locally with shopify theme dev.

5

Hi guys,

Thanks for looking into this. Here’s some more info:

  • Using the native Shopify cookie banner. (Automated settings)
  • Latest CLI 3.69.2, but happens with --legacy as well
  • Browser: chrome, safari, firefox (all latest) on mac osx (latest).
  • Tried clearing all cookies
  • Cookies are accepted on the primary domain, so on the live site or development preview url .myshopify.com/?preview_theme_id=xxxx it works
  • But on localhost http://127.0.0.1:9292/ it keep popping up every time
  • Issue only started happening ± a week ago

There is a cookie _tracking_consent :

{"con":{"CMP":{"a":"","m":"","p":"","s":""}},"v":"2.1","region":"BEVLG","reg":"","purposes":{"p":false,"a":false,"m":false,"t":true},"display_banner":true,"sale_of_data_region":false}

On localhost this value does not change after accepting. On the primary domain it does change after accepting.

Console error after accepting:

POST https://127.0.0.1:9292/api/unstable/graphql.json net::ERR_SSL_PROTOCOL_ERROR

Hope this helps!

6

Hi Dries - if you test on other stores and different themes, is it still appearing?

7

That’s correct. Tried on couple of stores and different themes.

8

Hi again Dries - were you able to figure this issue out?

9

Hey Liam,

No unfortunately still the same problem…

10

Will investigate more today and hopefully should have a solution soon.

1 Like
11

Hello, I still have the problem, regardless of the browser :confused:

12

Still having this issue. On a new store as well.

13

Have been having the same issue on multiple stores last few months.

1 Like
14

There’s an active open issue for this FYI

15

Yup been getting this for months, assumed everyone else had too! Possibly Firefox specific?