So, this isn't exactly a bug, but it's still aberrant behavior. The importer is currently extremely strict regarding the import file types it is willing to work with. Notably, it rejects anything that isn't a PURE CSV file, including Excel-exported csv's, plaintext csvs, and more. Believe it or not ( I know, it's stupid ) -- almost every word processing application encodes csv files differently...for some reason.
To make contact imports more useful for ALL, we need to accept a wider array of file types. This gets tricky -- because we still need to be able to parse the thing, and for that we need it to be amenable to csv-ish commands.
This is the first in a range of issues around imports, including better progress transparency, error messages, and more.
Here are the test cases we need to support:
Bonus points: write Meta tests that support these requirements.