Magento 2.4.2 composer upgrade broke after 2.4.3 released

[EliminatorRC-Christian]

I am currently in the process of upgrading Magento 2.2.6 to 2.4.2. I had a stable upgrade working prior to 2.4.3 being released. After Tuesday, August 10 when 2.4.3 was released, when I composer upgrade our installation with:

composer require magento/product-community-edition 2.4.2 --no-update
composer require --dev phpunit/phpunit:^9 friendsofphp/php-cs-fixer:~2.16.0 lusitanian/oauth:~0.8.10 pdepend/pdepend:~2.7.1 sebastian/phpcpd:~5.0.0 squizlabs/php_codesniffer:3.5.4 --no-update
composer remove --dev sjparkinson/static-review fabpot/php-cs-fixer --no-update
composer require msp/recaptcha 2.2.2 --no-update
composer require picqer/php-barcode-generator --no-update
composer update

I then enabled MSI modules. During bin/magento inventory:reservation:list-inconsistencies -r | bin/magento inventory:reservation:create-compensations I had problems where each inconsistency would throw an error saying 'caused exception "Area code is not set"'. I fixed this problem by manually setting the state in vendor/magento/module-inventory-reservation-cli/Command/CreateCompensations.php. I did not have to do this workaround prior to Tuesday.

After fixing this bug it appears my paid extensions (which hasn't been upgraded yet) now have errors.
There may be more bugs but I currently can't browse the storefront due to these errors.

Was the repository for 2.4.2 updated with the release of 2.4.3? I went from having a stable upgrade to an upgrade full of errors and the only thing that has changed is the new version of Magento releasing.

[m2-assistant]

Hi @EliminatorRC-Christian. 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.

Please, add a comment to assign the issue: @magento I am working on this

---

• 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, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

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

[davidandersson1]

After finished, composer update of 2.4.3, I am facing same error "Area code is not set" with command "setup:upgrade".

Also klarna checkout installation (through command: composer require klarna/m2-checkout) not working with 2.4.3 and its throw Conclusion: don't install klarna/m2-checkout 9.2.4|install ramsey/uuid 3.9.4

Please help if any body faced same issue and got any solution for same!

[hostep]

@davidandersson1: you should report that problem to Klarna, Magento increased the dependency on ramsey/uuid from v3 to v4 in Magento 2.4.3 and probably that Klarna module only supports v3 at the moment.

[davidandersson1]

@hostep thanks for you quick reponse, we already reported to klarna for same. is there any update regarding one more issue related "Area code is not set" with command "setup:upgrade"?

[hostep]

There is a PR that fixes one such issue: #33726, but I'm not sure if that is the same as your issue.
Would be great if you could try to debug somehow and figure out what sets the area in your specific case (probably in some constructor of some class that is called by a magento command somewhere)

[davidandersson1]

Hi @hostep its same issue(app/code/Magento/Payment/Helper/Data.php) for us, so is there any patch to resolve the bug or how?

[m2-assistant]

Hi @engcom-Delta. 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!

• 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-Delta]

Hi @EliminatorRC-Christian,

Hope this issue is resolved , if not , kindly provide issue description , steps to reproduce and expected results.

Thanks