Upgrade from 2.4.3-p1 to 2.4.4 throws terminal error "Fatal error: During inheritance of Countable"

[FadedOut]

UPDATE: THANKS to @loic-paquin for helping pinpoint a change in process with upgrading to 2.4.4. Please see comment 7 for solution!

Preconditions (*)

1. Magento 2.4.3-p1
2. Production Mode
3. Apache 2.4 (no NGINX)
4. mod_mpm_worker
5. PHP 7.4.23
6. Elasticsearch 7.12.1
7. Redis 6.2.6
8. MariaDB 10.3.34
9. Composer 2.1.6 (then upgraded to 2.3.5 because of the errors below thinking this would help but it made no difference)
10. RabbitMQ 3.9.14
11. PHP-FPM: on
12. PHP Handler: fcgi
13. Followed: https://devdocs.magento.com/guides/v2.4/install-gde/prereq/php-settings.html

Steps to reproduce (*)

These are the steps I did (in this exact order) then receive the error shown below (in terminal). M2.4.3-p1 worked fine btw.

1. I was on PHP 7.4.23 - I changed to PHP 8.1.4
2. Ran the following:

• composer require magento/product-community-edition 2.4.4 --no-update
• composer require magento/composer-root-update-plugin ~2.0 --no-update
• composer upgrade

3. It appeared to complete the files to download/update because it displayed the "generating autoload files" and "funding" lines at the end (no errors).
4. I tried running "rm -rf var/cache/* ; rm -rf var/page_cache/* ; rm -rf generated/code/* ; bin/magento setup:upgrade"

Expected result (*)

1. Magento 2.4.4 to work as intended.

Actual result (*)

1. After running "step 4" above, it simply throws the error shown below. No magento command works - the only command that works is "composer upgrade".

Can't run any of the following without error (with or without php before command):

• bin/magento maintenance:disable
• bin/magento setup:upgrade
• bin/magento setup:di:compile

2. Error Report:
   ----ERRORS SHOWN IN CONSOLE/TERMINAL (when executing any command with PHP 8.1)-----

Fatal error: During inheritance of Countable: Uncaught Exception: Deprecated Functionality: Return type of Composer\Repository\ArrayRepository::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/*****/public_html/vendor/composer/composer/src/Composer/Repository/ArrayRepository.php on line 277 in /home/*****/public_html/vendor/magento/framework/App/ErrorHandler.php:61
Stack trace:
#0 /home/*****/public_html/vendor/composer/composer/src/Composer/Repository/ArrayRepository.php(28): Magento\Framework\App\ErrorHandler->handler(8192, 'Return type of ...', '/home/*****/publi...', 277)
#)1 /home/*****/public_html/vendor/composer/ClassLoader.php(571): include('/home/*****/publi...')
#)2 /home/*****/public_html/vendor/composer/ClassLoader.php(428): Composer\Autoload\includeFile('/home/*****/publi...')
#)3 /home/*****/public_html/vendor/composer/composer/src/Composer/Repository/PlatformRepository.php(31): Composer\Autoload\ClassLoader->loadClass('Composer\\Reposi...')
#)4 /home/*****/public_html/vendor/composer/ClassLoader.php(571): include('/home/*****/publi...')
#)5 /home/*****/public_html/vendor/composer/ClassLoader.php(428): Composer\Autoload\includeFile('/home/*****/publi...')
#)6 /home/*****/public_html/vendor/composer/composer/src/Composer/Package/Loader/ValidatingArrayLoader.php(375): Composer\Autoload\ClassLoader->loadClass('Composer\\Reposi...')
#)7 /home/*****/public_html/vendor/composer/composer/src/Composer/Package/Loader/RootPackageLoader.php(70): Composer\Package\Loader\ValidatingArrayLoader::hasPackageNamingError('magento/project...')
#)8 /home/*****/public_html/vendor/composer/composer/src/Composer/Factory.php(368): Composer\Package\Loader\RootPackageLoader->load(Array, 'Composer\\Packag...', '/home/*****/publi...')
#)9 /home/*****/public_html/vendor/composer/composer/src/Composer/Factory.php(595): Composer\Factory->createComposer(Object(Composer\IO\BufferIO),Array, false)
#)10 /home/*****/public_html/vendor/magento/framework/Composer/ComposerFactory.php(47): Composer\Factory::create(Object(Composer\IO\BufferIO), '/home/*****/publi...')
#)11 /home/*****/public_html/vendor/magento/framework/Composer/ComposerInformation.php(368): Magento\Framework\Composer\ComposerFactory->create()
#)12 /home/*****/public_html/vendor/magento/framework/Composer/ComposerInformation.php(381): Magento\Framework\Composer\ComposerInformation->getComposer()
#)13 /home/*****/public_html/vendor/magento/framework/Composer/ComposerInformation.php(244): Magento\Framework\Composer\ComposerInformation->getLocker()
#)14 /home/*****/public_html/vendor/magento/framework/App/ProductMetadata.php(120): Magento\Framework\Composer\ComposerInformation->getSystemPackages()
#)15 /home/*****/public_html/vendor/magento/framework/App/ProductMetadata.php(80): Magento\Framework\App\ProductMetadata->getSystemPackageVersion()
#)16 /home/*****/public_html/vendor/magento/framework/Console/Cli.php(98): Magento\Framework\App\ProductMetadata->getVersion()
#)17 /home/*****/public_html/bin/magento(22): Magento\Framework\Console\Cli->__construct('Magento CLI')
#)18 {main} in /home/*****/public_html/vendor/composer/composer/src/Composer/Repository/ArrayRepository.php on line 28

