Timeout while searching for location - Angular 2

Description Of The Issue

When requesting a users location after a successful location services request, the getCurrentLocation method times out.

import {Component, OnInit} from "@angular/core";
var geolocation = require("nativescript-geolocation");

@Component({
    selector: "my-app",
    templateUrl: "app.component.html",
})
export class AppComponent implements OnInit {
    status:string = "Location services not enabled";

    ngOnInit() {
        if (!geolocation.isEnabled()) {
           geolocation.enableLocationRequest().then(() => {
                this.getLocation();
            });
        }
        else {
            this.getLocation();
        }
    }

    getLocation() {
       // this method times out when called from the enableLocationRequest promise
        geolocation.getCurrentLocation({ timeout: 20000 }).then((location) => {
            this.status = `Latitide: ${location.latitude}, Latitude: ${location.longitude}`;
        });
    }
}

Expected Result

The application should request access to the user’s location and then display their latitude and longitude.

Actual Results

The getCurrentLocation method times out.

geolocation-timeout-log.txt

Steps To Recreate

1. tns create geolocation --ng
2. replace the code in app.component.ts with the code above
3. tns livesync ios --emualtor --watch or tns livesync android --watch (Android Studio Emulator)

Environment Configuration

• NativeScript CLI 2.2.1
• Node 5.4.0
• iOS Simulator version 9.3
• Android API version 22 Emulator

[vchimev]

Hey @burkeholland,

For the Android side you could check out:

1. The emulator should use the Google APIs System Image; here is a reference to the Android SDK Manager.
2. In the Settings menu, the Location option should be turned ON.

Let me know how it goes.

[toddanglin]

I ran in to this same challenge with the iOS Simulator and geolocation timeouts.

Burke’s solution worked for me, too, even though I had not set a custom location. I was using the standard/default “Apple” location. Simply changing this location to “None” and then back to “Apple” in the Debug > Location menu fixed the simulator. Now getCurrentPosition does not timeout.

It appears there is indeed an odd behavior in the iOS Simulator that requires you to change the Location value at least once to set it.