{
	"id": "119671",
	"key": "TIMOB-15088",
	"fields": {
		"issuetype": {
			"id": "1",
			"description": "A problem which impairs or prevents the functions of the product.",
			"name": "Bug",
			"subtask": false
		},
		"project": {
			"id": "10153",
			"key": "TIMOB",
			"name": "Titanium SDK/CLI",
			"projectCategory": {
				"id": "10100",
				"description": "Titanium and related SDKs used in application development",
				"name": "Client"
			}
		},
		"fixVersions": [],
		"resolution": null,
		"resolutiondate": null,
		"created": "2013-09-07T22:05:25.000+0000",
		"priority": {
			"name": "Low",
			"id": "4"
		},
		"labels": [],
		"versions": [
			{
				"id": "15479",
				"description": "Release 3.1.2",
				"name": "Release 3.1.2",
				"archived": true,
				"released": true,
				"releaseDate": "2013-07-31"
			}
		],
		"issuelinks": [],
		"assignee": null,
		"updated": "2018-02-28T20:03:18.000+0000",
		"status": {
			"description": "The issue is open and ready for the assignee to start work on it.",
			"name": "Open",
			"id": "1",
			"statusCategory": {
				"id": 2,
				"key": "new",
				"colorName": "blue-gray",
				"name": "To Do"
			}
		},
		"components": [
			{
				"id": "10206",
				"name": "iOS",
				"description": "iOS Platform"
			}
		],
		"description": "Given that Ti.Geolocation.ACCURACY_BEST is defined as -1, the following code starting at line 275 in GeolocationModule.m, sometimes changes ACCURACY_BEST to ACCURACY_THREE_KILOMETERS.\r\n\r\n{code}\r\n-(CLLocationManager*)locationManager\r\n{\r\n\t[lock lock];\r\n\tif (locationManager==nil)\r\n\t{\r\n\t\tRELEASE_TO_NIL(tempManager);\r\n\t\tlocationManager = [[CLLocationManager alloc] init];\r\n\t\tlocationManager.delegate = self;\r\n\t\tif (!trackSignificantLocationChange) {\r\n            if (accuracy!= ACCURACY_BEST) // -1\r\n            {\r\n                locationManager.desiredAccuracy = accuracy;\r\n            }\r\n            else\r\n            {\r\n                locationManager.desiredAccuracy = ACCURACY_THREE_KILOMETERS;  //kCLLocationAccuracyThreeKilometers\r\n            }\r\n            locationManager.distanceFilter = distance;\r\n        }\r\n...\r\n{code}\r\n\r\nIf you set the accuracy to ACCURACY_BEST before adding the event listener, then it's changed to ACCURACY_THREE_KILOMETERS.\r\n\r\nThis issue was brought up by Ondrej Urik in a comment @ https://developer.appcelerator.com/question/116986",
		"attachment": [],
		"flagged": false,
		"summary": "Geolocation Accuracy sometimes resets from ACCURACY_BEST to ACCURACY_THREE_KILOMETERS",
		"creator": {
			"name": "gorilla128",
			"key": "gorilla128",
			"displayName": "Gordon Illan",
			"active": true,
			"timeZone": "America/Los_Angeles"
		},
		"subtasks": [],
		"reporter": {
			"name": "gorilla128",
			"key": "gorilla128",
			"displayName": "Gordon Illan",
			"active": true,
			"timeZone": "America/Los_Angeles"
		},
		"environment": "iOS",
		"comment": {
			"comments": [
				{
					"id": "419229",
					"author": {
						"name": "bitshftr",
						"key": "bitshftr",
						"displayName": "Shawn Lipscomb",
						"active": true,
						"timeZone": "America/New_York"
					},
					"body": "Why is this a low priority?  It's been there for 3 major versions and looks like a simple fix.",
					"updateAuthor": {
						"name": "bitshftr",
						"key": "bitshftr",
						"displayName": "Shawn Lipscomb",
						"active": true,
						"timeZone": "America/New_York"
					},
					"created": "2017-05-05T21:37:08.000+0000",
					"updated": "2017-05-05T21:37:08.000+0000"
				}
			],
			"maxResults": 1,
			"total": 1,
			"startAt": 0
		}
	}
}