GE4.7\GVH2.8: “find me” fails to work and generates “There was an error in geolocation: insufficient permissions for geolocation”,
GE4.7\GVH2.8: “find me” fails to work and generates “There was an error in geolocation: insufficient permissions for geolocation”,
Despite the fact that the geolocation feature is activated at the level of geocortex manager and Samsung device, “find me” tool fails to work and generates the error "There was an error in geolocation: insufficient permissions for geolocation”.
what might be the issue here?
_img_ alt="User-added image" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=90660000000Gu3L&feoid=Body&refid=0EM60000000Ujmd" _/_img_
_img_ alt="User-added image" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=90660000000Gu3L&feoid=Body&refid=0EM60000000Ujmi"_/_img_
0
-
(https://caniuse.com/#search=geolocation) Some browsers no longer support geolocation for unsecure (HTTP) applications, and others are expected to follow suit. Chrome's desktop browser started requiring secure connections (https://support.geocortex.com/essentialsGSCForum?sub-nav=forum&main-nav=essentials&#!/feedtype=SINGLE_QUESTION_SEARCH_RESULT&id=906600000000BdyAAE) as of version 50 (and v.51 on Chrome for Android). For iOS, Safari started requiring secure connections (https://support.geocortex.com/essentialsGSCForum?id=90660000000PDgrAAG) as of version 10 . Firefox plans to require secured connections for geolocation (https://developer.mozilla.org/en-US/Firefox/Releases/55) in version 55 , due out in August of this year. 0 -
I'm also getting this error, and I'm using https only... 0 -
I removed the depreciated Geolocation URL from the viewer, and checked that I had it correct under GIS Services on the site, but now I'm getting a "Geolocation has timed out" error... 0 -
If the viewer is downloading any resources from HTTP, geolocation may not work on certain devices. I just tracked down an issue with a client where there was an HTTP image in the home panel and on iOS safari, geolocation was not working. Once that image was HTTPS, geolocation worked like a charm. 0
Please sign in to leave a comment.
Comments
4 comments