{"action":"created","issue":{"url":"https://api.github.com/repos/jamesmontemagno/GeolocatorPlugin/issues/39","repository_url":"https://api.github.com/repos/jamesmontemagno/GeolocatorPlugin","labels_url":"https://api.github.com/repos/jamesmontemagno/GeolocatorPlugin/issues/39/labels{/name}","comments_url":"https://api.github.com/repos/jamesmontemagno/GeolocatorPlugin/issues/39/comments","events_url":"https://api.github.com/repos/jamesmontemagno/GeolocatorPlugin/issues/39/events","html_url":"https://github.com/jamesmontemagno/GeolocatorPlugin/issues/39","id":184868396,"number":39,"title":"timeoutMilliseconds on IOS seems to depict how long the GPS will take to return","user":{"login":"wickedw","id":4195207,"avatar_url":"https://avatars.githubusercontent.com/u/4195207?v=3","gravatar_id":"","url":"https://api.github.com/users/wickedw","html_url":"https://github.com/wickedw","followers_url":"https://api.github.com/users/wickedw/followers","following_url":"https://api.github.com/users/wickedw/following{/other_user}","gists_url":"https://api.github.com/users/wickedw/gists{/gist_id}","starred_url":"https://api.github.com/users/wickedw/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wickedw/subscriptions","organizations_url":"https://api.github.com/users/wickedw/orgs","repos_url":"https://api.github.com/users/wickedw/repos","events_url":"https://api.github.com/users/wickedw/events{/privacy}","received_events_url":"https://api.github.com/users/wickedw/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2016-10-24T15:08:16Z","updated_at":"2016-11-09T19:09:42Z","closed_at":null,"body":"Please fill out either the bug or feature request section and remove whatever section you are not using.\n## Possible Bug\n\nRunning the included SAMPLE app produces some strange behaviour with the timeoutMilliseconds parameter.\n\nOn IOS Device, if I set this to 10 seconds as per sample (no code changes) then the GPS will come back eventually BUT is really slow, it wont timeout but takes approx 10+ seconds (did not time it exactly).\n\nIf I set timeoutMilliseconds to 1000 ms, then the GPS comes back (seemingly correct) after 1 second.\nIf I set timeoutMilliseconds to 500 ms, then the GPS comes back (seemingly correct) after 0.5 seconds?\n\nYes, this does not make sense, I could be doing something wrong, but I am not modifying the sample in any other way, could the async task code IOS imp be getting confused on when it is supposed to return its result?\n\nNOTE The IOS emulator comes back instantaneously no matter the setting.\nDroid (used S3) seem to use the timeout as expected.\n\nUPDATE: After looking at the plugin code, I noticed that the accuracy of 165 of the returned IOS GPS was > then 50 default, so when setting the desired Accuracy to 200 it comes back instant :) but I would like to know why it does return the same result on the timeout above.\nI \"think\" I can see what could be happening in the code for this to happen, will dig further.\n\nVersion Number of Plugin:  3.0.4\nDevice Tested On: IOS 10\n### Steps to reproduce the Behavior\n\nRun the sample with various GPS timeoutMilliseconds as above.\n\nThanks for your help\n\nBest\nMatt\n"},"comment":{"url":"https://api.github.com/repos/jamesmontemagno/GeolocatorPlugin/issues/comments/259498231","html_url":"https://github.com/jamesmontemagno/GeolocatorPlugin/issues/39#issuecomment-259498231","issue_url":"https://api.github.com/repos/jamesmontemagno/GeolocatorPlugin/issues/39","id":259498231,"user":{"login":"alanspires","id":22159404,"avatar_url":"https://avatars.githubusercontent.com/u/22159404?v=3","gravatar_id":"","url":"https://api.github.com/users/alanspires","html_url":"https://github.com/alanspires","followers_url":"https://api.github.com/users/alanspires/followers","following_url":"https://api.github.com/users/alanspires/following{/other_user}","gists_url":"https://api.github.com/users/alanspires/gists{/gist_id}","starred_url":"https://api.github.com/users/alanspires/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/alanspires/subscriptions","organizations_url":"https://api.github.com/users/alanspires/orgs","repos_url":"https://api.github.com/users/alanspires/repos","events_url":"https://api.github.com/users/alanspires/events{/privacy}","received_events_url":"https://api.github.com/users/alanspires/received_events","type":"User","site_admin":false},"created_at":"2016-11-09T19:09:42Z","updated_at":"2016-11-09T19:09:42Z","body":"I have my location set to 1609 meters (1 mile) and this still occurs 75%+ of the time. So I don't believe accuracy is the issue."}}
{"actor":{"display_login":"alanspires"}}