IssueTracker

-What is the incorrect behavior that you are experiencing?

The latitude and longtitue that I was using to pull up images in GooglePlaces on iOS Xcode 8.3.3 with a radius of 100 was accurate and the panoView always showed the same coordinates and image when it moved near the coordinates. Now that I have upgraded to Xcode 9 and downloaded the newest GooglePlaces and GoogleMaps cocoa pods, when I use the same exact lat and lon with the same radius of 100, the panoView moves near entirely different coordinates and shows an entirely image at an entirely different address.

It seems on the old pods with Xcode 8.3.3 if I used:

panoView.moveNearCoordinate(CLLocationCoordinate2D(latitude:  40.8760214, longitude: -73.9126076), radius: 100)

I would get the panoView result of:

panoramaID: Optional("NDAWLmlGAIMVQwfbj2KRlA") coordinates: (40.875936,-73.912461)

Now that I'm using Xcode 9 with the updated GooglePlaces and GoogleMaps pods the panoView displays some place else with different coordinates:

updated pods:

panoView.moveNearCoordinate(CLLocationCoordinate2D(latitude: 40.8760214, longitude: -73.9126076), radius: 100)

I would get the panoView result of:

panoramaID: NDAWLmlGAIMVQwfbj2KRlA coordinates: (40.8759361954681,-73.912460975194) //this is 100% INCORRECT

The only way I can get the same coordinates using the updated pods is for me to change the radius to 25:

panoView.moveNearCoordinate(CLLocationCoordinate2D(latitude: buildingLat!, longitude: buildingLon!), radius: 25)

I get the panoView result of:

panoramaID: NDAWLmlGAIMVQwfbj2KRlA coordinates: (40.8759361954681,-73.912460975194) //same as Xcode 8.3.3

The problem with using 25 is it's way to close. For instance is I use the address 150 W. 225 St, Bronx, NY 10463 with a lat: 40.875487100000001 and lon: -73.913723300000001, the panoView result shows no image. I can only get an accurate panoView image at with a radius of 60 or greater. The problem with that radius is when I use it for different addresses the panoView gets thrown off. Another address would be 1738 Lexington Ave, New York, NY 10029.

I'm not sure what's happening with the new panoView but the coordinate accuracy does not match up with the the older panoView.

-What should happen instead?

Using a radius of 100 I should get the same panoView coordinates and the same image result that I was getting in Xcode 8.3.3. with the Google Maps and Google Places pods that I was using at that time.

Link to the Demo application[1] that reproduces the problem:

My isn't live in the app store yet but the image results returned from the address the user types in is imperative to the success of my app.
 
-Steps to reproduce the problem:

1. Use both Xcode 8.3.3 with the old cocoa pods and then use Xcode 9.0.1 with the updated cocoa pods both for GoogleMaps and GooglePlaces to see the difference between the StreetView images that are returned. Your going to have to try the 3 address I listed below with a radius of 25, 60, and 100.

Using the old pods and Xcode 8.3.3, using a radius of 100 will get the same associated address image it's supposed to bring up.
panoView.moveNearCoordinate(CLLocationCoordinate2D(latitude: xxx, longitude: xxx, radius: 100)

Using the new pods and Xcode 9.0.1, using a radius of 100 will get an a completely different image from what was returned in Xcode 8.3.3.

panoView.moveNearCoordinate(CLLocationCoordinate2D(latitude: xxx, longitude: xxx, radius: try 100, 25, and 60 here)

Using the new pods if you use a radius of 25:

1 Adrian Ave -returns completely different address image
1738 Lexington Ave -returns completely different address image
150 W 225 St -returns the same image from Xcode 8.3.3(radius 100)

Using the new pods if you use a radius of 60:

1 Adrian Ave -returns the same image from Xcode 8.3.3(radius 100)
1738 Lexington Ave -returns the same image from Xcode 8.3.3(radius 100)
150 W 225 St -returns no image at all

Basically using the new updated pods there isn't a standard radius to use any longer.

2. Using Google Place Autocomplete I type in the address and get the lat and lon that is returned. From there I pass in the lat and lon to GoogleStreetView using the panoVIew and get the image that is returned.

Directions:
https://developers.google.com/places/ios-api/autocomplete
https://developers.google.com/maps/documentation/ios-sdk/streetview

3.
The addresses I use are:

#1
1 Adrian Ave
Bronx, NY 10463
lat: 40.8760214
lon: -73.9126076

#2
1738 Lexington Ave
New York, NY 10029
lat: 40.7939914
lon: -73.9453045

#3
150 W 225 St
Bronx, NY 10463
lat: 40.875487100000001
lon: -73.913723300000001

Operating system version:
Google Maps SDK for iOS version:
Google Places API for iOS version:
Hardware model:

----------------------------------------------------------
Original Platform iOS:
Xcode 8.3.3
Deployment Target 9.1

Original Pods:
GoogleMaps (2.0.0)
GoogleMaps/Base (2.0.0)
GooglePlacePicker (2.0.0)
GooglePlaces (2.0.0)
GooglePlacesAPI (1.1.3)

----------------------------------------------------------
Updated Platform iOS:
Xcode 9.0.1
Deployment Target 9.1

Updated Pods:
GoogleMaps (2.5.0)
GoogleMaps/Base (2.5.0)
GooglePlacePicker (2.5.0)
GooglePlaces (2.5.0)
GooglePlacesAPI (1.1.3)

***These updated pods are causing problems***
----------------------------------------------------------

I'm using a MacBook pro 13 inch early 2011 running Sierra 10.12.6

I'm running the tests on an iPhone 7Plus and an iPhone 4s. The results are consistent on both phones

-------------------------------------------------------------------
[1] You can fork https://github.com/googlemaps/maps-sdk-for-ios-samples.git and modify it until it demonstrates the issue