Geolocation not working after upgrading iOS to 10.3.1

Permanently deleted user

18. April 2017 12:30

I upgraded a iPad to iOS 10.3.1 and now I get the following error "There was an error in geolocation. Geolocation has timed out." when I try to use Geolocate. I'm using HTML5 2.7.2 viewer. Has anybody else experienced this?

0

• 

  Permanently deleted user

  18. April 2017 15:56

  Hi Steve,

   

  Thanks for reporting this!  Yes, we are aware of this issue, and it is being tracked under the following bug ID: GVH-14519

   

  We don't have a timeline for a fix yet, but it's been validated, and will be resolved in a future release.

   

  I'll add you as a stakeholder on the issue.

   

  Thanks,

   

  Danny

  0
• 

  Permanently deleted user

  18. April 2017 18:53

  Please add me to your list of stakeholders. Thanks!

  0
• 

  Permanently deleted user

  24. April 2017 21:00

  Hi Steve and Peter,

   

  I'm pleased to say that we have a workaround for this issue!

   

  1) Back up your sites's viewer configuration (Here by default: C:\Program Files (x86)\Latitude Geographics\Geocortex Essentials\Default\REST Elements\Sites\YourSite\Viewers\YourViewer\VirtualDirectory\Resources\Config\Default)

   

  2) Modify your desktop.json.js file

   

  3) Search for the following line:

   

  "enableHighAccuracy": true,

   

  4) Directly below that line, add the following line:

   

  "timeout": 100000000000,

   

  5) Repeat step 2-4 for the Handheld and Tablet json.js files.

   

  This should get your geolocation working again!  if it doesn't, please open a support case so we can assist.

   

  Thanks,

   

  Danny

  0
• 

  Erik Engstrom

  24. Mai 2017 13:35

  Thanks Danny, this worked for us!

  0
• 

  Permanently deleted user

  31. Mai 2017 18:27

  Update: this issue has been fixed in the 2.8.1 HTML5 viewer.

  0
• 

  Jeff Pope

  2. Juni 2017 13:25

  I still have this same issue with iOS 10.3.2 and HTML5 2.8.1.

  0
• 

  Permanently deleted user

  2. Juni 2017 14:56

  Your work around  did cause the geolocation to work, but it seemed like it went into a loop and never finished - the spot appeared, but it did not zoom to, and it never stopped spinning on the bottom.

   

  I tried to do the update, but when deploying to IIS, it complained about my folder in the wwwroot folder already there.  I was unable to rename the old folder, and this is a production site, so didn't do much more... 

  0
• 

  Permanently deleted user

  2. Juni 2017 15:37

  Got the 2.8.2 installed, and now the Find Me will zoom to location, but the thing is still spinning on the bottom for a long time.  I went into the same json files and took out a zero from each of the three singleGeolocationProfiles - e.g. 3000 instead of 30000 for the default, and now it seems to work fine.

  0
• 

  Permanently deleted user

  3. Juni 2017 18:48

  Hi All,

   

  The issue is still there despite the fact that LG confirmed that it is resolved in 4.7.1\2.8.2.

   

  Is the issue solved for https or http?

   

  Best,

   

  Fatin

  0
• 

  Permanently deleted user

  5. Juni 2017 15:31

  Hi Fatin,

   

  This issue is solved in 2.8.1.  In order to use geolocation, you need to access your map over HTTPS.  This is a limitation of the browser, and is not something that we can solve.

   

  If you are using HTTPS, and you are still seeing this issue, please let me know.  

   

  Thanks!

   

  Danny

  0
• 

  Dibya Pradhan

  21. Juli 2017 14:33

  Hi Dan,

   

  Does Geolocation work on GCX 2.6.3 / GVH 2.7.2.?

   

  I have converted our site to https, we are using all https map services and geometry services and I have also done all the changes suggested above but I'm still getting Geolocation has timed out. 

   

  Thanks,

   

  Dibya

   

   

  0
• 

  Permanently deleted user

  2. August 2017 16:38

  Hi Dibya,

   

  Yes, that should work.  Are you seeing this just on an iOS device, or on the desktop version of the site as well?

   

  Thanks!

   

  Danny

  0
• 

  Permanently deleted user

  4. August 2017 11:45

  Thanks Daniel, the fix worked for us with GE4.6.3 and GHV2.7.2

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.