visgl / visgl/react-google-maps
New Routes api key does not work with Directions api
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 193
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 13
Description
Description
The problem is that I created a new Google Maps account and a new API key, but there is no Directions API. They say you should use the Routes API. However, when I use the new API key with the Routes API enabled, I get
MapsRequestError: DIRECTIONS_ROUTE: REQUEST_DENIED: There was an issue performing a Directions request.
Uncaught (in promise) MapsRequestError: DIRECTIONS_ROUTE: REQUEST_DENIED: The webpage is not allowed to use the directions service.
When I use an old API key from 5 years ago with the Directions API enabled, it works fine.
Steps to Reproduce
Create new google account and Reoutes api.
Environment
- Library version:
- Google maps version: weekly
- Browser and Version:
- OS:
Logs
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is identified. First reproduce the request with a newly created key, checking the enabled Google Maps APIs and webpage restrictions against the working older key. Done means determining whether the library mishandles the Routes API or documenting that the failure is caused by Google Maps account or key configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100