Is it possible to implement session based autocomplete from the places sdk for Android and iOS apps?
According to new Google Maps framework pricing coming into effect June 11th request made to autocomplete can be broken down into keystroke/session based.
I haven't been able to find documentation describing implementation steps, except for this reference.
The session tokens will be available in the new versions of Google Places SDK for Android and Google Places SDK for iOS. These new versions are announced in the user guide documentation.
Google is currently preparing new versions of the Places SDK for Android, and the Places SDK for iOS. The following section describes the changes and explains how they will affect you.
A new Places SDK for Android will be made available as a standalone library, and will no longer be available through Google Play services; This version will not be backward-compatible with the current SDK
A new Places SDK for iOS will be made available
It's worth noting that several Places SDK features will be updated to reflect overall Places API changes, affecting both mobile platforms:
Place Details (Android, iOS) request will have a new fields parameter.
Autocomplete billing will be session-based.
In the coming months we will share more details including a timeline and appropriate lead time to migrate to the new SDK versions. These new versions will replace the current SDK versions. The current SDKs will be deprecated and will follow appropriate deprecation timelines.
source: https://cloud.google.com/maps-platform/user-guide/product-changes/
In the current version of Places SDK there are no session tokens. Unfortunately, there is no exact ETA for new versions of SDKs. Hopefully, they will be available in couple of months. Stay tuned to Google announcements.
Regarding billing of current versions of Places SDK for Android and Places SDK for iOS I'm not sure. Probably they will be free of charge as deprecated versions. I would suggest reach out to Google support with this question.
You can also check this question regarding sessions:
How long do the new Places API session tokens last?
I hope this clarifies your doubt.
Update
The new version of the Places Android SDK is now available. You can read about the new version at
https://developers.google.com/places/android-sdk/client-migration
Note that the previous SDK is deprecated and will be shut down on July 29, 2019.
The new version of SDK implements session tokens for autocomplete.
The new version of the Places SDK for Android is distributed as a static client library. Until now, the Places SDK for Android has been made available through Google Play Services.
A compatibility library is available, which enables you to switch from the deprecated Google Play Services Places library to the new static library with minimal effort.
There are all-new methods.
Field masks are now supported for methods that return place details. You can use field masks to specify which types of place data to return.
The exceptions used to report errors have been improved.
Autocomplete now supports session tokens.
Related
I'm using Google Places Autocomplete API in my Application. Recently I have changed my package name. Then i have created a new project in Google Developers Console and added the API Key to my project.
I have Enabled the Google Maps SDK for Android and Places API.
Now only detecting current location is works, Places AutoComplete Search returns "PLACES_API_ACCESS_NOT_CONFIGURED".
i think you have to Enable the Google Places API for Android in developers console and check on the credentials page that your key is still present. Hope this helps
Please, note that Places SDKs for Android and iOS has been updated as per this announcement.
The Places SDK for Android (in Google Play Services 16.0.0) and Places SDK for iOS v 2.7.0 are deprecated as of January 29, 2019.
The services Places SDK for Android/iOS are not available for new users as of January 29, 2019. Please follow the instructions in the Migration Guides for Android and iOS in developers' doc on how to migrate your implementation to the new versions of Places SDKs.
For using new versions of Places SDKs please ensure that Places API service is enabled on your Google Maps Platform project. Enabling Places API service makes all Places APIs available - Web Services, JavaScript and Places SDKs for Android and iOS.
Hope this helps!
Google places SDK will get deprecated
As Google announced "Deprecation notice: Google Play Services version of the Places SDK for Android" so will it affect on this API (https://maps.googleapis.com/maps/api/place/autocomplete/json) which I am using in my project with the help of google play services. for getting predictions regarding the autocomplete address.
Please note that URI https://maps.googleapis.com/maps/api/place/autocomplete/json doesn't form part of the Places SDK for Android. This URI belongs to the Google Places API web service.
Web service wasn't deprecated and will continue working as usual. If your application executes direct calls to web services there is nothing to worry about. You should only migrate old code that uses methods of Places SDK for Android to new SDK.
I hope this clarifies your doubt.
Yes it's deprecated and it will be turned off on July 29, 2019
Notice: The Google Play Services version of the Places SDK for Android (in Google Play Services 16.0.0) is deprecated as of January 29, 2019, and will be turned off on July 29, 2019. A new version of the Places SDK for Android is now available. We recommend updating to the new version as soon as possible. For details, see the migration guide.
see the documentation , also see the new way to implement it in the documentation .
Hi today google send me this email about all my application that use Google Place picker in ios and android.
*Today we're launching upgraded Places SDKs for Android and iOS. They are pay-as-you-go and billed at the same rate as our Places API and Places Library in the Maps JavaScript API. You can visit the Android and iOS migration guides to install the new SDKs.
Effective January 29, 2019, the upgraded Places SDKs for Android and iOS will replace the existing versions of the Places SDKs - please read our documentation for more information. The existing Places SDKs (including the Place Picker feature) can continue being used by current customers of these SDKs until July 29, 2019. In order to avoid service disruption, please start using the upgraded SDK versions before July 29, 2019.
We have identified that your projects listed below are using Places API and will be impacted by this change:
#
We have noticed that you do not have a billing account with a valid form of payment. Please update your billing account and associate it to your project(s) by July 29, 2019 to avoid service interruption.
We understand this announcement may have an impact on your implementations. If you have any questions, or require further assistance, please contact Google Maps Platform Support.*
Does this means that by by July 29, 2019 all my apps that use Place Picker will not function correctly because Google decided to remove it?
What am i suppose to do? Really confused again. Thanks Google!
My app heavily depended on the PlacePicker and It was free. Though there is a migration guide, but the new APIs are not free and have an upper cap on free usage. SO I built a Place picker that lets you pick places from a map using Geocoder and its free Check it out: https://github.com/suchoX/PlacePicker
As far as I can tell, the placepicker UI that they provided will no longer be available. You will have to find a replacement for the UI or come up with something on your own. You can still use the SDK to get autocompletion in order to simulate what the placepicker was doing. Everything that made the placepicker UI work is still there, they are just deprecating and no longer supporting the UI.
It says what you are supposed to do in the email google sent you. From yesterday, you have up to July 29, 2019 to implement and start using the updated SDK versions just for the Places API in place of the old. Once you have done this release it. Make sure you do this for all your apps that are effected by this update. If you don't do this, your apps can possibly still function but that feature will not.
EDIT:
On this page you can see the Deprecation notice
When you click the Android Migration we can see that you can install the compatibility library to continue using the Place Picker during the deprecation period. After this the place picker will no longer work.
Looks like you have to find another way to do what the place picker is currently doing for you.
Place Picker old version will be turned off from jul 29 2019 but migration option available
Migration Guide here
I was reading this tutorial http://www.androidhive.info/2015/02/android-location-api-using-google-play-services/ and I find it amazing that this one and many others never state what versions they support.
There must be a simple list which contains what libraries are for what api versions, not just Google Play library but for everything else, from reading file paths to camera api. An example would be just the camera api 2, which is for api version 21 and above. A nice list listing all of this would be very helpful!
It's extremely time consuming tracking down all of this information.
I would say that there is one - in packages documentation you can easily filter by API number.
Official Android APIs have their API number define on official Android documentation like #sebap123 said.
Google Play Services isn't part of Android itself. It's a complimentary add-on. Google Play Services runs on Android 2.3 or higher. All new GPS APIs included in GPS will run on all these devices that have GPS(Android 2.3 or higher). Unlike new Android APIs that only run on new version of Android.
Is the Google Play Services SDK R15 available to download anywhere? The "ChromeCast SDK" was "released" Monday, according to hundreds of news sites. Those same news sites claim Android app developers are "hard at work implementing ChromeCast functionality." Is the SDK appearing in anyone's SDK Manager?
How are Android app developers implementing ChromeCast functionality when the SDK isn't available and the API has changed dramatically? The DayFrame developers supposedly already updated their app to the new API, which seems suspicious to me...
Edit - As per the announcement post, SDK15 is now available.
As per the Chromecast Android API reference:
These APIs are currently not available for development. They require Google Play services 4.2, which began rolling out to devices worldwide on February 3rd. Once the update to devices is complete, the corresponding Google Play services library (revision 15) will be available for you to begin using these APIs.
Certain developers have been given early access to the SDK directly from Google to allow early development, but general availability of SDK R15 is still to come. You can still read through the Developers Guide and the Android Sender App Development Guide and prepare your application, design, and resources appropriately, but the actually integration of the SDK and testing cannot occur until Google releases it officially after the full rollout of Google Play Services 4.2.