---

-------ERROR SHOWN IN SYSTEM.LOG (when executing: php bin/magento setup:upgrade with PHP 7.4)-------
main.CRITICAL: Type Error occurred when creating object: Magento\Framework\Communication\Config\Data, Magento\Framework\Reflection\TypeProcessor::resolveFullyQualifiedClassName(): Argument #2 ($typeName) must be of type string, null given, called in /home/*****/public_html/vendor/magento/framework/Reflection/TypeProcessor.php on line 550

---

I apologize if I did something wrong. I don't wish to waste anyone's time. I've spent hours trying to figure out why it's doing this before posting this report, to try and make sure it's not on my end. And I tried researching and there isn't much on this. Hopefully the error log points to a bug.

EDIT: Updated my command processes - with same outcome. Just to clarify.
EDIT2: Learning more as I keep trying. Something is up with the PHP changes in Magento I think,
EDIT3: Solution info added to top of OP

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• [-] 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 @FadedOut. 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.

⚠️ 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.

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

[loic-paquin]

Hey, I got the same issue, what saved me was :

composer require magento/composer-root-update-plugin ~2.0 --no-update
composer require-commerce magento/product-community-edition 2.4.4 --no-update
composer update

https://experienceleague.adobe.com/docs/commerce-operations/upgrade-guide/prepare/prerequisites.html?lang=en
https://experienceleague.adobe.com/docs/commerce-operations/upgrade-guide/implementation/perform-upgrade.html

[FadedOut]

Hey, I got the same issue, what saved me was :

composer require magento/composer-root-update-plugin ~2.0 --no-update
composer require-commerce magento/product-community-edition 2.4.4 --no-update
composer update

https://experienceleague.adobe.com/docs/commerce-operations/upgrade-guide/prepare/prerequisites.html?lang=en https://experienceleague.adobe.com/docs/commerce-operations/upgrade-guide/implementation/perform-upgrade.html

Hello,

Thank you for your help on this. Unfortunately, I tried exactly that before modifying composer.json manually. The funny part is, I actually looked at that exact site the first time I tried to update. I ran across this error:

"Command "require-commerce" is not defined."

So I assumed something was wrong with the command and went for composer.json instead. But seeing how you mentioned to do it that way I tried again just now. It seems it is a typo.

--This goes through but when doing composer update it says invalid pacakge:--
composer require commerce-magento/product-community-edition 2.4.4 --no-update

--THIS is the correct command:--
composer require magento/product-community-edition 2.4.4 --no-update

But in the end, that did what I did by modifying the composer.json manually. I also saw on that site you linked about the composer-root-update-plugin - I did this as well in my initial trials - I should have put that in the OP - dang. Knew I was missing something.

SUMMARY:
Still no fix. Still throws that same error even with running these three commands. Thank you for trying though, any help is very much appreciated.

composer require magento/composer-root-update-plugin ~2.0 --no-update
composer require magento/product-community-edition 2.4.4 --no-update
composer update

[loic-paquin]

"Command "require-commerce" is not defined."
My Bad :

