Latest Contributions by AndrewMurdoch1

I ran the code on /next and it looks like the problem is "solved", I'm seeing a lot of errors but nothing is doing an inf loop: ... View more

Yes:  It seems to have something to do with stacking the data.  I've disabled the indexDB functionality so we have to load from a HTTP endpoint but I can still run into it. ... View more

We've seen this problem across Firefox / Chromium browsers and on Windows / Linux.  I'm currently on Ubuntu 20.04 Brave. ... View more

Okay, I'll send the HAR file and I'll test on /next to see if I can cause the same problem.  In the case I run into the error it's just from loading the Feature Layer, I'll see one of the port closed errors and then run into this: [esri.views.layers.2d.features.support.AttributeStore] e {name: "mapview-attribute-store", message: "Encountered an error during client initialization", details: e} details: e details: undefined dojoType: "cancel" message: "Abort job: worker closing" name: "AbortError" message: "Encountered an error during client initialization" name: "mapview-attribute-store" Which happens to then cause and info loop, which requires me to jump away from the map quickly, to prevent a total lock up. ... View more

Yes, that's very likely for our use case, as we store the data in the the browser and fetch it from IndexDB when we need it.  Is there a way I can listen for the connect to be ready / set before I go to create the feature layer? ... View more

How can I upload a file or is there any email I can send the HAR file to? ... View more

I'm going to try getting a HAR capture, if I do I'll attach it. ... View more

Good Day This issue disappeared for months but now it's popping up, but I can't seem to figure out any pattern.  Would it be possible to edit the error message to show what's happening to help debugging, or catch the error in dojo-lite and discard it?  I haven't been able to make a source repo that demonstrates the problem.  Thanks ... View more

Okay, I have a potential workaround on my end but it's less then ideal.  If there's no simple / non-hackish ways to pull this off then I see about editing my code. Thanks! ... View more

Good Day Thanks for the suggestions, that was the problem!  When I changed it to simple-line the problem went away.  I removed the style: null, it wasn't relevant for our actual code base and the same problem persisted on 4.16. Thanks for your help. ... View more

Any idea what the issue might be? ... View more

GitHub - docmur/esri-printtask-issue  If you run that project and press the print button you'll get: ... View more

Thanks for the reply: API Version: 4.14 Example Print Task: Example using the Print Widget Example using the screenshot (Works but doesn't have the template) I generate the polyline geoJSON with this: if (coordinateText) { const _temp = WKT.parse(coordinateText); if (_temp) { let geometry; switch (_temp.type) { case 'LineString': geometry = { type: 'polyline', paths: 'coordinates' in _temp ? _temp.coordinates : null, } break; case 'Polygon': geometry = { type: 'polygon', rings: 'coordinates' in _temp ? _temp.coordinates : null, } break; default: break; } return { geometry: _.cloneDeep(geometry), attributes: { ObjectID: randomObjectID, colour: _.cloneDeep(entry.colour), } }; } } Then I build the Feature Layers with: buildFeatureSettings(geometryType, data, colour) { return { source: data, renderer: this.buildRenderSettings(data, colour, geometryType.toString().includes('point')), fields: this._fields, objectIdField: 'ObjectID', geometryType: geometryType, spatialReference: { wkid: 4326 }, title: 'Random Title' }; } buildRenderSettings(data, colour: string, marker = false) { return { type: 'simple', symbol: { style: marker ? 'circle' : null, type: marker ? 'simple-marker' : 'simple-fill', size: marker ? 12 : 30, color: _.cloneDeep(colour), outline: { width: 4, color: _.cloneDeep(colour), } }, } } Thanks for you assistance, I can try throwing together a code sample a bit later. Thanks ... View more