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
Thank you for the excellent library @tolu360! I'm wondering if this is a possible issue, or if I am doing something incorrectly. Please note that I did have to patch to Places and Maps 3.5.0 before installing for compatibility with react-native-maps.
priceLevel is considered Atmospheric Data by Google, which is billed as a separate SKU, and is very expensive to query. I am seeing priceLevel returned on iOS even if it is not part of the selected fields.
I could be mistaken here. Is (-1) a default value always returned for priceLevel on iOS if it is not part of the original query?
chrislarson
changed the title
[IOS] priceLevel is returned even if not selected in placeFields - billing concern
[IOS] priceLevel is returned even if not selected in placeFields - possible billing concern
Jun 15, 2020
Without checking the docs for confirmation, I would go out on a limb to say that may be the default on iOS when it is not included in the selected fields - however, let me confirm and get back to this later.
Thank you for the excellent library @tolu360! I'm wondering if this is a possible issue, or if I am doing something incorrectly. Please note that I did have to patch to Places and Maps 3.5.0 before installing for compatibility with react-native-maps.
priceLevel is considered Atmospheric Data by Google, which is billed as a separate SKU, and is very expensive to query. I am seeing priceLevel returned on iOS even if it is not part of the selected fields.
Sample code:
Sample response (iOS):
The text was updated successfully, but these errors were encountered: