NullReferenceException when using .Callback

[oskaremil]

I have tried to attach a callback method to assert generated SQL sent.

            connectionMock
                .SetupDapperAsync(x => x.QueryAsync<Instant StartTime, long SecondCount)>(
                    It.IsAny<string>(),
                    It.IsAny<Parameters>(),
                    null, null, null))
                .Callback(
                    (string sql, Parameters, IDbTransaction transaction, int? commandTimeOut, CommandType? commandType) =>
                    {
                        // Assert
                    })
                .ReturnsAsync(new (Instant StartTime, long SecondCount)[0]);

I get the message System.NullReferenceException : Object reference not set to an instance of an object. on the same line as connectionMock.SetupDapperAsync is called.

Is this supported ?

The other parts work, if I remove the .Callback function everything runs fine

[KurtKroeker]

We just started using Moq.Dapper in our code, and we're having the same issue. Everything works great for mocking the Dapper function calls, but unfortunately attaching the callback fails, making verification that the mock was called difficult.

[dnovhorodov]

Same issue here. Defined callback call with lambda after .SetupDapperAsync returns System.NullReferenceException

[dubstepadii]

Issue still appears

[akrasp]

Still the same issue

[leontyl]

Nothing changed.

[heynineteen]

This is still a problem. Any idea of when this can be looked at?