REST endpoint /customers/search not working for multi-store newsletter subscriptions

[moiashvin]

Preconditions (*)

1. Magento version 2.4.1
2. Magento 2.4-develop
3. Admin -> Stores -> Configuration -> Customers -> Customer Configuration -> Account Sharing Options and set Share Customer Accounts to Global

4. Multiple-store views setup in Magento

5. Have one customer ( [email protected] for ex.);

Steps to reproduce (*)

1. Go to Admin -> Customers -> All Customers and open customer for edit;
2. On left side, select Newsletter, to have the Newsletter Informaiton panel where all stores views are displayed.
3. Select more than 1 checkbox to subscriber customer to the store's newsletter and save customer
   (at this point, in Newsletter Subscribers view, customer is subscribed to newsletter for multiple-store views)

4. Use REST to call GET /V1/customers/search to retrieve the customer

V1/customers/search?searchCriteria[filterGroups][0][filters][0][field]=email&searchCriteria[filterGroups][0][filters][0][value]=[email protected]&searchCriteria[filterGroups][0][filters][0][conditionType]=eq

Expected result (*)

1. Customer details are returned correctly

Actual result (*)

1. Exception occurs.
   {
   "message": "Internal Error. Details are available in Magento log file. Report ID: webapi-xxx"
   }

2. And in the exception.log file:

[2020-12-07 10:36:54] main.CRITICAL: Report ID: webapi-5fce05c67a1e6; Message: Item (Magento\Customer\Model\Customer\Interceptor) with the same ID "1" already exists. {"exception":"[object] (Exception(code: 0): Report ID: webapi-5fce05c67a1e6; Message: Item (Magento\\Customer\\Model\\Customer\\Interceptor) with the same ID \"1\" already exists. at /var/www/html/magento24/lib/internal/Magento/Framework/Webapi/ErrorProcessor.php:208, Exception(code: 0): Item (Magento\\Customer\\Model\\Customer\\Interceptor) with the same ID \"1\" already exists. at /var/www/html/magento24/lib/internal/Magento/Framework/Data/Collection.php:408)"} []

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• [x ] 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 @moiashvin. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• 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, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant]

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

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

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

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - 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.

[magento-engcom-team]

✅ Confirmed by @engcom-Alfa
Thank you for verifying the issue. Based on the provided information internal tickets MC-39712 were created

Issue Available: @engcom-Alfa, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[korovitskyi]

@magento I am working on this

[magento-engcom-team]

Hi @moiashvin. Thank you for your report.
The issue has been fixed in #31261 by @korovitskyi in 2.4-develop branch
Related commit(s):

• f5cc98e68c00ff0e66d1dcc40b706e3bed1b7c98
• 66c3bff0b4c5aff1cfd1dd26bd7719bd622d8862
• b19a6dccb759e5cf0a494984467ea8efd9af3df5

The fix will be available with the upcoming 2.4.3 release.