The generated certificate from dotnet dev-certs https isn't valid on iOS

When you use dotnet dev-certs https --trust on Mac OSX, it creates a new certificate and adds it to the store as expected. However, when you are using the iOS simulator to test that website, or even use Azure B2C authorisation, you can't use the generated certificate on the device.

The reason for this is the certificate generated isn't a self-signed cert with Basic Constraint x509 extension with enabled CA option. The dotnet certs tool should provide the option to create this type of certificate. Without it, you can't trust the certificate on iOS and you can't do any HTTPS calls from your iOS simulator to your localhost webserver.