Comment 1 for bug 1481240

Hi Shawn,

I think the issue may be that when scopes first run, the location may not yet be known through GPS, and so the less accurate location from IP address based geo-location is used. After refreshing a scope, the GPS based more accurate location is known.

Can you please confirm this as follows:
1) reboot
2) go directly and immediately to the NearBy scope
3) report here whether the listed location is the accurate one or the inaacurate one.
4) refresh NearBy scope by pulling down
4) report here the listed location.

We need to determine whether the initial inaccurate location is due to the time it takes to get a GPS location or if it is due to a shell bug.