IE11 Assigns new Nop.Customer Cookies for every request. Once you add a product and go to another page, shopping cart will be empty as Nop commerce assigned a new customer id for that request.
Tested with Add to cart also flow as well. Its described below.
Just tested Nop 3.20 with IE 11. Add items to cart and then once you go to cart, i can see an empty cart.
This is happening in demo site. http://demo.nopcommerce.com
This is happening for Guests.
More interestingly, then i tried to login as member using IE 11, once you click login button, it takes to home page without logging me in. i tested with my local dev nop3.20 with IE11.
When i try to register in demo site, it throws an error in IE 11.
Checked in following forums, no idea to solve. https://www.nopcommerce.com/boards/t/24280/ie10-items-will-not-add-to-cart.aspx https://www.nopcommerce.com/boards/t/21509/shopping-cart-empty-at-checkout.aspx
See my vedio demo, http://screencast.com/t/LYHypgTix
Appears to be a new Nop.Customer Cookie is assigned every time when using IE11.
I have a customer experiencing the same thing. I don't have IE11 installed, but am eagerly researching a solution. Please let me know if you find anything.
Are you still facing this issue? I'm facing the same with nopCommerce 3.10 and it seems is not the browser.
If I run the application in my local in debug then in any browser i see nop.customer cookie being created, but once I deploy it, then the cookie is no longer created (my server is Windows Server 2012, IIS 8.5)
What I found is that if you remove the expiration date, then the cookie will get created, for some reason adding the expiration date will prevent the cookie from being created, any clue on this?
On the meantime that is my workaround and now I can have guest customers adding items to the cart and then register.
It seems everything works fine in the application the problem is for some reason the server Request Date header was sending a wrong date (3 years from now) obviously what will happen is that since nop.customer cookie expires in one year from now that date is less than the date the request header is expecting and it will be treated as an expired cookie.
I checked in fiddler and saw that the response was writing the cookie with the proper date, but then in Cache section on the top the Date field was wrong.
The solution, simple - Restart your server - and you will be all set.
It seems that this happens with VMs as servers (I'm using Amazon EC2 VM)