I’m facing an issue where logged-in customer details become unavailable in the online store theme after 24 hours, despite the customer remaining logged in with the new customer accounts feature. Below are the details to help diagnose and resolve this issue.
When a customer logs in using the new customer accounts system, their details (e.g., customer.email, customer.name) are initially accessible in the theme’s Liquid code. However, after approximately 24 hours, these details become unavailable
Hey @Ayush - I believe this may be expected behaviour, but I’ll dig into this further for you to confirm and loop back here once I have more info - speak with you soon!
@Alan_G - As you mentioned on this other thread, because the customer account is handled on another domain, it doesn’t appear to be available on the main storefront domain after the initial cookies disappear.
This feels very clearly to be a bug, as the user is effectively ‘logged out’ on the storefront and ‘logged in’ on the account pages.
Hey @TechSquid - thanks for reaching out. I’ve been able to connect with some folks internally about this cross-domain session behaviour, as like you mentioned, it does seem odd.
@Ayush - could you share any example shop URLs where you’re seeing this happen (and just confirm if the issue is happening on the live theme so we can replicate)? Having specific examples would really help us dig deeper into what’s going on here, hope to hear from you soon - we’ll get this looked at
Hey folks - just following up per Liam’s post in the other thread:
We’ve pushed a fix for this and it should be live as of now. If you do see the errors persist for new sessions, just ping us here and we can take a look!
I have a development store where I’m logged into the customer account. However, despite being logged in, the customer details are not showing up on the storefront via the liquid object.
Maybe the existing logged-in user sessions aren’t being properly reflected on the store’s frontend.
You’re on point here, the fix we deployed only affects new sessions created after the deployment, so an existing logged-in session wouldn’t be affected
Could you try logging out completely from your customer account by visiting /account/logout on your storefront. Then clear your browser cookies for both your storefront domain and the customer accounts domain.
This should create a new session that includes the fix, and the customer details should remain available on the storefront for 30 days.
Could you give that a try and let me know if it resolves the issue? If you’re still seeing problems after creating a new session, just let me know and we can take another look for sure.
Thanks again for your patience while we worked on this fix, really appreciated!
- I believe this may be expected behaviour, but I’ll dig into this further for you to confirm and loop back here once I have more info - speak with you soon!
