react-native-google-places
react-native-google-places copied to clipboard
tolu360
PLACE FIELDS for getAutocompletePredictions
There is an option to specify PLACE FIELDS for "openAutocompleteModal" method but absent for "getAutocompletePredictions" method. This results in having to initiate the "lookUpPlaceByID" method as well after getAutocompletePredictions resulting in two different requests from google perspective as session keys are not shared between the requests.
Is there any ways to add PLACE FIELDS "getAutocompletePredictions" method as well? currently the two requests are generating a huge bill from google for us and unsure what can be done from our end.
getAutocompletePredictions does not support place fields as you have rightly noted but I have come across session tokens on iOS, not sure but it seems Google manages sessions for you automatically on Android. Would research a cross-platform way, if any, to add session tokens. Keep this issue open in the meantime. Cheers!
On Wed, Aug 14, 2019, 2:00 PM manithin [email protected] wrote:
There is an option to specify PLACE FIELDS for "openAutocompleteModal" method but absent for "getAutocompletePredictions" method. This results in having to initiate the "lookUpPlaceByID" method as well after getAutocompletePredictions resulting in two different requests from google perspective as session keys are not shared between the requests.
Is there any ways to add PLACE FIELDS "getAutocompletePredictions" method as well? currently the two requests are generating a huge bill from google for us and unsure what can be done from our end.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/tolu360/react-native-google-places/issues/253?email_source=notifications&email_token=AA53YZQND5GZYWFA75XOJRLQEP6XNA5CNFSM4ILUT2N2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HFGL7ZA, or mute the thread https://github.com/notifications/unsubscribe-auth/AA53YZSXOMBXSGOZBORBIZLQEP6XNANCNFSM4ILUT2NQ .
We also contacted google support as well. They informed that we are using session token but each time a different one. I guess the session taken is not shared between the two methods. Also I wanted to know if any styling customizations can be done on "openAutocompleteModal'.
Thanks for the quick response earlier!
As seen on Places API Usage and Billing - Autocomplete (included with Places Details) – Per Session, supporting sessions is a critical item as it essentially kills the cost of running the leading autocomplete query http calls. I'd love to see this feature implemented.
