Magento Analytics must be decoupled

[IbrahimS2]

Preconditions and environment

• Magento version: 2.4.7
• Anything else that would help a developer reproduce the bug: Add the following in your composer json file:

    "replace": {
        "magento/module-analytics": "*",
        "magento/module-admin-analytics": "*",
        "magento/module-cms-page-builder-analytics": "*",
        "magento/module-customer-analytics": "*",
        "magento/module-catalog-analytics": "*",
        "magento/module-quote-analytics": "*",
        "magento/module-review-analytics": "*",
        "magento/module-sales-analytics": "*",
        "magento/module-wishlist-analytics": "*",
        "magento/module-page-builder-analytics": "*",
        "magento/module-page-builder-admin-analytics": "*"
}

Steps to reproduce

This error when running indexer using cli and after digging in it is used by the following module:

vendor/magento/module-query-xml/Model/Config/Config.php: * Config of ReportXml
vendor/magento/module-query-xml/Model/Config/ConfigInterface.php: * Interface for ReportXml Config
vendor/magento/module-query-xml/Model/Config/ConfigInterface.php:     * Config of ReportXml
vendor/magento/module-query-xml/etc/di.xml:            <argument name="converter" xsi:type="object">Magento\Analytics\ReportXml\Config\Converter\Xml</argument>
vendor/magento/module-data-exporter/etc/di.xml:            <argument name="converter" xsi:type="object">Magento\Analytics\ReportXml\Config\Converter\Xml</argument>
vendor/magento/module-data-exporter/Config/Config.php: * Config of ReportXml

Expected result

The shop must operate normally

Actual result

Class "Magento\Analytics\ReportXml\Config\Converter\Xml" does not exist

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 @IbrahimS2. 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. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• 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-Dash. 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

     - 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!

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[engcom-Dash]

Hi @IbrahimS2

Thanks for reporting and collaboration.

Verified the issue on Magento 2.4.7 and the issue is reproducible.

Steps to reproduce:

1. Install 2.4.7 instance
2. Add the following code in composer.json file

"replace": {
        "magento/module-analytics": "*",
        "magento/module-admin-analytics": "*",
        "magento/module-cms-page-builder-analytics": "*",
        "magento/module-customer-analytics": "*",
        "magento/module-catalog-analytics": "*",
        "magento/module-quote-analytics": "*",
        "magento/module-review-analytics": "*",
        "magento/module-sales-analytics": "*",
        "magento/module-wishlist-analytics": "*",
        "magento/module-page-builder-analytics": "*",
        "magento/module-page-builder-admin-analytics": "*"
}

3. Perform bin/magento in:rein
4. Verify if the Magento instance is working or not

We are getting the below error after performing reindexing

Class "Magento\Analytics\ReportXml\Config\Converter\Xml" does not exist

Hence, Confirming the issue.

Please take a look at the screenshots I've attached

Added the above code in composer.json

Error message after performing bin/magento in:rein :

[github-jira-sync-bot]

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

[m2-assistant]

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