Admin Usage Tracking causes JS error

[drinkingsouls]

Preconditions and environment

• Magento 2.4.2, 2.4.3, 2.4.4, 2.4.5, 2.4.6, 2.4.7
  As of this morning the Knowledge Centre feature has appeared in our Magento install. I've never seen this before.
  It is linked to the Admin system setting "Enable Admin Usage Tracking". This has always been enabled for us and I've never had the Knowledge Centre appear before.
• The Knowledge Centre is causing a JS error in our console. It conflicts with some Magento Dashboard settings.
• With Enable Admin Usage Tracking set to Yes. The "Role Resources" tab is no longer visible in User Roles.
• Causing issues loading product grids & products also.

!https://github.com/magento/magento2/assets/45666862/dab631d3-7870-4348-933f-300e6833a9b0!

!https://github.com/magento/magento2/assets/45666862/ef5193b3-da10-4827-bb07-38c000043541!

Steps to reproduce

• Enable Admin Usage Tracking > Yes
• Flush Cache
• Knowledge Centre link appears in Dashboard
• JS error present (console)

Expected result

Knowledge Centre is activated in Dashboard with no errors.

Actual result

Knowledge Centre is activated in Dashboard with errors.

Additional information

The Knowledge Centre only appeared on our install of Magento this morning. It has never been there previously.

Workaround

Enable Admin Usage Tracking > No
Or via CLI:
bin/magento config:set admin/usage/enabled 0;
bin/magento cache:clean;

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

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

[pixiemediaweb]

not just 2.4.6 - had this reported since around 11:30am (BST) on multiple sites; 2.4.3, 2.4.4, 2.4.5 etc.

[drinkingsouls]

@pixiemediaweb Where is this being reported?

[samcleathero]

Also experiencing this issue on 2.4.5-p1 - it looks like a change has been made to an externally loaded file (here) which is causing a RequireJS mismatched anonymous define error. It looks to me like this is occurring on line 22562 of the unminified file (here). Disabling Admin Usage Tracking prevents this file from loading so fixes the error.

[drinkingsouls]

Yes, I can confirm that setting Enable Admin Usage Tracking to No is a current workaround for us.

[pixiemediaweb]

@pixiemediaweb Where is this being reported?

by a number of our clients

[rbouma]

Confirmed. Problems with loading external JS file from Adobe causing this to not work on multiple clients on multiple Magento versions.

Temporarily solution from #37618 (comment) is also working for us

Thank you, @pixiemediaweb , for providing a temporary solution when unable to access the system configuration due to this issue > #37618 (comment)

[pixiemediaweb]

quick fix for those looking for a TLDR

bin/magento config:set admin/usage/enabled 0;
bin/magento cache:clean;

[willbrammer]

Experiencing this on both commerce, open-source clients varying from 2.4.4-2.4.6

Quick fix works for now

[enigmainteractiveuk]

Experiencing this issue on a range of 2.4.x Magento sites - turning off admin usage tracking also seems to have worked here. Is anybody aware of any official communications from Adobe about this issue?

[samcleathero]

Experiencing this issue on a range of 2.4.x Magento sites - turning off admin usage tracking also seems to have worked here. Is anybody aware of any official communications from Adobe about this issue?

Confirmed in the Magento Slack that Adobe are aware and looking into it.