PostgresNIO.PSQLError (backing: PostgresNIO.PSQLError. (unknown context at $10160e44c). Backing)

[Muning69]

bug

The original project was running well, and everything logged in was normal. No code changes have been made, only the latest version of Vapor has been updated. As a result, the app's account cannot be logged in.

If you intentionally use the wrong account password to log in, you will normally report that your identity has not been verified.
But if the correct account password is used for login, it will report:
PostgresNIO.PSQLError (backing: PostgresNIO.PSQLError. (unknown context at $10160e44c). Backing)

It's really strange to have this problem. Once again, confirm that the original project code has not been changed. Everything was originally normal.

I am using the Postgres database.

I tried using both the old and new versions of the database registration API, but the problem remained the same.

I am trying to write a routing method to read the database content, and using a Postman request, I can successfully obtain the data content. But logging in using Postman or app and using the correct account and password will result in an error:
PostgresNIO.PSQLError (backing: PostgresNIO.PSQLError. (unknown context at $10160e44c). Backing)
If the wrong account password is used, it will be reported that the identity has not been verified.

I am using Basic Auth provided by Vapor.
The premise is that everything was running normally.

[Muning69]

The cause of the problem

If there are multiple fields in the model, it is easier to understand when reporting an error in versions before Vapor 4.77.0, while in version 4.77.0, it will report PostgresNIO.PSQLError (backing: PostgresNIO.PSQLError. (unknown context at $10160e44c) The mistake of 'Backing' makes people confused.