Skip to main content

Identify/MapTip no longer working in Chrome for some users

Comments

30 comments

  • Max Molello
    We've also see this seemingly randomly affect users, we have no known fix either.
    0
  • Permanently deleted user
    Same for us here in Alberta. Some Chrome users functionality is fine but as soon as you go to the next office, no response at all for map tips, identify by point, or adding vertices while measuring/drawing. I'm wondering if it could be some extension specific to those users that was updated and causing the issue.
    0
  • Permanently deleted user
    I was experiencing this as of last week. We upgraded to the 4.14.1 viewer, and for a week or two I noticed this behavior also!

     

    If you do a right-click > Find data on the map (default tool/behavior) - it seems to trigger the client, and the map tip then starts working again. 

     

    But having said all this, I don't really get the problem on a consistent basis - which can be a little frustrating I guess. ie. just this morning I noticed the problem, and now, having just refreshed the browser session, I no longer get it - very strange....

     

    just my 2c worth... but agree - there is something NQR here..

     

     

    cheers

     

    GF
    0
  • Permanently deleted user
    Just further on this, can we get a feel for what viewer versions this is symptomatic on please. As mentioned, I've just updated to 4.14.1

     

    would be great to know if this is a 'viewer thing' or a 'chrome thing'

     

    I have not seen this behaviour in any of our 2.11.1 Viewer sites....

     

     

    cheers

     

    GF
    0
  • Carmen Durham
    Update... our viewer is at 4.12.2 of viewer. We had not made any upgrades to GCE or Viewer in a while I did just change a data layer in the last week but that's it. For the user I dealt with today - reinstalling Chrome did not work. She is having to use IE or Edge. I have submitted to Support and they seem aware of the issue.
    0
  • Emily Renkema
    Same here! So far only 2 users have reported it and it seems to be temporary, but now I'm concerned about this being a larger issue
    0
  • Emily Renkema
    We're using 4.12.0 by the way
    0
  • Carmen Durham
    we tried this and it didn't work for us. I would like to hear from others if it worked for you.
    0
  • Annet Naus-Hospers
    Hi Carmen, a strange. You have renamed the folder 'User Data' ? And restarted Chrome? Chrome should act as if it is newly installed.
    0
  • Stefan Schweigert

    Hello All,

    I haven't been able to reproduce this issue when using that version of Chrome with any version of GVH 2.11 and newer.

     

     

    Are there any details that you can provide on the hardware and software of affected machines? I'm particularly wondering about what version of Windows is being used on the client machines and if they might be x86-based.

     

     

    Also, are there any errors or warnings in the Chrome DevTools (F12) console?

    Thanks, Stefan

    0
  • Permanently deleted user
    Comparing two machines in our office, one of which using Chrome functions properly, while the other using the same version of Chrome is experiencing these issues stated above. Both are Windows 10 Pro 64 bit. I experience the same issues at home while using CHrome and am using an iMac.
    0
  • Permanently deleted user
    We have seen this issue on random machines.  Does not seem to be version specific as we intentionally upgraded old chrome versions to see if we could trigger it.  It works fine on some machines and fails on others.  they are alI 64 bit windows 10.  still testing...
    0
  • Permanently deleted user
    agree with Daniel.

     

    There seems to be no pattern to this. Even on my laptop (win10), it can behave differently one day to the next! Other team members with the same spec laptops, and chrome versions are not seeing this behaviour.

     

    I will sniff the dev tools next time I get the problemo.
    0
  • Permanently deleted user
    ok - just getting the problem again now - as I went to test, however,  I have some sessions open from yesterday and they seem to be 'stale' for want of a better word.

     

    The map tip does not work, but also the right-click > find data, and the normal Identify tools do not work either, they just sit their spinning, and returning nothing. 

     

    I can't see anything in the Dev tools - nothing is returned.

     

    This is the first time I've noticed this using a session that's been opened with many hours of inactivity - this could be normal behaviour perhaps?? 

     

    I refreshed the client/site, and everything returned to normal - map tips included.
    0
  • Mark Peacey
    We're hitting the same issue with Chrome Version 89.0.4389.90 (Official Build) (64-bit), which was rolled out in the last week. For some users it works fine and others are hitting this issue. Nothing in Dev Tools, it just fails to fire anything.

     

    It also affects the draw tool, users with the issue have to double click for the stating vertex but then can't single click to add the next vertex to continue drawing. They have to double click and that ends the drawing.
    0
  • Dan Giersz
    We also had a user complaining about this a week or so ago. Maptips and Measure tool were not working. Measure tool eventually started working again, but no Maptips. Dev tools in Chrome didn't even show the Maptips module loading...
    0
  • Permanently deleted user
    We have had mixed results uninstalling Chrome and reinstalling Chrome.  But I see this has been temporary for some people.
    0
  • Permanently deleted user
    Hi everyone,

     

     

    We've found an Esri thread that sounds like it could be our issue:

     

     

    https://community.esri.com/t5/arcgis-api-for-javascript/javascript-api-3x-map-click-event-intermittently-fails-to-fire/m-p/1041632

     

     

    If someone has a live Chrome session with a broken viewer, can we have them try launching our demo viewer and attempting a similar operation:

     

     

    https://gedemo.geocortex.com/Html5Viewer/index.html?viewer=LACountyPlus& 

     

     

    The demo viewer uses Esri javascript API 3.34 which (in theory) should work as expected.
    0
  • Permanently deleted user
    Hi everyone (again),

     

     

    I spoke too soon!  That demo viewer is having some non-Chrome-related problems with its backing server.  Clicks work fine!  Identify does not.

     

     

    This one should work though: https://gedemo.geocortex.com/Html5Viewer/index.html?viewer=CapitalCity

     

     

    It's sure going to be nice using the Community for these threads, I'll be able to edit my own posts!  What wonders of technology.

     

     

    Regards,

     

    -Malcolm

     

     
    0
  • Kate Weber
    I've narrowed down the issue is specific to user's profile and computer.  I logged on their computer and was able to use the tools and they logged onto another computer and the tools worked.
    0
  • Carmen Durham
    I see that Chrome has pushed out an update. Before we look at upgrading GCE and the Viewer, has anyone tried the updated Chrome and still experienced the problem? An upgrade to GCE and the Viewer is not what was on our "schedule" for the next week or month! A coworker was handling our case late last week while I was out which is why I haven't been responding until now. Thanks, Carmen
    0
  • Permanently deleted user
    We are also experiencing this issue.  We are using Essentials 4.12/HTML5 4.12.2; Chrome 89.0.4389.114.  Some of our users had deleted the Chrome user folder last week, which solved the problem for us and it has not yet resurfaced.  I had one user that was experiencing this issue who had not yet deleted her Chrome folder, so I had her test the site that Malcom posted and the Identify tool works on that site. So, now I am just even more perplexed.
    0
  • Permanently deleted user
    Hi Everyone,

     

     

    I believe this Esri bug is our culprit:

     

     

    https://support.esri.com/en/bugs/nimbus/QlVHLTAwMDEzODY4NA==

     

     

    While a Chrome update/rollback may resolve the issue, we haven't been able to successfully confirm the behavior here in-house so we also can't confirm if it gets fixed by Google.

     

     

    Geocortex Viewer for HTML5 4.13 uses Esri Javscript API 3.31, so any installations of GVH older than that could encounter this bug.

     

     

    Upgrading to 4.13 or later (we always recommend the latest!) is the best solution we have right now.  We've had some customers report that upgrading resolved their issues.

     

     

    Regards,

     

    -Malcolm
    0
  • Permanently deleted user
    @malcolm - we first noticed this problem after upgrading to 4.14.1 - so I'm not sure that upgrading is the silver bullet either unfortunately.

     

    My laptop has just done a forced update of chrome this morning so I'll test it out further, but as I've mentioned already, this quirk is a hard one to replicate and test.
    0
  • Kate Weber
    @Gareth.  We had already upgraded to 4.14.2 in our dev environment so I had users test there.  This version appeared to have fixed the issue for the users who reported having the issue.  I did not have the issue and it still worked for me.  (Always good to check that too.)

     

     

    Malcom posted more info on the new site:  https://communities.geocortex.com/s/feed/0D55x00007YqALjCAN 
    0
  • Carmen Durham
    Over the weekend, we performed the upgrade on our main Intranet site where we had identified users that were having issues.  The affected users were again able to use Chrome for the left-click mouse events.

     

     

    Thanks,

     

    Carmen
    0
  • Chris Roberts
    Hi All

     

     

    We are on 4.10.2 and 2.11.2 we have had no reported issues from either our internal or external users.  I have tested on both my work PC and a couple of external PCs all with the latest version of chrome and edge, and the left click works as expected.

     

     

    If someone who was experiencing this issue could test our external site and let me know if they see any issue it would be appreciated.

     

     

    http://spatialwebapps.environment.sa.gov.au/naturemaps/?locale=en-us&viewer=naturemaps

     

     

    According to our local Geocortex support because we are a little behind in our upgrading I will likely need to do a two step upgrade 4.10.- 4.12 - 4.14 ... I'm a  little stretched at the moment, so if it aint broke don't fix it :-)

     

     

    Cheers

     

     

    Chris

     

     
    0
  • Tom Neer
    Chris,

     

     

    Unfortunately, there is no solution except to upgrade to 4.12 or later. This is not only affected web GIS but other web applications also. As a workaround, the right-click Identify still works. 

     

     

    This is limited right now to Google Chrome 89. However, since nearly every web browser, except Firefox, is based on the Chromium code-base, it will eventually percolate down to the majority of browsers.

     

     

    Sorry for the bad news. We've been working with clients to get them upgraded. This bug affects:
    • ArcGIS Enterprise using Portal for ArcGIS 10.8.0 or earlier

    • Geocortex Essentials 4.12 or earlier

    • Web AppBuilder for ArcGIS 2.14 or earlier

    • Custom applications using ArcGIS API for JavaScript 3.30 or earlier

    0
  • Piper McKinnon
    Hi All, I'm looking for advice with upgrading - is it advisable to upgrade directly to 4.14.2 from Essentials 4.11.0.94 with HTML5 viewer 2.12.1? Or should it be a stepped approach?

     

    Appreciate any guidance, thanks
    0
  • Piper McKinnon
    FYI, Malcolm responded to my question above on https://communities.geocortex.com/s/feed/0D55x00007YqALjCAN 

     

     

    "You should be able to go straight to the latest from 4.11/2.12. We haven't required a staged upgrade for a long time, so I think any 4.9/2.10 version or later can be upgraded to the latest in a single operation."

     

     

    Thanks again Malcolm
    0

Please sign in to leave a comment.