You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Roads: Nearby Roads does not give error when trying to issue request without billing setup #246
create a project ( the billing is enabled by default )
create an API key in by click Create credentials > API key.
disable the billing for this project.
the error message will be shown as follow?
{
"error": {
"code": 404,
"message": "Requested entity was not found.",
"status": "NOT_FOUND"
}
}
my raw query ( please replace YOU_KEY field )
curl --request GET \
--url 'https://roads.googleapis.com/v1/nearestRoads?points=60.170880%2C24.942795%7C60.170879%2C24.942796%7C60.170877%2C24.942796&key=YOU_KEY'
my guess
I think it did throw an error, you can find err = json.NewDecoder(httpResp.Body).Decode(resp) will return an error as the response with error cannot mapped to resp which is a reference from response := &NearestRoadsResponse{}
Thanks for the response. I agree that the underlying raw API call throws the error. I think the issue is that unlike the geocoding go call, the error does not get propagated up to the developer. There may very well be an internal error but to the developer using the gmaps golang library, it looks like a silent failure.
As for reproduction, billing was not enabled by default but I imagine having a project with billing explicitly disabled will reproduce the issue.
Activity
AlphaWong commentedon Oct 9, 2020
hi
May I confirm with you about the step to setup?
click Create credentials > API key.the error message will be shown as follow?
{ "error": { "code": 404, "message": "Requested entity was not found.", "status": "NOT_FOUND" } }my raw query ( please replace YOU_KEY field )
my guess
I think it did throw an error, you can find
err = json.NewDecoder(httpResp.Body).Decode(resp)will return an error as the response with error cannot mapped torespwhich is a reference fromresponse := &NearestRoadsResponse{}twa16 commentedon Oct 10, 2020
Thanks for the response. I agree that the underlying raw API call throws the error. I think the issue is that unlike the geocoding go call, the error does not get propagated up to the developer. There may very well be an internal error but to the developer using the gmaps golang library, it looks like a silent failure.
As for reproduction, billing was not enabled by default but I imagine having a project with billing explicitly disabled will reproduce the issue.