Latest Contributions by AndyGup

@GiovanniVanore1 I'm not sure what's going on, I tried just about everything to get the app running right. My recommendation is to start fresh using our Angular sample app: https://github.com/Esri/jsapi-resources/tree/master/esm-samples/jsapi-angular-cli.   ... View more

Hi @GiovanniVanore1 this doesn't sounds like it's related to the ArcGIS API for JavaScript. Can you provide a simple github repo that reproduces the issue? ... View more

It sounds like your assetsPath isn't configured correctly for the subfolder. Are you using the AMD or ES modules (arcgis-js-api or @arcgis/core)? Version 4.19 which is releasing in the next few days has a fix for this. At 4.19 the assets will be pulled from CDN by default so there's no need to configure assetsPath unless you need local assets. You can test this by updating to the "next" version and commenting out your config.assetsPath:   npm i @arcgis/core@next     ... View more

@JohnWyant which API modules are you using, e.g. arcgis-js-api or @arcgis/core? Try testing with our "next" build: https://github.com/Esri/feedback-js-api-next. We fixed a bug at 4.19 that sounds similar. 4.19 will be in production later this week or next week. ... View more

@Sam try testing with our "next' version. Are you using arcgis-js-api (AMD) or @arcgis/core (ES modules)?  They are both available on NPM. If you are using @argis/core then run this command then test again: npm i @arcgis/core@next That will install the preview for version 4.19 which will be coming out in the next week or two. We fixed a couple bugs that may be causing your issue. ... View more

@Valgenmap I followed your instructions and I do see the error now. But I didn't see anything obvious, and I don't understand the architecture of your app. It's too large for simple troubleshooting we can provide through this forum or through Esri tech support. My recommendation is to create a branch and de-construct the app - keep simplifying it - until you figure out the problem. Since you know the architecture I think that wouldn't take very long. The only other alternative is to open a contract with our professional services and they can dedicate time to this level of troubleshooting. ... View more

@Valgenmap Nice site! I didn't see the errors on npm start. Any chance you can provide a repo with just the mapping component that reproduces this issue? That will help to try and isolate the problem.  ... View more

Whoops, I missed one entry. Try also removing this line of code from SalesChartCard.js: esriConfig.assetsPath = '/assets';   ... View more

We don't have this concept in the API, but there is functionality that you can try. The best approach would be to check for layer.loadError and inspect the error that caused the failure, then run layer.refresh(): https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-FeatureLayer.html#loadError And, like your snippet above you could also try adding a request interceptor with the "before" callback. Make the request yourself and then retry. We don't have a way to delay or retry a request automatically: https://developers.arcgis.com/javascript/latest/api-reference/esri-config.html#BeforeInterceptorCallback You might also experiment with watching layer.loadStatus for "failed", here's a sample demonstrating the concept: https://codepen.io/andygup/pen/xxgjQZE?editors=1000  ... View more

I suspect you are using @Anonymous User/core. If that's what's installed then you can try testing with the "next" version by running:   npm i @ArcGis/core@next     And, then remove these two lines from package.json. That might fix the issue you are seeing: "copy": "ncp ./node_modules/@arcgis/core/assets ./public/assets", "postinstall": "npm run copy" ... View more

Hi @Valgenmap can you please share the entire package.json file? Are you using arcgis-js-api or @arcgis/core? Those are both JS API with the exact same functionality, but they use different module types. arcgis-js-api is AMD and @arcgis/core is ES modules. ... View more

Hi @RoyJackson2 , can you share a vanillaJS codepen app that reproduces a 504 timeout? It's very unlikely that Angular is causing the problem, more likely something to do with the network or cloud. A vanillaJS app will help with isolating and troubleshooting the HTTP request issue.  ... View more

@SahilBansal  for your second question about Routes, I recommend creating a new issue with a new Title since it's not related to the original question and Title. That way the question will get more visibility. ... View more

I'm not sure about the sign-in issue, maybe check the permissions on your service.   I talked to a colleague. On the first issue of the Graphic not compiling, I missed the fact that you can't mix a Point with a LineSymbol, so getting a compiler error was valid. We recommending the following, and I verified this works on my machine: import Point from '@arcgis/core/geometry/Point'; import SimpleMarkerSymbol from '@arcgis/core/symbols/SimpleMarkerSymbol'; const g = new Graphic ({ geometry : new Point({ // type : 'point' , // autocasts as new Point() longitude : - 71.2643 , latitude : 42.0909 }), symbol : new SimpleMarkerSymbol( { // type : 'simple-line', size : '12px' , color : 'blue' , outline : { color : '#efefef' , width : '1.5px' } })});   On your second issue, with the graphic not showing up that may be related to an issue that's fixed in 4.19, which is coming out in a few weeks. Try upgrading to the "next" version: https://github.com/Esri/feedback-js-api-next.  How you are using the JS API (e.g. esri-loader, arcgis-webpack-plugin, ES modules)? I can provide an example of how to do that. ... View more