composer require magento/composer-root-update-plugin ~2.0 --no-update
composer update

It will add the command require-commerce.

The problem you may encouter here is that you're already in php 8.1 but magento 2.4.3 expects php7.4. In this case, composer will fail.
In order to fix this you can use update-alternatives --config php to select the php version used by linux.

[FadedOut]

Oh not your fault at all, it's actually a typo on that site you linked. And I'm not sure I understand what you mean when you "It will add the command require-commerce".

But with more testing and your ideas, it does appear to be something up with the PHP versions.

So I did originally try doing it with PHP 7.4 first and it failed half way through when doing the "php bin/magento setup:upgrade" with this error:

Type Error occurred when creating object: Magento\Framework\Communication\Config\Data, Argument 2 passed to Magento\Framework\Reflection\TypeProcessor::resolveFullyQualifiedClassName() must be of the type string, null given, called in /home/cmp/public_html/vendor/magento/framework/Reflection/TypeProcessor.php on line 550

Throws that right after the

Schema post-updates:
Module 'Magento_Amqp':

So that's when I assumed it needed to be on PHP8.1. Then when switching to 8.1 I received the other larger error where no command works at all. It says it is compatible with PHP8.1 so I'm not sure what I'm doing wrong :(

This is odd because I have updated from 2.4.1 -> 2.4.2 -> 2.4.3 -> 2.4.3-p1. Had no issues like this. Must be the PHP changes, IDK.

I do appreciate your help though.

[loic-paquin]

There is no typo, The correct syntax is :

composer require-commerce magento/product-community-edition 2.4.4 --no-update

as stipulated : WARNING
The procedure for upgrading Adobe Commerce and Magento Open Source has changed. You must install a new version of the magento/composer-root-update-plugin package (see prerequisites). In addition, the commands for upgrading have changed from composer require magento/<package_name> to composer require-commerce magento/<package_name>.

And I'm not sure I understand what you mean when you "It will add the command require-commerce".
It will allow you to use composer require-commerce for the next step.

I got confused too with require-commerce. But once I installed with this method, it was OK. I'm still facing issues with custom modules but it's not Magento's fault.

Also you definitely need to launch bin/magento setup:upgrade with php 8.1

[henryyyt]

For me it was solved after I added types to all interfaces in my custom module.

Example:

public function get($storeCode); -> public function get(string $storeCode);

[FadedOut]

There is no typo, The correct syntax is :

composer require-commerce magento/product-community-edition 2.4.4 --no-update

as stipulated : WARNING The procedure for upgrading Adobe Commerce and Magento Open Source has changed. You must install a new version of the magento/composer-root-update-plugin package (see prerequisites). In addition, the commands for upgrading have changed from composer require magento/<package_name> to composer require-commerce magento/<package_name>.

And I'm not sure I understand what you mean when you "It will add the command require-commerce". It will allow you to use composer require-commerce for the next step.

I got confused too with require-commerce. But once I installed with this method, it was OK. I'm still facing issues with custom modules but it's not Magento's fault.

Also you definitely need to launch bin/magento setup:upgrade with php 8.1

That is crazy, I understand there was that warning box but really? Just a single small blip on this? I think it should have been on the 2.4.4 release notes as well or something (unless it was there as well and I missed it there too? If so ugh - I read that whole thing too :( ).

But, that indeed DID IT :) THANK YOU!

The step I was missing out on and to help anyone else that comes across this odd issue/change:

