aws-vault: Appears to fail if no existing .aws/config file?

I’ve rolled out aws-vault to all our team and after upgrading to 4.1.0 one of them got the following error: Error adding profile: &errors.errorString{s:"No iniFile to add to"}

Which presumably comes from the fact he has neither .aws/config or .aws/credentials. I got him to manually create there files (just empty text files) and that got past the problem. It seems like aws-vault doesn’t handle these files not being there? But if we are to use aws-vault exclusively instead of aws configure then they probably won’t be there.

Also, it is possible this is only a problem due to upgrading. And a fresh install wouldn’t have a problem.