11-25-2017 03:06 - edited 11-25-2017 03:07
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

11-25-2017 03:06 - edited 11-25-2017 03:07
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
I use the function geolocation.getCurrentPosition(locationSuccess, locationError). I define the functions locationSuccess and locationError as descripted in the SDK-Guide. I also do several console.log-statements.
But obviously neither the locationSuccess function nor the locationError function is called.
I absolutely have no idea why this shouldn't work...
Can somebody help?
11-25-2017 04:37
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

11-25-2017 04:37
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
I am using watchPosition and it seems to works. I'll test again today and post if something seems odd.
12-02-2017 02:49
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

12-02-2017 02:49
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
@agsurf5geolocation.watchposition() works too, in my app.
But it seems that the function locationError(error) will not be entered.
I mentioned it in another threat: I call locationError() to show that the GPS connection isn't established yet, but since the last OS update that function isn't entered in my opinion, because the commands I execute there don't show any reaction.
Do you notice similair behaivors?
Capitano

12-02-2017 05:22
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

12-02-2017 05:22
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hey Capitano,
It threw an error for me when I did not use the package.json checkbox.
Other than that I really have nothing going on on error, so I can't really tell you.

01-27-2019 10:20
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

01-27-2019 10:20
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I've noticed this exact behaviour when deploying to my ionic via FitBit studio... but it works fine when deploying to the simulator locally. Did you end up finding out what was up?

