I have an app which uses (or used...) Place Picker. As you may know it is deprecated since January 29th, 2019. I deleted my old "Places SDK for Android" API in Google Cloud plarform some time ago. Today I wanted to create new one but now I see that it is no more available there, only "Places API" is available.
On migration tutorial you can see this information:
IMPORTANT: The Place Picker is deprecated as of January 29, 2019. This feature will be turned off on July 29, 2019, and will no longer be available after that date. To continue using the Place Picker through the deprecation period, do NOT disable the Places SDK for Android service in your Google Cloud Platform project, as doing so will also disable the Place Picker.
Does it mean that if I disabled my Places SDK for Android which was created before 29.01.2019 I can no longer use Place Picker through the deprecation period with compatibility libraries? Even if I will enable "Places API" instead of "Places SDK for Android"?
If yes, can you recommend any service/library similar to place picker?
With regards to your concern, Yes, you will not be able to use the Place Picker once you disable the Places SDK for Android and you will be forced to migrate to the new SDK since the Places SDK for Android will be removed in your library once disabled. Currently, Google Maps doesn't have a library that offers the same functionality as the Place Picker, however, you may fill up the form in issue tracker for Google to understand what drives your interest in having a Place Picker widget.
Related
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
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.
it's been days since I started reading pages and pages on the internet in order to clean my mind on the question up here (for an assignment).
I have to write a school assignment about the differences between the location APIs on the Android platform and those ones introduced with the Google Play Services. So far so good, in a certain way.
My doubt regards what my teacher said (and well, it's the title of the assigment): "Analysis of Android 5 location APIs and comparison with older versions of the platform".
Android 5 came out during November 2014.
What I was thinking to write about was the introduction of FusedLocationProviderAPI and all its features but I can't find anywhere when these location APIs were added to Google Play Services. It seems they've been put out before the rollout of Android 5.
My question is, am I on the right way? In other case, what kind of new location based feature has been introduced with Android 5?
thanks
I have an Android geolocation application released into the market named apna ilaka.
It is using Android API level 2.1. In order to allow a user to add places I would like to display a Google map with which the user could find different locations and would be able to add place indicators and information.
Following are my questions :
Do I really need to change my Android API level to Google API level in config path?
Since my app is already in market if I upload this new apk on market will it create any issue in updating the software on user side?
You only need to update the API level of you app if you want to use any api that are higher than the currently set level.
Supporting multiple API levels can be tricky but it isn't a nightmare, check out this great post by google on this subject:
http://android-developers.blogspot.com/2010/07/how-to-have-your-cupcake-and-eat-it-too.html
I guess you are talking about "Google API" versus "Android API"? If you need Google Maps you will need to use "Google API" as it contains the Maps libraries. Otherwise you could not use Maps classes when developing/compiling.
No, as far as I know you should not have any problems.