Magento 2.4.7 can not delete messages header in magento admin

[supp_younify]

We found this is a Magento bug, but we can't find a fix. When we want to dismiss system message, we can see an error in the console. This needs to be debugged in Knockout JS.

The error is

This issue is not critical, and this is not stopping Magento functionality. This part is only for system messages. 

If there is a fix for this problem, can you please send me the solution?

Thank you. 

[atiraowngm5c1c]

• Clear Cache:

  • Navigate to System > Cache Management in the admin panel.
  • Click on Flush Magento Cache and Flush Cache Storage.

• Check File and Folder Permissions:

  • Ensure that directories have permissions set to 755 and files to 644.

• Review Theme or Layout Modifications:

  • Switch to the default Luma theme temporarily to determine if the issue is theme-related.
  • If the problem resolves, the custom theme may need adjustments.

• Inspect JavaScript Errors:

  • Open the browser's developer tools (usually by pressing F12).
  • Check the Console tab for any JavaScript errors that might provide more insight.

[supp_younify]

When we want to dismiss system message, we can see an error in the console.

The error is

registry.js:57 Uncaught TypeError: Cannot read properties of undefined (reading 'apply')

    at registry.js:57:35

    at Registry._resolveRequest (registry.js:416:30)

    at Registry._addRequest (registry.js:383:22)

    at Registry.get (registry.js:227:18)

    at async (registry.js:56:22)

    at actions.js:256:31

    at _$1.each (underscore.js:1330:17)

    at actions.js:255:19

    at UiClass.applyAction (actions.js:160:17)

    at HTMLButtonElement.<anonymous> (knockout.js:4669:74)

[personalpaa034]

The issue has been recognized, and a fix is available through Amasty. To resolve this, you need to install a specific package.

First, open your terminal and navigate to your Magento root directory. Run the command composer suggest to check for recommended packages. Look for amasty/module-mage-2.4.7-fix in the list and install it using composer require amasty/module-mage-2.4.7-fix. Once the package is installed, it will automatically adjust the necessary code dependencies to fix the issue.

If you prefer a manual approach, you can visit the Amasty GitHub repository to download and install the fix yourself. This temporary solution should resolve the console error while dismissing system messages in the admin panel until Magento releases an official patch.