Caching issue per theme based on User Agent Rules

[konstantinos158358]

Preconditions and environment

• Magento ver. 2.4.7-p3
• Php : 8.3.15
• composer create-project --repository-url=https://repo.magento.com/ magento/project-community-edition
• bin/magento setup:install --base-url="WEBSITE_URL" --base-url-secure="WEBSITE_URL" --backend-frontname="mybackend" --session-save="files" --db-host="localhost" --db-name="XXXXX" --db-user="XXXXX" --db-password="XXXXX" --admin-firstname="XXXXX" --admin-lastname="XXXXX" --admin-email="email@example.com" --admin-user="XXXXX" --admin-password="XXXXX" --language="en_US" --currency="EUR" --timezone="Europe/Athens" --use-rewrites="1"
• bin/magento setup:upgrade (successfully)
• bin/magento setup:di:compile (successfully)
• bin/magento deploy:mode:set developer (successfully)
• bin/magento cache:flush (successfully)

Frontend working properly
Admin working properly

Steps to reproduce

From Admin area navigate to:

• Content | Design | Configuration
  
• Edit the parent theme
  
• Select Magento Blank as Applied Theme and Magento Luma as theme for mobile devices and Save Configuration [User Agent Rule: /iPhone|iPod|BlackBerry|Palm|Googlebot-Mobile|Mobile|mobile|mobi|Windows Mobile|Safari Mobile|Android|Opera Mini/]
  
• Clear all caches and keep them enable.
  

1. From Destop device navigate to default Magento Homepage
   
2. From Mobile device navigate to default Magento Homepage
   
3. From Destop device navigate to default Magento Homepage
   

Expected result

From Desktop device, homepage should keep as applied theme the Magento Blank, as selected from configuration settings.

Actual result

From Desktop device, homepage applied as theme the Magento Luma which selected only for mobile devices.

Additional information

No response

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @konstantinos158358. 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.

[konstantinos158358]

@magento I am working on this

[m2-assistant]

Hi @konstantinos158358! 👋
Thank you for collaboration. Only members of Community Contributors Team are allowed to be assigned to the issue. Please use @magento add to contributors team command to join Contributors team.

[konstantinos158358]

@magento add to contributors team

[m2-assistant]

Hi @konstantinos158358! 👋
Thank you for joining. Please accept team invitation 👉 here 👈 and add your comment one more time.

[konstantinos158358]

@magento add to contributors team

[m2-assistant]

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.