Getting the location tends to time out

[boldtrn]

Using older versions capacitor geolocation plugin, getting the current location was done using the lastKnownLocation. We see a lot of issues in our app because getting a fresh location with not optimal GPS reception creates an error now.

While I think it is great to first use the timeout to fetch a fresh location, there should be either:

• A fallback to return the lastLocation if now fresh location can be fetched
• A second method (or parameter) to return the last known location instead

[alexgerardojacinto]

Hi @boldtrn!

Did you try using a higher value for IONGLOCLocationOptions.maximumAge? With a high enough value, the last known location (cached location) should be returned.

[boldtrn]

@alexgerardojacinto - thanks for the feedback, yes I did try that. The last GPS fix of the device is younger than 5 minutes, yet calling it with:

{
    // Location max 8 hours old
    maximumAge: 8 * 60 * 60 * 1000,
    // 12 second timeout
    timeout: 12000,
    // Update location up to every second
    minimumUpdateInterval: 1000,
    enableHighAccuracy: true,
};

Does lead to:

Sending plugin error: {"save":false,"callbackId":"53121254","pluginId":"Geolocation","methodName":"getCurrentPosition","success":false,"error":{"message":"Could not obtain location in time. Try with a higher timeout.","code":"OS-PLUG-GLOC-0010"}}

It's important that the device is actually indoors or has no active GPS reception (because that obviously works).