I'm running into an issue with the cookie consent banner (from the SC bundle) that no matter what buttons I press in the banner, the banner does not go away. Whenever I clear my cookies/cache, I am able to click the button to close the banner. However if I refresh the screen, the banner comes back and I cannot remove the banner in any way besides clearing cookies again. I recently updated to version 1.1.2, and the issue seems to persist. Has anyone else run into this and found a resolution? Replication steps: Navigate to SC site. Click reject all/accept all. Banner does not disappear

does it persist across all browsers ?

Yes, an issue on chrome, edge, and firefox

I have seen similar behavior with the SuiteCommerce Cookie Consent bundle when the consent state is not being stored correctly in the browser. please check like this: Open browser DevTools → Application → Cookies. Check if the consent cookie is added or updated after clicking the buttons. If no cookie is saved, the banner will appear again after every refresh.

Please raise a case. I've seen a few people mention this, and I've seen it myself a couple of times. More cases help prioritise it

The cookie is being saved

Hi Guys , I also faced this issue, at first it will work , once the page is refreshed the banner will appear again and become unresponsive

Thanks for confirming. Since the cookie is being saved, it looks like the persistence part is working. I would next check if the SC cookie consent script is reading the value correctly after refresh. Could you check the browser console for any JS errors and also confirm the cookie domain/path matches the SC site domain? It may be an initialization issue rather than a cookie creation issue.

Yes, my understanding is that it is an interface problem rather than a cookie problem

Since the consent cookie is being saved, I agree this looks more like a UI initialization issue. I would check the console for JS errors and verify the cookie consent script is correctly loading the saved state after refresh. It may need a SuiteCommerce bundle fix rather than a browser change.