To try to say the hardware for FSD is now present in 1M vehicles (which I doubt) is disingenuous to the insinuation Elon made that FSD is right around the corner. They're not meaningfully closer to FSD today than they were three years ago. Somewhat closer? Sure. A few feet on a journey that's a few miles though.
Actually driving a Tesla for 15,000 miles, of which perhaps 5,000 of those miles have been AP over the last 18 months, I can state this is totally false.
There has been extremely significant incremental progress with AP which is totally evident in everyday usage.
Turns through intersections is another area where Tesla's current implementation needs a lot of help (read: can barely do it at all) but should be within range soon given where they are at. And lane splits in city streets is definitely something the Tesla implementation is going to need to get better at before really making it door-to-door.
It's a very exciting, even historic time for self driving.
But yeah, taxi fleets are a ways out. There's a turn in the road just a 1/2 mile from my house where my Model 3 gives up every time.
I can imagine navigation services not working, but I've not been in places outside of the high Arctic (~82'N) where GPS itself wasn't very reliable.
And inaccuracy at start-up is also surprisingly challenging; think a person requesting a car within 5 seconds of opening the app, before the location service of the device has really resolved the location, thus ending up with a pick-up pin that is a hundred feet wrong or more. And maybe on the wrong side of a street, fence, etc.
We think of GPS as just the positioning part, but its just as important to remember that there is a large amount of work to translate that position into a meaningful data point within each given country. Just knowing someones exact GPS coordinates isn't helpful.
That is not what Elon predicted at Autonomy Day last April. He thought they would be feature-complete by the end of 2019, which is to say, that all the basic code paths necessary for best case city driving would be functional.
If you've done software development, you understand that getting to "feature-complete" is different from "code-complete", which is also different from "Beta", which is different from "GA". Those are each progressively later stages in the software development / release cycle.
Feature complete is merely the day that you can say that there is some functional code in place for all of the code paths that you expect to write. You would expect to be able to do an internal demo showing all the functionality working in the "happy case" at that point. Usually QA has not really even begun in earnest at this point. It is by no means the point where development is "done", which is for FSD in fact, approximately, never.
Code complete isn't always distinguished from feature complete, but in my experience, code complete would contemplate negative testing, error handling, and alternative processing modes which might not have been implemented at the point of "feature complete". Code complete typically signifies that from that point forward only bug fixes will be added into the next release.
Some projects can reasonable be expected to remain in testing, validation, and certification for several years after the point of "code complete".