1. STAY IN PHP 7.4
2. composer require magento/composer-root-update-plugin ~2.0 --no-update
3. composer update
4. rm -rf var/cache/* ; rm -rf var/page_cache/* ; rm -rf generated/code/* ; bin/magento setup:upgrade
5. composer require-commerce magento/product-community-edition 2.4.4 --no-update
6. composer update
7. CHANGE TO PHP 8.1
8. rm -rf var/cache/* ; rm -rf var/page_cache/* ; rm -rf generated/code/* ; bin/magento setup:upgrade

It still failed throwing the "main.CRITICAL: Type Error occurred when creating object:" half way through the upgrade process, but when you said about the modules not being compatible it made me think maybe it was a module failing. I assumed when I did composer update it would say which were not compatible with the new version. But dur, I didn't change to PHP 8.1 until after running composer update the second time. So I disabled a bunch of the modules I had and it finished 100%. 👍

I much appreciate the help on this. In the end it seems it was me that somewhat messed up. But at least with this ticket/bug report, anyone else coming across this same problem can be helped.

@henryyyt thank you for that info as well. That will help to fix up some modules to get them compatible with PHP 8.1. For now, disabling them was the quickest solution for me.

[C4rter]

I still have that issue with PHP 8.1.3.

No matter what I do, it keeps saying:

PHP Fatal error:  During inheritance of Countable: Uncaught Exception: Deprecated Functionality: Return type of Composer\Repository\ArrayRepository::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/composer/composer/src/Composer/Repository/ArrayRepository.php on line 277 in /var/www/html/vendor/magento/framework/App/ErrorHandler.php:61

when I try to run any Magento command like bin/magento setup:upgrade after upgrading to 2.4.4 and switching to PHP 8.1.

It seems the composer folder in vendor/composer is old or something?
But even when I deleted it and recreated it with composer install, it stays the same.

My count function in vendor/composer/composer/src/Composer/Repository/ArrayRepository.php looks like this:

/**
     * Returns the number of packages in this repository
     *
     * @return int Number of packages
     */
    public function count()
    {
        if (null === $this->packages) {
            $this->initialize();
        }

        return count($this->packages);
    }

[FadedOut]

@C4rter Yup that sounds like exactly what I was going through. For the lack of sounding repetitive, but to cover all bases, did you read all the previous posts?

Specifically, did you follow the steps I found to work for me exactly? Here:

1. STAY IN PHP 7.4
2. composer require magento/composer-root-update-plugin ~2.0 --no-update
3. composer update
4. rm -rf var/cache/* ; rm -rf var/page_cache/* ; rm -rf generated/code/* ; bin/magento setup:upgrade
5. composer require-commerce magento/product-community-edition 2.4.4 --no-update
6. composer update
7. CHANGE TO PHP 8.1
8. rm -rf var/cache/* ; rm -rf var/page_cache/* ; rm -rf generated/code/* ; bin/magento setup:upgrade

Staying with PHP 7.4 all the way to the end is very important. Also, making sure to update to the new 'composer-root-update-plugin' properly is important as well (doing composer require then composer update then rm those folders then setup:upgrade). I missed the step of doing the composer update & setup:upgrade my first time around, so the new command of "composer require-commerce" didn't work for me and I went with the old way of "composer require magento/..." which was not correct.

If you follow that precisely it should work as intended. The error you're getting is the exact one I got and this fixed it for me.

[C4rter]

Thank you for the reply.

I did it the same way you did at the beginning, so the wrong way.

So at first I did not do:
composer require magento/composer-root-update-plugin ~2.0 --no-update
composer require-commerce magento/product-community-edition 2.4.4 --no-update
Just plain old composer require.

And everything was fine when still using PHP 7.4. That was no issue.

But now I switched to 8.1 and the issues started.

Then I found your post and I switched back to 7.4 and did that.
composer require-commerce also works as it should.

But it didn't change anything in the vendor/composer/composer/src/Composer/Repository/ArrayRepository.php file for me.
That's still old and stays old, even when I delete it and it's recreated with composer install.

I'm clueless what actually changes that contents folder and why it's old.

Can you show how your count() function in vendor/composer/composer/src/Composer/Repository/ArrayRepository.php looks like?

[FadedOut]

I'll attach the file - but oddly mine says it was updated yesterday along with every other file in that folder - which is when I think I was in the middle of trying to figure this out. So I'm not sure honestly when/which version this file is. And simply replacing this file with yours or making changes is probably not the best course of action. It should update correctly if the steps are done in the right order.

So, that error I resolved without doing any file modifications. My 2.4.3-p1 was working great when I updated, so no previous bugs/problems/errors. Then I simply did the steps I just posted (thanks to the help from @loic-paquin pointing out my mistake) and my problem was solved.

Just make sure to run composer update after updating the "composer-root-update-plugin". If you still end up with problems, you'll need to post your exact steps 1 by 1 so I can see where you're going wrong. Also follow my "preconditions" listed in OP, to make sure you at least have the same versions of stack as I do. Most of what I have is required by Magento (things like my Elasticsearch is somewhat off but so far seems to be okay).

ArrayRepository.php in zip attached - this file also states it's part of composer. This "updated file" might be from when I updated to 2.3.5, which might look different from yours depending on your composer version.
ArrayRepository.zip