Skip to main content
edited body
Source Link
Amit Naraniwal
  • 1.3k
  • 1
  • 11
  • 20

It turns out that customer-data.js uses the localStorage to store a variety of stuff (probably for caching purposes). This means that when a module (or Magento) updates, you'd better make sure to flush your local storage as well.

Reference - You can finefind some more solution here :

https://github.com/magento/magento2/issues/6410

https://github.com/magento/magento2/blob/9db4501d29028ba9ac552f14d80b42bc923847f4/app/code/Magento/Review/etc/frontend/di.xml#L32

It turns out that customer-data.js uses the localStorage to store a variety of stuff (probably for caching purposes). This means that when a module (or Magento) updates, you'd better make sure to flush your local storage as well.

Reference - You can fine some more solution here :

https://github.com/magento/magento2/issues/6410

https://github.com/magento/magento2/blob/9db4501d29028ba9ac552f14d80b42bc923847f4/app/code/Magento/Review/etc/frontend/di.xml#L32

It turns out that customer-data.js uses the localStorage to store a variety of stuff (probably for caching purposes). This means that when a module (or Magento) updates, you'd better make sure to flush your local storage as well.

Reference - You can find some more solution here :

https://github.com/magento/magento2/issues/6410

https://github.com/magento/magento2/blob/9db4501d29028ba9ac552f14d80b42bc923847f4/app/code/Magento/Review/etc/frontend/di.xml#L32

Source Link
Amit Naraniwal
  • 1.3k
  • 1
  • 11
  • 20

It turns out that customer-data.js uses the localStorage to store a variety of stuff (probably for caching purposes). This means that when a module (or Magento) updates, you'd better make sure to flush your local storage as well.

Reference - You can fine some more solution here :

https://github.com/magento/magento2/issues/6410

https://github.com/magento/magento2/blob/9db4501d29028ba9ac552f14d80b42bc923847f4/app/code/Magento/Review/etc/frontend/di.xml#L32