Customer is automatically logged out during checkout process or sometime after order is placed

[akhileshlpatel]

Logged In customer automatically logged out during the checkout process when one of the catalog setting is set to YES in admin. This issue occurred when user come to the checkout page and sometimes just after placing an order. Sometimes when user just refresh the checkout page.

Preconditions

1. Magento CE 2.2.2 with sample data is installed. PHP 7.0.26

Steps to reproduce

1. Enable the setting in Admin -> Stores -> Configuration -> Catalog -> Catalog -> Recently Viewed/Compared Products -> Synchronize widget products with backend storage -> Yes
2. Login as register customer.
3. Add product in cart and go to the checkout page.
4. Just refresh the checkout or go ahead with checkout process.

Expected result

1. Customer should not be logged out automatically

Actual result

1. Customer is logged out automatically

I have tested this with different PHP versions and in multiple websites.

[magento-engcom-team]

@akhileshlpatel thank you for your report.
We were not able to reproduce this issue by following the steps you provided. Please provide more detailed steps to reproduce or try to reproduce this issue on a clean installation or latest release.

[akhileshlpatel]

@magento-engcom-team Thanks for the reply. Yes may be you didn't get the the issue in first time. Please check with different products and browsers if possible. Also I didn't check this in version 2.2.3 but I have checked this in version 2.2.2 and we faced this in many different setups.

[magento-engcom-team]

@akhileshlpatel thank you for your report.
We were not able to reproduce this issue by following the steps you provided. We tried to reproduce this issue on the clean installation ver 2.2.2 Open source include "Sample Data" which downloaded from GitHub repository.
See the video record 13889.webm.zip

[fronke]

Hi,

I also have the same problem since 2.2.2 but I still didn't figure out when it was happening exactly. It seems kind of random for now, but it happens most of the time between step 1 and 2 of checkout.

Please keep us informed if you find more about this.

Thanks

[magento-engcom-team]

Hello @akhileshlpatel
Please try to reproduce this issue on the clean installation (clear, fresh, without any custom themes, third-party extensions, etc.)2.2.2 Open source include "Sample Data" and tell us the result.

[akhileshlpatel]

Did you change the settings as per I mention? Is it working for you after making that catalog widget settings? As we have changed that settings for our client and it is working for them now. *Thanks,Akhilesh*

…

On Tue, Mar 6, 2018 at 2:55 PM, Kévin Fronteau ***@***.***> wrote: Hi, I also have the same problem since 2.2.2 but I still didn't figure out when it was happening exactly. It seems kind of random for now, but it happens most of the time between step 1 and 2 of checkout. Please keep us informed if you find more about this. Thanks — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#13889 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAb4ZkjGf8rfDL7u0gkG1nanRIRCOKfTks5tblX9gaJpZM4SWo9r> .

[darkrisingx]

Was having the same issue on 2.2.2 thought was a bug until after while upgraded to 2.2.3.

After upgrading to 2.2.3 it followed so I started to look into the issue. Found my issue as the magento team has stated to be a theme issue.

Looking into my theme the issue is something in my footer html not looked at my footer html yet but maybe I forgot to close a tag or something.

From your images the theme is modified from default so my guess is theme issue also.

UPDATE
Just looked into the html of my footer and sorta funny what was causing my issue. Html itself is fine it was <img src="#" /> that i've not yet created in my theme was just placeholder not got to finishing the footer yet.

Thankfully it's something simple.

[magento-engcom-team]

@akhileshlpatel
We are closing this issue due to inactivity. If you'd like to update it, please reopen the issue.