Upgrade to Magento 2.4.7 error in module-payment-services-base

[mahesh-makwana-web-vision]

Preconditions and environment

• Magento version: 2.4.7
• After upgrading from Magento 2.4.6 to 2.4.7 I receive the following error,

Steps to reproduce

Every time I try to access to payment method configuration (Stores -> Configuration -> Sales -> Payment Methods):

Error : {"0":"Warning: Undefined array key "children" in /var/www/vhosts/releases/55/vendor/magento/module-payment-services-base/Plugin/MovePaymentMethods.php on line 66","1":"#1}

Expected result

The page should be visible without any errors.

I found a useful solution at this link: Upgrade to Magento 2.4.7 - Error in Module Payment Services Base.

Is this the correct way to create a patch for it?

Actual result

Page showing Error.

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 @mahesh-makwana-web-vision. 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.

[mahesh-makwana-web-vision]

@magento I am working on this

[m2-assistant]

Hi @mahesh-makwana-web-vision! 👋
Thank you for collaboration. Only members of Community Contributors Team are allowed to be assigned to the issue. Please use @magento add to contributors team command to join Contributors team.

[mahesh-makwana-web-vision]

@magento add to contributors team

[m2-assistant]

Hi @mahesh-makwana-web-vision! 👋
Thank you for joining. Please accept team invitation 👉 here 👈 and add your comment one more time.

[mahesh-makwana-web-vision]

@magento I am working on this

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

[OvalMedia]

As a workaround you can disable the plugin from a custom module.
etc/adminhtml/di.xml:

<?xml version="1.0"?>
<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:framework:ObjectManager/etc/config.xsd">
    <type name="Magento\Paypal\Model\Config\Structure\PaymentSectionModifier">
        <plugin name="move_express_checkout_us_to_other_paypal_payment_solutions" disabled="true"/>
    </type>
</config>

[simonmaass]

we also just upgraded and have the same problem!

[engcom-Dash]

Hi @mahesh-makwana-web-vision

Thanks for reporting and collaboration.

Verified the issue on Magento 2.4 dev instance and the issue is not reproducible.

Steps to reproduce:

1. Upgrade from Magento 2.4.6 to 2.4.7
2. try to access to payment method configuration (Stores -> Configuration -> Sales -> Payment Methods)

We are not seeing any errors and are able to access the payment methods

Please refer the screenshots and let us know if we missed anything.

Before upgrading to 2.4.7

After upgrading to 2.4.7

Able to access payment methods without any errors