Include the following details (edit as applicable):
- Issue category: VPS
- Host machine & OS version: Mac
- Issue Environment : Unity Mock
- ARDK version: 2.0.0
- Unity version: 2021.2.7f1
Description of the issue:
When setting the spoof location in the VPS Coverage Image template (VPS Coverage Image – Niantic Lightship), if I set it to an Australian GPS location (e.g. -33.75271477354195, 150.69735115186165), I get the error of:
ArgumentOutOfRangeException: Argument must be in range of -180 to 180
Parameter name: longitude
Niantic.ARDK.LocationService.LatLng…ctor (System.Double latitude, System.Double longtitude) (at Assets/ARDK/LocationService/LatLng.cs:32)
Niantic.ARDK.LocationService.LatLng.ToDegrees () (at Assets/ARDK/LocationService/LatLng.cs:180)
Niantic.ARDK.LocationService.LatLng.Add (System.Double bearing, System.Double distance) (at Assets/ARDK/LocationService/LatLng.cs:157)
Niantic.ARDK.LocationService.SpoofLocationService.StartTravel (System.Double bearing, System.Double distance, System.Single speed) (at Assets/ARDK/LocationService/SpoofLocationService.cs:206)
Niantic.ARDK.LocationService.SpoofLocationService.StartTravel (Niantic.ARDK.LocationService.LatLng destination, System.Single speed) (at Assets/ARDK/LocationService/SpoofLocationService.cs:222)
Niantic.ARDK.Templates.VPSCoverageController.ProcessTargetsResult (Niantic.ARDK.VPSCoverage.LocalizationTargetsResult result) (at Assets/LightshipHUB/Runtime/Scripts/VPSCoverageController.cs:104)
Niantic.ARDK.VPSCoverage._MockCoverageClient.RequestLocalizationTargets (System.String targetIdentifiers, System.Action`1[T] onTargetsReceived) (at Assets/ARDK/VpsCoverage/CoverageClient/_MockCoverageClient.cs:78)
System.Runtime.CompilerServices.AsyncMethodBuilderCore+<>c.b__7_0 (System.Object state) (at :0)
UnityEngine.UnitySynchronizationContext+WorkRequest.Invoke () (at /Users/bokken/buildslave/unity/build/Runtime/Export/Scripting/UnitySynchronizationContext.cs:153)
UnityEngine.UnitySynchronizationContext.Exec () (at /Users/bokken/buildslave/unity/build/Runtime/Export/Scripting/UnitySynchronizationContext.cs:83)
UnityEngine.UnitySynchronizationContext.ExecuteTasks () (at /Users/bokken/buildslave/unity/build/Runtime/Export/Scripting/UnitySynchronizationContext.cs:107)
Has anyone else had this issue? I haven’t been able to test on device yet (not related to this bug), but wanted to raise this in case it’s something others might have come across too.