Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compat - PlacePicker closes immediately after launch #2

Closed
CyanDeveloper opened this issue Feb 5, 2019 · 20 comments
Closed

Compat - PlacePicker closes immediately after launch #2

CyanDeveloper opened this issue Feb 5, 2019 · 20 comments

Comments

@CyanDeveloper
Copy link

By installing the demo app ther is an issue on PlacePicker.
CurrentPlace and AutoComplete features works correctly but PP is shown and closed immediately without errors or warnings.
It can't be a API Key issue because 2/3 features works perfectly showing data.

@CyanDeveloper CyanDeveloper changed the title PlacePicker closes immediately after launch Compat - PlacePicker closes immediately after launch Feb 5, 2019
@ghost
Copy link

ghost commented Feb 17, 2019

Same issue here

@amuramoto
Copy link
Contributor

@CyanDeveloper @cr05s19xx Can you provide error logs? I just tested this on API 25, 26, 27, and 28 with no issue

@CyanDeveloper
Copy link
Author

@CyanDeveloper @cr05s19xx Can you provide error logs? I just tested this on API 25, 26, 27, and 28 with no issue

No error.. it closes immediatly like "permission denied" issue.. but if I change it with Compat AutoComplete all works well. So, it isn't permissions problem.

@amuramoto
Copy link
Contributor

What API version are you using?

@CyanDeveloper
Copy link
Author

CyanDeveloper commented Feb 19, 2019

What API version are you using?

I run it on Samsung S7 with Android 8.0.0
The project was cloned and not modified.
Other projects that used same technology (PlacePicker), now do same thing and no work more.

@amuramoto
Copy link
Contributor

There's no crash log in Logcat when this happens? Can you try testing on a more recent API version as well? Would like to see if this is specific to the API version + device or not. I've run this with Android 8.0.0 on a Pixel 2 and it ran without issue.

@CyanDeveloper
Copy link
Author

There's no crash log in Logcat when this happens? Can you try testing on a more recent API version as well? Would like to see if this is specific to the API version + device or not. I've run this with Android 8.0.0 on a Pixel 2 and it ran without issue.

@amuramoto ... No log, no crash.. simply closes PP activity returning to MainActivity that show the options to pick a place (PlacePicker, AutoComplete and PlacePhotos)..

Is the same behavior as an api error, but without errors.. it close activity immediatly.

Anyway, I'll try run it on an emulated device and another physical device, letting you know if works or not.

@amuramoto
Copy link
Contributor

Ok thanks - I'm not able to reproduce the error, so it is difficult to help debug at this point

@ghost
Copy link

ghost commented Feb 19, 2019

There is an error being thrown, but my biggest suspect is this error:

https://stackoverflow.com/questions/30067210/android-place-picker-closes-immediately-after-launch...

I'm not sure why this is happening, especially since the other components work perfectly

@amuramoto
Copy link
Contributor

@cr05s19xx Can you share the error being thrown?

I don't think the SO issue you pointed to is the root cause (at least not in all cases) since I am able to run the sample without the described behavior.

@strangelove11
Copy link

Same issue

@gavingt
Copy link

gavingt commented Feb 27, 2019

With the new SDK, the PlacePicker will only work for API keys that were activated prior to the PlacePicker's deprecation date (January 29, 2019). Or, at least, that's how I interpret the email Google sent me when they announced the new SDK:

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.

So the PlacePicker might not be working for some people while other features do, simply because your API key isn't flagged to use the PlacePicker through the deprecation period.

@CyanDeveloper
Copy link
Author

With the new SDK, the PlacePicker will only work for API keys that were activated prior to the PlacePicker's deprecation date (January 29, 2019). Or, at least, that's how I interpret the email Google sent me when they announced the new SDK:

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.

So the PlacePicker might not be working for some people while other features do, simply because your API key isn't flagged to use the PlacePicker through the deprecation period.

This is not true. You have misinterpreted the text of the email. He simply says that in July 2019 the PlacePicker will be removed from their libraries as they have updated them. But currently it is still possible to use it (until July) using the new "compat" library.
Also, I downloaded and tested the app the first days of February, so what you said does not make sense.

@amuramoto
Copy link
Contributor

Checking back in on this... Can anyone provide an error log? Also, check that you are calling StartActivityForResult rather than StartActivity

@amuramoto
Copy link
Contributor

Closing since we can't replicate and haven't received any error logs

@ghost
Copy link

ghost commented Apr 7, 2019

The problem still exist

@venkateshtata
Copy link

With the new SDK, the PlacePicker will only work for API keys that were activated prior to the PlacePicker's deprecation date (January 29, 2019). Or, at least, that's how I interpret the email Google sent me when they announced the new SDK:

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.

So the PlacePicker might not be working for some people while other features do, simply because your API key isn't flagged to use the PlacePicker through the deprecation period.

@gavingt You're right ! it worked for me when i tried with my previous API Key of my old Google Developer account. Hope there's a market place for old Google API Keys : )

@alexismo
Copy link

I'm trying to complete the Udacity Advanced Android App Development course and running into the same issue.
https://developers.google.com/places/android-sdk/client-migration#place-picker-deprecation says that

The Place Picker was deprecated on January 29, 2019. It was turned off on July 29, 2019, and is no longer available. Continued use will result in an error message. The new SDK does not support the Place Picker.

Cross-posting to https://stackoverflow.com/questions/30067210/android-place-picker-closes-immediately-after-launch

@zawawimanja
Copy link

any solution ?? already follow stackover that need to enable places api in cloud console.

@gavingt
Copy link

gavingt commented Mar 7, 2020

any solution ?? already follow stackover that need to enable places api in cloud console.

You can't use PlacePicker any more. It's been turned off. It's gone forever.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants