Attempted to call an undefined method named "introspectSchema" of class "Doctrine\DBAL\Schema\PostgreSQLSchemaManager"

[FluffyDiscord]

Q	A
auditor-bundle version	5.2.1
PHP version	v8.1.13
Database	PostgreSQL
Doctrine ORM	2.13.1
Doctrine DBAL	3.4.0
Symfony	6.1.2

Summary

Running php bin/console audit:schema:update throws Attempted to call an undefined method named "introspectSchema" of class "Doctrine\DBAL\Schema\PostgreSQLSchemaManager".

Exception trace:
  at /var/www/app/vendor/damienharper/auditor/src/Provider/Doctrine/Persistence/Schema/SchemaManager.php:120
 DH\Auditor\Provider\Doctrine\Persistence\Schema\SchemaManager->getUpdateAuditSchemaSql() at /var/www/app/vendor/damienharper/auditor/src/Provider/Doctrine/Persistence/Command/UpdateSchemaCommand.php:66
 DH\Auditor\Provider\Doctrine\Persistence\Command\UpdateSchemaCommand->execute() at /var/www/app/vendor/symfony/console/Command/Command.php:308
 Symfony\Component\Console\Command\Command->run() at /var/www/app/vendor/symfony/console/Application.php:1016
 Symfony\Component\Console\Application->doRunCommand() at /var/www/app/vendor/symfony/framework-bundle/Console/Application.php:94
 Symfony\Bundle\FrameworkBundle\Console\Application->doRunCommand() at /var/www/app/vendor/symfony/console/Application.php:299
 Symfony\Component\Console\Application->doRun() at /var/www/app/vendor/symfony/framework-bundle/Console/Application.php:80
 Symfony\Bundle\FrameworkBundle\Console\Application->doRun() at /var/www/app/vendor/symfony/console/Application.php:171
 Symfony\Component\Console\Application->run() at /var/www/app/vendor/symfony/runtime/Runner/Symfony/ConsoleApplicationRunner.php:54
 Symfony\Component\Runtime\Runner\Symfony\ConsoleApplicationRunner->run() at /var/www/app/vendor/autoload_runtime.php:29
 require_once() at /var/www/app/bin/console:11

Current behavior

Throws an exception

How to reproduce

Run php bin/console audit:schema:update

Expected behavior

Create the schema, so auditing works.

[DamienHarper]

@FluffyDiscord thanks for the report, this is fixed in 2.4.1 release (thanks to @dmitryuk)