Currently, it appears as though when an incorrect clientId and/or privateKey are given when using GoogleMapsBusinessProvider, that a NoResultException is thrown rather than the more informative and accurate InvalidCredentialsException. This is rather problematic because a NoResultException is also thrown when the correct credentials are given, but when a query is sent to Google that does not return a result.
From what I can tell, the following providers currently throw the InvalidCredentialsException:
- BaiduProvider
- BingMapsProvider
- ChainProvider
- CloudMadeProvider
- GeoIPsProvider
- GeonamesProvider
- IGNOpenLSProvider
- IpInfoDbProvider
- MapQuestProvider
- MaxMindProvider
- TomTomProvider
Does anyone know why this isn't implemented for GoogleMapsBusinessProvider? If it is an easy fix I can make a PR early this week.