Update ESRI JS API to 3.26 - Is this supported?
We have some ruggedized field laptops with touchscreens (Chrome / Windows 10 / Essentials 4.9 / 2.10 VTE) that we noticed do not support gestures to pan and zoom the map control. All other touch functions work... clicking toolbar tabs & buttons, navigating the layer list, etc... just pan and zoom do not work from the touchscreen.
We found that there is a bug in the 3.21 JS API from ESRI that is causing this in the latest version of Chrome (v68.x.x.x....). ESRI has reported that the bug was resolved in the 3.26 version of their API and it does not appear they will patch or resolve it at 3.21.
So... is there support for moving to 3.26?
Are there other issues this will introduce?
Is there a support matrix anywhere that highlights known issues between GVH and different ESRI's JS APIs?
0
-
Hi Lance,
During development of GVH 2.11, we tested upgrading to newer versions but decided against a major upgrade to the latest due to some inconsitencies in markup behaviour between versions on mobile devices, so I wouldn't recommend upgrading yet.
We are looking into using 3.26 for the next release of GVH.
Thanks, Stefan0 -
Thanks for the reply Stefan. I have additional questions stemming from your response.
Since 3.26 had rendering issues on Mobiles, I understand the decision not to roll it out, however, in my situation, the users are not using Mobile / Handheld devices. They only use the application on Desktop devices. With that in mind, were any issues recorded in the 3.26 testing that affected Desktop devices? If not, we may explore updating to 3.26 anyway. But if there is a long list of known issues, we’d hold off. Beyond this, if updating to 3.26 would disrupt support from you, please let me know that as well. That would likely be a deal-breaker when considering an update.0 -
No problem. One of the issues found was in all platforms: a major number of additional requests were being generated to the feature service when making measurements on the map, when there should be none, which would have impacted performance. This issue was found against 3.24, no testing was done with 3.25 as it was not released at the time.
We do not recommend upgrading the JSAPI. Support would be able to assist in terms of understanding your situation but since the product would not have gone through regression testing with this version of the API, they may not be able to help with incidental issues that come up as a result of the upgrade.
Thanks, Stefan0 -
How confident are you that the next release will use 3.26? "Looking into it" sort of leaves it open that it may not actually happen and I'd just like to understand the level of certainty here for the benefit of our planning. Has Latitude contacted ESRI about potentially patching 3.21 as I would imagine this affects all GVH5 users that have touchscreens and that use Chrome. 0 -
GVH 2.12 will use 3.25. We are planning on testing the upgrade in the next month or so and will have more information soon.
3.26 is not available yet but we will consider it if it is released early enough prior to our planned release to be tested.0 -
Sorry for the delay... we are circling back around to this issue today and we are in conversations on this with ESRI support as well. They are wondering what is the latest version of the JS API that Essentials 4.9, GVH 2.10 will support or is certified against. GVH 2.10 shipped with ESRI 3.21, but has GVH 2.10 been certified against any later version of the JS API? Your earlier reply on August 29th indicated testing was done against 3.24, but an issue was found with the measurement tools... this makes me wonder if 3.23 or anything after 3.21 is also certified/supported for GVH 2.10 - if so, please let me know. Thanks! 0 -
Upgrading and testing against an updated version of the API is a time-intensive process, so we only looked at upgrading to 3.24 during that time period. 0 -
Hey Stefan - Hoping to revive this conversation a bit. In the last couple months, ESRI has addressed this issue in the 3.21 API and have fixed the gestures issue. My problem now is that we consume the API locally as the field technicians do not have open internet access to obtain the API from js.arcgis.com. I presume this means to consume the fixed API we'd have to replace the existing local API baked into the application's Resources\Scripts directory in IIS. What is the procedure to accomplish this? I'm hesitant to just copy / paste the new API into that directory for two reasons... 1- there appears to be a 3.21 and 3.21 Compact version of the API from ESRI - which is required for the viewer, and 2- there appears to be Geocortex files intermingled in the existing local API directory structure.
So, in short, how do we consume the updated 3.21 API locally?
0 -
Hi Lance,
We would probably have to create the updated 3.21 file for you, though it would be an easy swap of a single file (esri.js) once done. This file combines a number of separate files from the original api download package.
Alternatively, the upcoming release of GVH (2.12) will include the 3.27 api which also includes the fix for Chrome on touchscreen devices. Unfortunately, earlier versions of this fix in previous api releases no longer work in the latest version of Chrome.0 -
In our client's test environment I replaced the esri.js file with the ESRI fixed 3.21 version and left the use local API flag commented out... that enabled gestures but it references a lot of files from js.arcgis.com. If we use the fixed 3.21 esri.js file and set the flag to use the local API, the viewer won't even load.
So... I'll take you up on creating the 3.21 esri.js file for us. Presumably your version would eliminate the calls to js.arcgis.com - or we'd have to add/replace/update other files already in the Scripts directory??? Not sure how that all works, but yes, we need to pursue this. Reach out to me directly if you would please. Thanks!0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
10 Kommentare