Ufdjrw

I'm flying to France today and my passport expires in less than 2 months

Today is the Center

Could gravitational lensing be used to protect a spaceship from a laser?

How to draw the figure with four pentagons?

What is the most common color to indicate the input-field is disabled?

Anagram holiday

Why is it a bad idea to hire a hitman to eliminate most corrupt politicians?

Facing a paradox: Earnshaw's theorem in one dimension

Can I ask the recruiters in my resume to put the reason why I am rejected?

Did Shadowfax go to Valinor?

Is it possible to run Internet Explorer on OS X El Capitan?

AES: Why is it a good practice to use only the first 16bytes of a hash for encryption?

Took a trip to a parallel universe, need help deciphering

Why doesn't H₄O²⁺ exist?

Why can't we play rap on piano?

What is the intuition behind short exact sequences of groups; in particular, what is the intuition behind group extensions?

Why "Having chlorophyll without photosynthesis is actually very dangerous" and "like living with a bomb"?

How can I tell someone that I want to be his or her friend?

Should I tell management that I intend to leave due to bad software development practices?

Is it unprofessional to ask if a job posting on GlassDoor is real?

Is it possible to create light that imparts a greater proportion of its energy as momentum rather than heat?

Is it canonical bit space?

Is there a hemisphere-neutral way of specifying a season?

Intersection of two sorted vectors in C++

Concerning the current Google Places SDK tutorials should a newbie just skip all the steps and start with the Migration tutorial?

Android Places API: Google Play Services Out of Date on EmulatorGoogle place Autocomplete is not working?Failed to resolve module 'react-native-google-place-picker'Google's new Places Library ( implementation 'com.google.android.libraries.places:1.0.0') not resolvingHow do I run google's new “places_compat_compatify.sh” compatibility script?error while adding google places sdk for Android[Cause: duplicate entry: com/bumptech/glide/GeneratedAppGlideModule.class]PlaceAutocompleteAdapter with Places SDK compat LibraryApiException: 9003: PLACES_API_ACCESS_NOT_CONFIGURED

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;

0

I am trying to add some of the very cool functionality of Google Places to my application, so I decided to read and follow the tutorial starting from this link:

https://developers.google.com/places/android-sdk/intro.



Right away I noticed that alot of what is in this tutorial is currently depreciated.

• Deprecation notice: Google Play Services version of the Places SDK
  for Android
  


• Deprecation notice: Place Picker
  
  

I found these depreciation notices on every page of the tutorial, so I skipped down the the "Migrating to the new Place SDK Client" tutorial. In this tutorial there are instructions not to use the

com.google.android.gms:play-services-places:16.0.0

library. But later on I read the following:

Install the compatibility library

The compatibility library is a thin
library that mirrors the API surface of the current Google Play
Services Places client, and wraps the new Places SDK client. There is
no need to alter the basic functionality of your app, as it will
function identically to the previous version with only a few minor
changes. The compatibility library is a temporary measure to assist
with your migration to the new Places SDK client.

I am confused as how to proceed now. The rest of the Migration tutorial seems to be about the new features that cost money, and not a tutorial on a newer version of the previous SDK. Should I just use the depriciated libraries (which will undoubtably cause errors) and then use the migration info to debug? Any Thoughts on how to proceed?

google-places-api

share|improve this question

edited Mar 8 at 5:42

codenamejupiterx

asked Mar 8 at 0:01

codenamejupiterxcodenamejupiterx

12

add a comment | 

0

I am trying to add some of the very cool functionality of Google Places to my application, so I decided to read and follow the tutorial starting from this link:

https://developers.google.com/places/android-sdk/intro.



Right away I noticed that alot of what is in this tutorial is currently depreciated.

• Deprecation notice: Google Play Services version of the Places SDK
  for Android
  


• Deprecation notice: Place Picker
  
  

I found these depreciation notices on every page of the tutorial, so I skipped down the the "Migrating to the new Place SDK Client" tutorial. In this tutorial there are instructions not to use the

com.google.android.gms:play-services-places:16.0.0

library. But later on I read the following:

Install the compatibility library

The compatibility library is a thin
library that mirrors the API surface of the current Google Play
Services Places client, and wraps the new Places SDK client. There is
no need to alter the basic functionality of your app, as it will
function identically to the previous version with only a few minor
changes. The compatibility library is a temporary measure to assist
with your migration to the new Places SDK client.

I am confused as how to proceed now. The rest of the Migration tutorial seems to be about the new features that cost money, and not a tutorial on a newer version of the previous SDK. Should I just use the depriciated libraries (which will undoubtably cause errors) and then use the migration info to debug? Any Thoughts on how to proceed?

google-places-api

share|improve this question

edited Mar 8 at 5:42

codenamejupiterx

asked Mar 8 at 0:01

codenamejupiterxcodenamejupiterx

12

add a comment | 

I am trying to add some of the very cool functionality of Google Places to my application, so I decided to read and follow the tutorial starting from this link:

https://developers.google.com/places/android-sdk/intro.



Right away I noticed that alot of what is in this tutorial is currently depreciated.

• Deprecation notice: Google Play Services version of the Places SDK
  for Android
  


• Deprecation notice: Place Picker
  
  

I found these depreciation notices on every page of the tutorial, so I skipped down the the "Migrating to the new Place SDK Client" tutorial. In this tutorial there are instructions not to use the

com.google.android.gms:play-services-places:16.0.0

library. But later on I read the following:

Install the compatibility library

The compatibility library is a thin
library that mirrors the API surface of the current Google Play
Services Places client, and wraps the new Places SDK client. There is
no need to alter the basic functionality of your app, as it will
function identically to the previous version with only a few minor
changes. The compatibility library is a temporary measure to assist
with your migration to the new Places SDK client.

I am confused as how to proceed now. The rest of the Migration tutorial seems to be about the new features that cost money, and not a tutorial on a newer version of the previous SDK. Should I just use the depriciated libraries (which will undoubtably cause errors) and then use the migration info to debug? Any Thoughts on how to proceed?

google-places-api

share|improve this question

edited Mar 8 at 5:42

codenamejupiterx

asked Mar 8 at 0:01

codenamejupiterxcodenamejupiterx

12

share|improve this question

edited Mar 8 at 5:42

codenamejupiterx

asked Mar 8 at 0:01

codenamejupiterxcodenamejupiterx

12

share|improve this question

edited Mar 8 at 5:42

codenamejupiterx

asked Mar 8 at 0:01

codenamejupiterxcodenamejupiterx

12

asked Mar 8 at 0:01

codenamejupiterxcodenamejupiterx

12

asked Mar 8 at 0:01

codenamejupiterxcodenamejupiterx

12