I found these snippets:

<?php

class Foo
{
    /** @param array<string, mixed> $array */
    public function foo(array $array): void {}
}

/** @psalm-method void foo(array $array) */
class Bar extends Foo
{
}

Psalm output (using commit 526debb):

No issues!

Can you perhaps create a reproducer in a separate repo then?

Can you make sure you don't have your cache folder in your config. Did you install the plugin for doctrine? Do you sometimes use psalm with only one file in in command line?

Can you perhaps create a reproducer in a separate repo then?

I tried to make a new repo with Doctrine and Symfony in order to reproduce this inconsistent error, but Psalm doesn't yield MethodSignatureMismatch in a brand new repo.
As I understand, Psalm should yield MethodSignatureMismatch in this minimal case, right? But it doesn't. https://psalm.dev/r/dd7372a1bf

Can you make sure you don't have your cache folder in your config.

My config is

<?xml version="1.0"?>
<psalm
    errorLevel="1"
    resolveFromConfigFile="true"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns="https://getpsalm.org/schema/config"
    xsi:schemaLocation="https://getpsalm.org/schema/config vendor/vimeo/psalm/config.xsd"
>
    <projectFiles>
        <directory name="src"/>
        <ignoreFiles>
            <directory name="vendor"/>
            <file name="src/Kernel.php"/>
        </ignoreFiles>
    </projectFiles>
    <forbiddenFunctions>
        <function name="dd"/>
        <function name="dump"/>
    </forbiddenFunctions>
    <plugins>
        <pluginClass class="Psalm\SymfonyPsalmPlugin\Plugin"/>
        <pluginClass class="Weirdan\DoctrinePsalmPlugin\Plugin"/>
    </plugins>
</psalm>

Did you install the plugin for doctrine?

Yes. Sorry, forgot to mention it.

Do you sometimes use psalm with only one file in in command line?

In CLI I use Psalm only as vendor/bin/psalm command, but I use PHPStorm built-in Psalm inspection, that relies on the Psalm instance installed in the project. I think the way how PHPStorm calls Psalm can be related to the issue indeed. It looks like Psalm doesn't yield MethodSignatureMismatch anymore when I close PHPStorm and clear Psalm's cache. It's interesting that right after the PHPStorm built-in inspection find MethodSignatureMismatch issue, the CLI Psalm instance still reports "No issues found!", it takes some time to yield MethodSignatureMismatch in the CLI too.

I found these snippets:

<?php

class Foo
{
    /** @param array<string, mixed> $array */
    public function foo(array $array): void {}
}

/** @psalm-method void foo(array $array) */
class Bar extends Foo
{
}

Psalm output (using commit 8c33b21):

No issues!

I think I already observed this bug but not through PHPStorm. It looked like this:

• Have a basic project with doctrine + doctrine plugin
• Run Psalm on a single file
• Doctrine plugin can't link entity with repository with such a limited scope
• Report on a single file emits an error
• Running psalm on full project use cache from single file analysis and re-emit the error that is no longer legit because repository is in scope

It may be more subtle than that but I was at work and couldn't spend a long time on this