Warning: Undefined array key "agreementId" in vendor/paypal/module-braintree-core/Plugin/AddAgreementsToMinicartConfig.php

[sw-tt-jaydeepcharadva]

Preconditions and environment

• Upgrading Magento Enterprise version from 2.4.3 - 2.4.5

Steps to reproduce

Steps to reproduce:

1. composer require magento/product-enterprise-edition=2.4.5 --no-update
2. composer require magento/magento-cloud-metapackage=2.4.5 --no-update
3. composer update
4. bin/magento deploy:mod:set developer
5. rm -rf var/di var/cache/ var/page_cache/ generated/code/
6. php bin/magento setup:upgrade
7. php bin/magento setup:di:compile
8. Go to Home page.
9. Exception #0 (Exception): Warning: Undefined array key "agreementId" in /vendor/paypal/module-braintree-core/Plugin/AddAgreementsToMinicartConfig.php on line 42

Note : This is warning message which is affected for developer mode only. If we change mode as default then that warning message falls into system.log file.

Expected result

Home page should be open and working.

Actual result

1 exception(s): Exception #0 (Exception): Warning: Undefined array key "agreementId" in /var/www/html/sapintegration/vendor/paypal/module-braintree-core/Plugin/AddAgreementsToMinicartConfig.php on line 42

Exception #0 (Exception): Warning: Undefined array key "agreementId" in /var/www/html/sapintegration/vendor/paypal/module-braintree-core/Plugin/AddAgreementsToMinicartConfig.php on line 42

#1 PayPal\Braintree\Plugin\AddAgreementsToMinicartConfig->afterGetConfig() called at [vendor/magento/framework/Interception/Interceptor.php:146]
#2 Magento\Checkout\Block\Cart\Sidebar\Interceptor->Magento\Framework\Interception\{closure}() called at [vendor/magento/framework/Interception/Interceptor.php:153]

### 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._
- [X] 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._
- [X] Severity: **S4** _- Affects aesthetics, professional look and feel, “quality” or “usability”._            

[m2-assistant[bot]]

Hi @sw-tt-jaydeepcharadva. Thank you for your report. To speed up processing of this issue, make sure that you provided the following information:

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

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.

:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

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

  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!

• [ ] 5. Add label Issue: Confirmed once verification is complete.

• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

Hi @sw-tt-jaydeepcharadva,

Thank you for reporting and collaboration.

We have verified the issue while upgrading Magento Enterprise version from 2.4.3 - 2.4.5. we are not able to reproduce the issue.

We are able to open to Home page and instance is working fine.

We have followed Magento upgrade guide https://experienceleague.adobe.com/docs/commerce-operations/upgrade-guide/implementation/perform-upgrade.html.Kindly go through with this document while upgrading the instance.

Kindly let us know if you are still facing any issue.

Kindly recheck the issue and check if any 3rd party extensions / modules enabled is causing this issue.

Thanks.

[engcom-Bravo]

Hi @sw-tt-jaydeepcharadva,

We have noticed that this issue has not been updated for a period of 14 Days.
Hence we assume that this issue is fixed now, so we are closing it. Please raise a fresh ticket or reopen this ticket if you need more assistance on this.

Thanks.