You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today I'm working on a navigation app, and we use @nativescript/directions 2.0.2.
Since our last upgrade, Directions.available() returns false, but it should return true, and when (for testing) we call directly Directions.navigate(), the navigation app opens correctly.
let directions = new Directions();
directions.available().then(available => {
console.log({ available }) // return false
if (true) { // force to enter and it
directions.navigate({ // it works despite the available = false !!!
to: {
lat: parseFloat(this.totem.latitude),
lng: parseFloat(this.totem.longitude),
}
}).then(() => { }, () => {
GlobalService.toast(localize('app.gps_unavailable'));
});
} else {
GlobalService.toast(localize('app.gps_unavailable'));
}
});
Can you help me please ?
Best regards
The text was updated successfully, but these errors were encountered:
Hello everybody,
Today I'm working on a navigation app, and we use @nativescript/directions 2.0.2.
Since our last upgrade, Directions.available() returns false, but it should return true, and when (for testing) we call directly Directions.navigate(), the navigation app opens correctly.
Can you help me please ?
Best regards
The text was updated successfully, but these errors were encountered: