Mobile 3G/4G data networks are reusing those IPs, so at best you'll get a country or state-level accuracy.
The IP of home / business connections can be static and the accuracy can be good, however you're not taking that IP with you when on the move. So in order to track a user's movement, online services have to link that IP to some unique identifier of that user.
It's not insurmountable of course and native apps have no problem in generating such unique identifiers per user, however without consent it's now illegal to use a user's IP for tracking his location under GDPR and it's also illegal to generate unique identifiers for users without consent. Even logging IPs is now illegal, unless you're doing it for security purposes and only for a limited amount of time.
Also the Terms of Use documents aren't sufficient, there are already many lawsuits active and we'll soon hear of the fallout.
If you're lucky. Right now I'm on a Verizon connection that reports me being in New Mexico.
My phone's AT&T connection currently says I'm in Los Angeles.
I'm half a continent away from either of those places.
Of course, since ip "geolocation" is just ip data + location agregatted from ISPs. How can the OS maker "fight" this ?
It's also very frustrating if you are using the Wi-Fi APIs for legitimate purposes. Having to explain to a user why you need location permissions in order to set up a Wi-Fi peripheral isn't easy.
It's just worth noting that flipping a switch in your OS might not do much in terms of location tracking.