Latest Contributions by ToddAtkins

In testing out the 4.9 API, I'm running into and issue around CORS with demographics8.arcgis.com. We're pulling a MapImageLayer from this domain and it's throwing a CORS error in the console. I've tried  esriConfig.request.trustedServers.push('https://demographics8.arcgis.com'); but that didn't help. Is there something else I need to do on my end? I'd really rather not setup a proxy since it was working in 4.8 but if that's what's required, then I'll do it. I'm wondering (hoping) if there's some issue on the Esri side for this? And for what it's worth, the legend for the layer does work--just the actual map part of the service is throwing this error. Here's the two errors it's throwing: Access to Image at 'https://demographics8.arcgis.com/arcgis/rest/directories/arcgisoutput/USA_Demographics_and_Boundaries_2018_MapServer/x_____x8rpmfxe7ycCrgTOULj6txw..x_____x_ags_map00d241a884ec469dafb1aeebc2cb111d.png?token=<redacted>' from origin 'http://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:3000' is therefore not allowed access. and {"error":{"name":"request:server","message":"Unable to load the resource","details":{"url":"https://demographics8.arcgis.com/arcgis/rest/directories/arcgisoutput/USA_Demographics_and_Boundaries_2018_MapServer/x_____x8rpmfxe7ycCrgTOULj6txw..x_____x_ags_map00d241a884ec469dafb1aeebc2cb111d.png?token=<redacted>","requestOptions":{"responseType":"image"},"ssl":false}}} ... View more

I've got a feature layer on AGOL that users picture marker symbols for its symbology. If I enable webgl feature layer using  "esri-featurelayer-webgl": 1‍ then the symbols do not all render correctly though they are correct in the legend: Disabling esri-featurelayer-webgl solves the issue but then breaks the labeling and feature highlights for popups which are required for the app I'm building here. The incorrect symbols appear as a mishmash of other symbols squished together. This is observed in both Chrome and Firefox on OS X. Using JS API 4.8. Any ideas here? Is this a bug in the API or something I'm doing wrong on the coding side? ... View more

Hello, I'm attempting to get the Print Widget functioning with some secured layers hosted on AGOL but am running into some difficulty getting this to work. We have several feature layers that we've created (a mix of both points and polygons) and if any of them are turned on, the print widget fails: {    "error": {    "code": 400,    "extendedCode": -2147467261,    "message": "Unable to complete operation.",    "details": ["Error executing tool. Export Web Map Task : Failed to create layer from service at https://services8.arcgis.com/redacted/arcgis/rest/services/redacted/FeatureServer/0.\nFailed to execute (Export Web Map).\nFailed to execute (Export Web Map Task)."]    } } The strange this is that the print widget DOES work as expected with various Esri provided "premium" layers such as Tapestry Segmentation, Population Density, etc. It seems like it should be possible to get this print service to work with AGOL secured services, since it works withe the Esri premium layers but this one has me baffled. If anybody has any insight into this, it'd be appreciated. Thanks. Relavent code snippets: Print Widget const print = new Print({    view: this.view,    printServiceUrl: 'https://utility.arcgisonline.com/arcgis/rest/services/Utilities/PrintingTools/GPServer/Export Web Map Task', }); this.view.ui.add(print, 'top-right'); Feature Layer import FeatureLayer from 'esri/layers/FeatureLayer'; import popupTemplate from '../../helpers/redacted'; const fLayer = new FeatureLayer({    url: 'https://services8.arcgis.com/redacted/arcgis/rest/services/redacted/FeatureServer/0',    outFields: ['*'],    title: 'redacted',    opacity: 1.0,    visible: false,    popupTemplate: popupTemplate }); export default fLayer; This is observed in MacOS, Chrome 67. I'm using the Esri js cli version 4.7 and Typescript. ... View more