-
Notifications
You must be signed in to change notification settings - Fork 4k
MissingMethodException: Method not found: '!!0 AutoMapper.IMapper.Map(System.Object)'. #4779
Comments
You on the latest version? #4677 |
I Using Blazor Webassembly Individual user account with default Authentication, unless not the latest version by default. |
Yea, the Microsoft templates are behind. You should not update AutoMapper if you're using their older templates. |
but when I changed the default identity server to the last version (to identity server4 4.0.4) and give me new error : |
System.MissingMethodException: Method not found: '!!0 AutoMapper.IMapper.Map(System.Object). This also occurs for me when creating an AspNetCore 3.1 web application using the Angular template with Individual Accounts for Authentication. |
Also occurs for React JS template using the Individual Accounts in AspNetCore 3.1 as well, reverting the AutoMapper to v9 and AutoMapper.Extensions.Microsoft.DependencyInjection to v7 fixes this. |
This happens to me in Visual Studio Community Edition but Enterprise Edition it works fine. |
I also came across this issue. |
Also have this issue on Blazor webassembly |
The current Microsoft templates are not compatible with the v4.x version of IdentityServer. You will have to wait for Microsoft to update them. |
I'm facing the same issue with |
Same. I'm having the same issue in a |
You can disregard my message above. I realized that I was referencing to |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
We can only help you if you are on the latest version. Either use the latest 3.x or 4.x
I using last version of IdentityServer 4
Issue / Steps to reproduce the problem
Automapper v10
andAutoMapper.Extensions.Microsoft.DependencyIn v8.0.1
note: I using Blazor Webassembly Individual user account with default Authentication
when I run project, in-browser give me 500 error :
AuthenticationService.js:44 GET https://localhost:5001/connect/authorize?client_id=Web.Client&redirect_uri=https%3A%2F%2Flocalhost%3A5001%2Fauthentication%2Flogin-callback&response_type=code&scope=Web.ServerAPI%20openid%20profile&state=4b9b0120a48442a786b5bc8260c52f65&code_challenge=ViBkoIwumlfy_kg_y0bAh9uFsEByt2aKDOVUSREfARE&code_challenge_method=S256&prompt=none&response_mode=query 500
and in self-host console:
and in
https://localhost:5001/connect/authorize?client_id=Web.Client&redirect_uri=https%3A%2F%2Flocalhost%3A5001%2Fauthentication%2Flogin-callback&response_type=code&scope=Web.ServerAPI%20openid%20profile&state=4b9b0120a48442a786b5bc8260c52f65&code_challenge=ViBkoIwumlfy_kg_y0bAh9uFsEByt2aKDOVUSREfARE&code_challenge_method=S256&prompt=none&response_mode=query
file:Stack:
Show raw exception details
The text was updated successfully, but these errors were encountered: