Random issues in backend

[hanaks]

Preconditions and environment

Magento version 2.4.5

Steps to reproduce

Either happens always on almost all pages in backend, or doesn't happen at all. Could be related to network delays affecting loading order of external scripts.

Expected result

No errors.

Actual result

Random JavaScript errors in backend.

Additional information

It seems that there is some random issue with Magento_AdminAnalytics module.

I started to get various JavaScript errors like these from the sudden in backend, causing stuck loaders on grids or menu not working in backend:

Uncaught Error: Mismatched anonymous define() module: function(){return cr} Uncaught TypeError: $(...).ready is not a function Uncaught TypeError: Cannot set properties of undefined (setting 'mage')

The errors disappeared after setting "Stores > Configuration > ADVANCED > Admin > Admin Usage > Enable Admin Usage Tracking" to "No".

Could be related to some network delay loading external scripts. The errors started at the same time on a hosted server and on a local dev server while no changes were made on the hosted server.

I remember the same issues long time ago at times of Magento 2.2 or similar. This could be one of the random errors which killed Magento 2.

Release note

No response

Triage and priority

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [X] 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[bot]]

Hi @hanaks. 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. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: 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.

[hostep]

This is most likely a duplicate of:

• https://github.com/magento/magento2/issues/37618
• https://github.com/magento/magento2/issues/37627

For now, you can disable admin analytics, that seems to be what works for everyone (but it looks like you've already figured this out yourself).

[m2-assistant[bot]]

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: :point_down:

• [ ] 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.

[hanaks]

This is most likely a duplicate of:

• Admin Usage Tracking causes JS error #37618
• Help Center Widget #37627

For now, you can disable admin analytics, that seems to be what works for everyone (but it looks like you've already figured this out yourself).

Now I recall that the issues at times of Magento 2.2 were also related to some sort of popup from "Admin Usage Tracking", so the current errors could be caused by the "help center widget" rather than network delays.

[hanaks]

When I add a JavaScript break point to code which calls the $(...).ready function then everything works, maybe because it gives time for js files to load. So maybe it's caused by loading order of js files?

[drinkingsouls]

Yes, this sounds like issue 37618 Try disabling the Admin Usage Tracking setting as mentioned in that thread and see if that temporarily resolves the JavaScript errors.

[hanaks]

Disabling "Admin Usage Tracking" fixes the errors, see ticket.

[engcom-Bravo]

@hostep @drinkingsouls Thanks for your contribution & collaboration over here.

HI @hanaks,

Thank you for reporting and collaboration.

Similar issue has been confirmed here https://github.com/magento/magento2/issues/37618 Kindly move onto this issue for latest updates / solutions on the same.We are closing this as duplicate.

Thank you.