WebView unable to access Embedded Resources from a NuGet Package in .NET MAUI

[aks14621]

Hi everyone,

I have a .NET MAUI app that references a class library containing embedded resources (fonts and HTML files). When the library is added as a project reference, everything works fine, fonts register correctly, and HTML content loads in a WebView.

However, when the same library is consumed as a NuGet package, the resources are not found at runtime. The app fails to locate fonts and HTML files from the external assembly.

I suspect this relates to how .NET MAUI or the platform build pipelines handle resource resolution across assemblies. Before implementing a workaround (like moving resources into the main app), I’d like to confirm the expected behavior.

Question

• Is it supported for a .NET MAUI app to access embedded resources (fonts, HTML, etc.) from a referenced NuGet package?
• If not, what’s the recommended approach to make these resources available at runtime (e.g., for WebView or font registration)?

Additional Details

• MAUI Version: [ .NET 9]
• Platforms: Android, iOS, Windows
• Resources are marked as EmbeddedResource in the library’s .csproj.
• Fonts register normally in MauiProgram.cs when using project references.
• Issue only occurs when using a NuGet package.

Goal

We want to know if cross-assembly resource access is supported or if resources must reside in the app’s assembly. Guidance from Microsoft or the community will help us decide whether to restructure our shared resource approach.

[ghost]

@aks14621 I think your NuGet does not include the Font, the same way you manually include them in MAUI. CoPilot says something about this:

1. Package assets so the app build includes them
   In the library/nupkg, include your fonts and HTML as MAUI assets or contentFiles and ensure the package provides build targets to mark them with the correct build action in the consuming project.

However, I only included NuGet that includes a file, that a specific content type is set, so the MAUI does include it in the build process. How it is done in the NuGet I do not know. Maybe this does help you a bit, to get started in the right direction.