Application not crashing if a resource string is incorrect in XAML

[asi-evin]

Description

if there is an error with a resource string in XAML, the app will run fine while debugging. However, when you try to run the app without the debugger, it will crash.

Ideally, the application should not compile or at least crash in debug; it's VERY frusterating to try and find the error without the debugger.

Recording.2024-01-19.145412.compressed.mp4

I've noticed this issue on "StaticResource" strings, "Translation" strings and other custom Provider extension strings. There could be other XAML issues that compile and run successfully in debug, but it's difficult to ascertain.

This COULD be related to Hot Reload, I haven't tried without it. I also have only tested Android Emulator, Physcal Android Device, and Physical iOS Device (both remote and local).

Steps to Reproduce

1. Create a new MAUI project

2. Add a BackgroundColor to the button, or some other element using a Static Resource that does not exist (e.g.
   <Button BackgroundColor="{StaticResource blooper}"/><!-- static resource that does not exist -->)

3. Run the Project in Debug

Expected Result: App should crash or not compile

Actual Result: App runs as if everything is hunky-dory

Further issues: App crashes when run without the debugger

Link to public reproduction project repository

No link required, can be replicated with a fresh project very easily.

Version with bug

8.0.6

Is this a regression from previous behavior?

Yes, this used to work in Xamarin.Forms

Last version that worked well

Unknown/Other

Affected platforms

iOS, Android

Affected platform versions

No response

Did you find any workaround?

Windows properly throws an exception during runtime, and will even tell you the position in xaml of the error. If possible, maintain windows as a viable platform, even if your app is mobile only.

Relevant log output

No response

[mattleibow]

Are there no warnings in the debug output window? I know we do log a lot. @StephaneDelcroix are we missing some logging for something? I am sure I have seen warings about invalid bindings and things.

[asi-evin]

@mattleibow I don't think it should matter. I'd hope if I accidentally typed a resource string wrong, I wouldn't need to slog through the output, especially since I may not know about the error for quite some time; I do a lot more debug runs than non-debug runs. But in the interest of clarity, below is the output with a local iOS device. I did a quick search for things such as "NonBlack" or "StaticResource" and didn't find anything.

ios log.txt

Edit: also did a search for "error" and "warning" and came up empty.

[asi-evin]

Got a chance to test with windows this morning, and it does properly throw an exception with a helpful message:

Position 33:17. StaticResource not found for key NonBlack

Still needs to be fixed for Android and iOS though (and presumably MacCatalyst). Difficult in my large project to do that, it's a mobile-only app, but I guess I have to get it running on windows now...

[asi-evin]

Just an FYI, I did have instances where windows did not crash or fail to compile when the debugger/hot reload was running. I couldn't re-create these behaviours in a small repro though.

I now have libraries that only work on the mobile platforms as well, so relying on windows to find XAML mistakes for me is simply no longer an option.

[QianaJiao]

Can repro this issue on the latest 17.10 preview 2 (8.0.14).
Build and Debug can succeed without error, and starting without debug will crash.