Several issues loading resources in MAUI (Windows)

[mdmontesinos]

I've been testing to use MAUI with my current web, but I'm encountering some issues:

First of all, some static resources are getting blocked by CORS policy but others are not, which is weird. For example:

Also, fonts that are imported within the bootstrap scss file are also blocked by CORS:

/* roboto-condensed-900 - latin */
@font-face {
    font-display: $font-display;
    font-family: 'Roboto Condensed';
    font-style: normal;
    font-weight: 900;
    src: url('../../fonts/roboto-condensed-v27-latin-900.woff2') format('woff2'), /* Chrome 36+, Opera 23+, Firefox 39+, Safari 12+, iOS 10+ */
    url('../../fonts/roboto-condensed-v27-latin-900.ttf') format('truetype'); /* Chrome 4+, Firefox 3.5+, IE 9+, Safari 3.1+, iOS 4.2+, Android Browser 2.2+ */
}

But not even all of them, only some, which is again weird:

Finally, images that are loaded with the "/files" server don't work at all because MAUI tries to request them as a local resource instead of the server:

Any clues on how to solve these issues?

P.S: I've set the ApiUrl in the MauiConstants, and I'm using the Oqtane version that sets the 0.0.0.1 origin in the CORS policy. Tested on Windows Machine, not Android.

[sbwalker]

I raised the challenges with static resources to Microsoft more than 2 years ago:

dotnet/maui#10898

And it has still not been resolved.

[mdmontesinos]

@sbwalker The issue you created relates more to the last issue I mentioned about the "/files" server being requested locally.

In the post you mentioned the GetAssetUrl() suggestion is exactly what I am doing in Oqtane already... but it feels like the wrong approach to treat this as a development concern (by forcing it to be implemented in the code itself) rather than a hosting model concern, can you point out where this logic is located so that I revise it and perhaps replicate it for all my images requests?

Apart from that, the CORS errors are different, because the assets are correctly being requested from the server not locally, but still failing.

Anyway, it's a shame that MAUI still presents these serious flaws and that Microsoft does not seem really that interested.