SETTINGS_CHANGE_UNAVAILABLE when locations are enabled

[yankeppey]

Steps to reproduce:

1. Enable Airplane mode (-> cell operator disabled)
2. Disable Wi-Fi.
3. Enable locations.
4. Start "LocationSettings" example from this repositoty.

Expected result:
LocationSettingsStatusCodes.SUCCESS or LocationSettingsStatusCodes.RESOLUTION_REQUIRED in onResult callback, because we're still able to receive updates for the same LocationRequest object.

Actual result:
LocationSettingsStatusCodes.SETTINGS_CHANGE_UNAVAILABLE. However, we still can requestLocationUpdates and receive them.

[Lomovskiy]

Yes, I have the same problem!

[gmarques33]

+1

[saket]

I'm also struggling with this.

[bnvinay92]

+1

[aspyct]

Same problem here. Looks like we won't get a fix anytime soon. Anybody has a good workaround to suggest?

[aspyct]

It seems you can still check for GPS and Network providers via the legacy LocationManager.

See below code (a bit specific, and Xamarin, but hey, you get the idea).

private IObservable<GoogleApiClient> ManualLocationCheck(GoogleApiClient client)
{
    Debug.WriteLine("Google can't tell us how to get location. Checking for ourselves");

    /*
    It looks like we can get a "Settings change unavailable" when the user
    is in airplane mode, but the location is enabled.
    So let's check whether location is enabled, because that's all we need.
    */
    var locationManager = (LocationManager)activity.GetSystemService(Context.LocationService);

    bool gpsEnabled;
    bool networkEnabled;

    try
    {
        Debug.WriteLine("Checking for GPS support");
        gpsEnabled = locationManager.IsProviderEnabled(LocationManager.GpsProvider);
    }
    catch (Exception e)
    {
        Debug.WriteLine(e);
        gpsEnabled = false;
    }

    try
    {
        Debug.WriteLine("Checking for network support");
        networkEnabled = locationManager.IsProviderEnabled(LocationManager.NetworkProvider);
    }
    catch (Exception e)
    {
        Debug.WriteLine(e);
        networkEnabled = false;
    }

    if (gpsEnabled || networkEnabled)
    {
        // Looks like we'll be able to get a location fix after all...
        OnUncertainLocationAvailability?.Invoke(new UncertainLocationAvailability
        {
            GpsEnabled = gpsEnabled,
            NetworkEnabled = networkEnabled
        });
        return Observable.Return(client);
    }
    else
    {
        // Nah, nothing we can do except ask the user to fix his settings
        throw new LocationNotAvailableException();
    }
}

[nidhishah-rally]

+1

[rakuishi]

+1

[Rex1313]

+1 It is hilarious that we need to use LocationManager as a backup

[dtunctuncer]

+1

[farmazon3000]

same happened to me :(

[igor-korotenko]

+1.
Any answer from maintainers?
Bug seems to be too easy to reproduce for not being fixed for 4 years.

[rolfwessels]

+1 Still having the same issue