Product Removed on Mobile Still Appears in Web's Mini Compare Section Until Re-login

[lintots]

Preconditions and environment

When a product is removed from the compare list via the mobile app using GraphQL, it is successfully removed from the mobile UI and from the main compare page on the web. However, the product still shows in the mini compare section (e.g., under My Account) on the web until the user logs out and logs back in.

Magento Version:
2.4.7-p3

Steps to reproduce

Steps to reproduce the behavior:

1. Login on mobile and web with the same user account.
2. Add products to the compare list using the following GraphQL mutation:

mutation {
addProductsToCompareList(
input: {
uid: "sssXyGZkTFksdPnxNoK1ut6OiV4bbchD",
products: ["3", "4"]
}
) {
uid
item_count
attributes {
code
label
}
items {
uid
product {
sku
name
description {
html
}
}
}
}
}

3. Remove products from the compare list using:

mutation {
removeProductsFromCompareList(
input: {
uid: "sssXyGZkTFksdPnxNoK1ut6OiV4bbchD",
products: ["3"]
}
) {
uid
item_count
attributes {
code
label
}
items {
uid
product {
sku
name
description {
html
}
}
}
}
}

4. Check the mini compare section on the web without logging out.

Expected result

The removed product should immediately disappear from all compare views on both mobile and web, including the mini compare section.

Actual result

The product is:

• Removed on mobile ✅
• Not visible on the main compare page on web ✅
• Still visible in the mini compare section on web ❌

Additional information

This suggests a caching or session state issue where the mini compare block on the web is not updating in real time with the backend or shared data source. Logging out forces a refresh and clears the stale entry.

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 @lintots. 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.

[m2-assistant]

Hi @engcom-November. 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.

[engcom-November]

Hello @lintots,

Thank you for your report and collaboration.

We’re unable to identify the issue you're referring to. Could you please clarify which mobile app you’re experiencing the problem with? Additionally, it would be helpful if you could provide more details and the steps to reproduce the issue.

Thank you!

[Syamsg]

Hi @engcom-November , I think the issue is that even after removing a product from the compare list in Magento 2 using GraphQL, it still appears in the mini compare list. I added a product to the compare list using GraphQL, and then removed it using GraphQL. Although the product is removed from the main compare list, it still shows up in the mini compare list.

mutation { removeProductsFromCompareList( input: { uid: "KsaJcluNrXkpGEom7Ux6cjXzeiDHyYWk", products: ["158"] } ) { uid item_count attributes { code label } items { uid product { sku name description { html } } } } }

In the above image only have one product to compare.

In here we can see two product in compare list.

[engcom-November]

Hello @lintots ,

Thank you for your report and collaboration.

We attempted to reproduce the issue in the latest 2.4-develop instace and We are able to reproduce the issue. Please refer to the attached screenshot for details.

Steps to reproduce the behavior:

• Login on mobile and web with the same user account.
• Add products to the compare list using the following GraphQL mutation:

mutation {
addProductsToCompareList(
input: {
uid: "sssXyGZkTFksdPnxNoK1ut6OiV4bbchD",
products: ["3", "4"]
}
) {
uid
item_count
attributes {
code
label
}
items {
uid
product {
sku
name
description {
html
}
}
}
}
}

Remove products from the compare list using:
mutation {
removeProductsFromCompareList(
input: {
uid: "sssXyGZkTFksdPnxNoK1ut6OiV4bbchD",
products: ["3"]
}
) {
uid
item_count
attributes {
code
label
}
items {
uid
product {
sku
name
description {
html
}
}
}
}
}

• Check the mini compare section on the web without logging out.

We followed the preconditions and steps as provided and encountered the issue.

Therefore, we are marking this ticket as "Issue: Confirmed."

Thank You!