iOS - Internal Error occurs in Google Places library when retrieving Place for PlaceID [119844521]

Assigned

Bug

Status Update

No update yet.

Description

[Deleted User]

created issue #1

Nov 21, 2018 04:32PM

# WARNING: DO NOT INCLUDE YOUR API KEY OR CLIENT ID CREDENTIALS
# It is OK to share your API Project ID, but _not_ API keys.

Issue report
----------------

Attempting to retrieve a Place for a PlaceID in the Google Places SDK on iOS sometimes results in an internal error.

PlaceID in question ChIJ65YdxZmjhVQRYyYums3lTsw

cURL'ing for this PlaceID returns `NOT_FOUND`. Full error message here

```
Error Domain=com.google.places.ErrorDomain Code=-3 "An internal error occurred in the Places API library. If you believe this error represents a bug, please file a report using the instructions on our community and support page (

https://developers.google.com/places/ios-api/support)." UserInfo={NSLocalizedFailureReason=An internal error occurred in the Places API library. If you believe this error represents a bug, please file a report using the instructions on our community and support page (

https://developers.google.com/places/ios-api/support)., NSUnderlyingError=0x604000138c90 {Error Domain=com.google.places.server.ErrorDomain Code=-2 "No result in response" UserInfo={NSLocalizedFailureReason=No result in response}}} #0
```

Comments

mi...@google.com <mi...@google.com> #2Nov 23, 2018 09:31AM

Hello,

Thank you for reaching out to us.

This report does not contain any description. The Public Issue Tracker is meant for reporting commonly observed issues with detailed description and reproducible steps, and requesting new features on GCP products. If it was created by mistake with no description, please open a new issue on the Issue Tracker with the description of your issue and the steps to reproduce it. I'm going to close this issue, which will no longer be monitored.

di...@google.com <di...@google.com> Dec 3, 2018 03:12PM

Assigned to ma...@google.com.

Issue 119844521

Description

Issue summary

Comments

mi...@google.com <mi...@google.com> #2Nov 23, 2018 09:31AM

di...@google.com <di...@google.com> Dec 3, 2018 03:12PM

Add comment

Issue metadata