Hi @rutvik-monpara. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.

  3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.

  4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

  5. Add label Issue: Confirmed once verification is complete.

  6. Make sure that automatic system confirms that report has been added to the backlog.
  To pick up a draggable item, press the space bar. While dragging, use the arrow keys to move the item. Press space again to drop the item in its new position, or press escape to cancel.

Hi @rutvik-monpara,

Thanks for your reporting and collaboration.

we have tried to reproduce the issue in Latest 2.4-develop instance and we are able to reproduce the issue.kindly refer the attached video.

Note : after cache clean it is working as expected.

store switch is not working.

Hence Confirming the issue.

Thanks.

✅ Jira issue https://jira.corp.adobe.com/browse/AC-14426 is successfully created for this GitHub issue.

✅ Confirmed by @engcom-Bravo. Thank you for verifying the issue.
Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

@magento I am working on this

We encountered issues with page caching behavior in Magento 2.4.8 under two specific scenarios: currency switching and guest-to-customer login after PLP cache.

Preconditions
Magento 2.4.8
Default Magento Luma theme (can be reproduced on custom themes as well)
Full Page Cache enabled (built-in cache)

1. Currency Switching Not Working Properly
Steps to reproduce:
Go to Stores > Configuration > Currency Setup > Allowed Currencies and add any additional currency (e.g., EUR).
On the Storefront, use the currency switcher in the header to select the added currency.

Expected Result:
The currency should switch, and prices should be updated accordingly.

Actual Result:
The currency remains the same (default one), and prices do not reflect the selected currency.

2. Guest Login After PLP Cache Returns Cached Content
Steps to reproduce:
Clear Magento cache: bin/magento cache:flush
As a guest, navigate to a category page, e.g., /bags.html
Log in as any existing customer.
Navigate again to the same category page (/bags.html)

Expected Result:
The page should be dynamically re-rendered for the logged-in customer (not served from guest cache).

Actual Result:
The page is served from the guest cache, showing incorrect content or layout for the logged-in user.

The Amasty team has prepared a fix for this issue as well as some others. To apply the fix, you need to run the following command: composer require amasty/module-mage-248-fix -W. For more details, see here: https://github.com/AmastyLtd/module-mage-248-fix .