I’ll post more info about this later if i need to. I believe this issue will ultimately go away in production but the way I’m developing my app it exists right now. I may be forced to change the way I’m developing. I have my aurelia application which i’m launching using the CLI’s au run. I have my dotnet core 2.1 web api application that I’m launching using dotnet run. Since both of these are running using their own port I needed to enable CORS. That is done with no issue. I have upload code that actually works.
The issue occurs on the aurelia/syncfusion end. When watching the network, I see my requests go out and they are returning 200s, but when watching the console, there is still a cors failure for some reason and that results in a rejected promise. The syncfusion control acts like the file upload actually failed.
The reason I say this should go away in production is because my aurelia application will be hosted on the same server as the API, but development was always meant to be standalone.