Problem when trying to unset additional data in payment method.

[marcoaacoliveira]

Preconditions (*)

1. Magento 2.3.2 & PHP 7.2.21

Steps to reproduce (*)

1. You must use \Magento\Payment\Model\Info::setAdditionalInformation to add an additional information to a payment method;
2. Try to use \Magento\Payment\Model\Info::unsAdditionalInformation to remove the inserted additional data.

Expected result (*)

1. \Magento\Payment\Model\Info::unsAdditionalInformation should remove an additional information from table quote_payment column additional_information after save the quote.

Actual result (*)

1. \Magento\Payment\Model\Info::unsAdditionalInformation didn't remove the data in additional_information (column)

[m2-assistant]

Hi @marcoaacoliveira. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

@marcoaacoliveira do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

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

[m2-assistant]

Hi @marcoaacoliveira. 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).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components 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.

[VladimirZaets]

Hi @marcoaacoliveira. Thank you for your report.
The issue has been fixed in #26084 by @marcoaacoliveira in 2.4-develop branch
Related commit(s):

• 13f34cd6e15c0e1ce1b1183761d3ca4bfc318c22
• 32227d2773836da0574db70fac8aad46ac0dad83
• 77390c18c505f743367f2a8b1eec37514ba7bec3
• ad1059fb9a0abb316a6cb92b62ef9fee546f1f77
• 408b725157f031a81119cb27816d204d48b45b97

The fix will be available with the upcoming 2.4.0 release.