Bug: AutoloaderRegistry::getAutoloader returns array

[lbajsarowicz]

Preconditions (*)

1. Cloned magento/magento2 repository (without changes)
2. Installed Composer dependencies

Steps to reproduce (*)

1. Configure and run Integration Tests

Expected result (*)

1. Integration Tests should pass

Actual result (*)

1. Randomly you get error Error: Call to a member function findFile() on array (/var/www/html/lib/internal/Magento/Framework/Code/Generator/DefinedClasses.php:59)

Comments

Actual source of issue is in: \Magento\Framework\Autoload\AutoloaderRegistry::getAutoloader

magento2/lib/internal/Magento/Framework/Autoload/AutoloaderRegistry.php

Lines 37 to 44 in a31f4a3

	public static function getAutoloader()
	{
	if (self::$autoloader !== null) {
	return self::$autoloader;
	} else {
	throw new \Exception('Autoloader is not registered, cannot be retrieved.');
	}
	}

For some cases just composer dump-autoload helps, but it's not always the case.

[m2-assistant]

Hi @lbajsarowicz. 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.

@lbajsarowicz 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.

[slavvka]

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

• ab1b1de0294314503af16d5b346e5e2536542210
• 61bc535bc277a340fd43bf9722c331b2a08f5712

The fix will be available with the upcoming 2.4.0 release.