fluttercommunity / fluttercommunity/flutter_google_places

Lost over $300 in GCP billing becoz this package pulls all fields in result, my bad I was unaware

Open
#119 8 comments 7 reactions 0 assignees View on GitHub
Dominant language
Dart
Stars
312
Forks
462
PR merge metrics
No merged PRs in 30d

Description

While this package is good and is working with no issues for me, I recently had a GCP billing issue where it charged me over $300-$400 without me querying for Contact or Atmosphere data. I was only accessing the Basic fields all the time like Name, Address, and Photos through getDetailsByPlaceId() method but I am unaware that this method pulls all fields and GCP Billing works such a way that its billing is based on the response (PlacesDetailsResponse) object fields rather than the fields that I fetch from PlacesDetailsResponse object.

After several emails and phone calls with GCP support, I came to know that the issues lie with this package and I had already lost over $300 to $400 over 2 months. Any new users please be aware that this API does not have a way to set Fields like Basic fields, Contact fields, Atmosphere fields separately but it returns all fields which you requesting for it.

Having said that, I like this package otherwise and I hope this package includes a way to set fields. For now, I am moving away from this package due to this missing field restrictions feature. I am now considering flutter_places_autocomplete package which has the feature that I am looking for, please suggest me any other package available which is good and also has a field restriction feature.

Also, correct me if there is already a way available in flutter_google_places to restrict the response to certain fields falling under Basic, Contact, or Atmosphere pricing plan.

PlacesDetailsResponse detail = await _places.getDetailsByPlaceId(p.placeId);

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.