Two examples of the Verify emails have been sent. Please note the link addresses of each.
Additional instructions sent to [email protected]
'Publish' copies all appsettings.json files to wwwroot.
If "CorsOrigins" is not identical for appsettings.Development.json and appsettings.Production.json and appsettings.json, the CORS error occurs.
It appears that appsettings.Development.json is still being referenced from somewhere.
Updated confirming email sent to info@aspnetzero Subject: [MyDomain] account email activation = RE: #10256
Yes. Address sent to [email protected]
Yes. Please notice the black lock icon visible in the first screenshot. Domain name sent to [email protected].
This issue has been resolved by using the injected UserManager. i.e.
var user = await _userManager.FindByEmailAsync(inputEmailAddress);
Starting with version 8.7.0 it appears. I'm at 8.1.0.
Removing "appsettings.Staging.json" and "appsettings.Development.json" from the server, and making "aspsettings.Production.json" the same as "aspsettings.json" fixed the issue.
Submitted ticket #10212 to suggest a long-term solution.
Added the "Allow CORS: Access-Control-Allow-Origin" browser extension to continue development. NOT A PERMANENT SOLUTION.
Logging in as 'admin' produced a lot of warnings. Log file sent via email.
Removed trailing / from "CorsOrigins", then from all string in .json files. Makes no difference. If you click on the links in the browser console message, both links return data from the server. If I have removed the wrong / please be more specific: file, line, column.
