Timeout searching for location on Android (Nativescript 3.0.3)

[clarenceh]

I saw issues reported on forum and this repository about issues on reading location on Android on NS3.0. I just want to report that it also not working on Nativescript Sample application.

Steps to reproduce:

• Clone the NS sample app repo (https://github.com/NativeScript/nativescript-sdk-examples-ng)
• run tns install
• run tns run android --emulator
• go to the location sample and click read current location

The plugin runs fine on iOS.

Attached please found the screenshot for your reference.

Versions:
│ Component │ Current version │ Latest version │ Information │
│ nativescript │ 3.0.3 │ 3.0.3 │ Up to date │
│ tns-core-modules │ 3.0.1 │ 3.0.1 │ Up to date │
│ tns-android │ 3.0.1 │ 3.0.1 │ Up to date │
│ tns-ios │ 3.0.1 │ 3.0.1 │ Up to date │

Hope this can help and let me know if need any further information.

Regards
Clarence

[OPADA-Eng]

same thing happening with me. any help ?

[OPADA-Eng]

I noticed that sometimes the internet connection type may cause this problem so try to change internet provider.

[tbozhikov]

Hi @clarenceh, looking at the sceenshots I see that you are running the app on emulator. You might check the Location options/settings/controls of the emulator if you can "Send" location to the device like the Android emulator for Mac:

Do you guys get the same exception when running the app on a physical device?

[dvdbrk]

Got the same problem. I don't think it has anything to do with emulator tho 😕

[marcel-braun]

I get the same error. iOS is working but Android unfortunately not.

[jaredjohnson59]

Has anybody found a solution for this issue on Android? I am still getting the following "JS: Error: Timeout while searching for location!"

[bufke]

Running the Send location command as described in the Android emulator makes it work for me - of course that is a workaround and generally unpleasant.

[clarenceh]

@tbozhikov Sorry for my late reply. Yes I can send location to the emulator. I opened Google Map, and then in emulator's location setting, change the value for latitude and longitude, and the location on the map was updated successfully. Have you had a chance to check out the NS Angular examples and test it out as I mentioned in my message? I believe you will be able to re-produce this. Many thanks, Clarence

[jeremypele]

Got the same issue here. Tested on many emulators and many real devices.
Last one is on Android 7.0, wifi - network - gps enabled. Timeout on location request almost anytime.

Using version 3.0 of the plugin

As for my dependencies:

┌──────────────────┬─────────────────┬────────────────┬─────────────┐
│ Component        │ Current version │ Latest version │ Information │
│ nativescript     │ 3.1.3           │ 3.1.3          │ Up to date  │
│ tns-core-modules │ 3.1.0           │ 3.1.0          │ Up to date  │
│ tns-android      │ 3.1.1           │ 3.1.1          │ Up to date  │
│ tns-ios          │ 3.1.0           │ 3.1.0          │ Up to date  │
└──────────────────┴─────────────────┴────────────────┴─────────────┘

[lecaobaophuc0912]

Hi , i have error same thing, i fix with open Location( or GPS ) of device choose Location Mode is a Hight accuracy. A reason is your device auto turn on Battery saving move or Device only mode. it is slow in get location from GPS. that plugin working with android and ios with me, i think it not a prolem.
Hope this will help...

[jeremypele]

@LeCaoPhuc Regarding the different tests I've done this weekend: on a real device it works well when data is active. If gps + wifi are active then it's not working well - even if accuracy is set to the highest on device settings

[lecaobaophuc0912]

@jeremypele your mean is in real device, if you use data (3g,4g) and turn on gps then you always get location. but if use wifi to connect internet, location will slow and time out if accuracy not in highest .
If problem as you talk , i don't know reason because with me, event if Device only mode in GPS all work fine.

[moayadnajd]

same thing happening with me. any help ?

[F481]

Same problem for me on real Galaxy S7 with Android 7.