Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Icon Fonts not showing up in Unpackaged Windows Deployment #79

Open
KaFo opened this issue Dec 15, 2023 · 10 comments
Open

Icon Fonts not showing up in Unpackaged Windows Deployment #79

KaFo opened this issue Dec 15, 2023 · 10 comments
Assignees
Labels
Area-External Bug Something isn't working

Comments

@KaFo
Copy link

KaFo commented Dec 15, 2023

Describe the bug
When using new .NET8 Unpackaged Windows Deployment the icon font is not included/applied in the published App. (MauiIcons 2.0). I haven't tested with MSIX deployment yet, so can't say if it works there.

I made simple example based on .NET8 Maui Hello World template. I only replaced the dot net bot image with a Mood Material Icon.

See code in GitHub Repo (MauiIcon branch)

or patch against base template here:
MauiIconsInHelloWorldMaui.patch

This is how it looks like
from IDE: OK
image

published: NOT OK
image

@AathifMahir
Copy link
Owner

Thanks for reporting this issue, I'll try diagnosing this issue on Sample Application and Get Back to you

@AathifMahir
Copy link
Owner

@KaFo Also would you mind explaining the patch url? What is that file

Screenshot_20231215_144511_Chrome

@AathifMahir AathifMahir self-assigned this Dec 15, 2023
@AathifMahir AathifMahir added the Bug Something isn't working label Dec 15, 2023
@KaFo
Copy link
Author

KaFo commented Dec 15, 2023

Thanks for the ultra fast response (and thanks for the great package, much appreciated!)
The Patch just illustrates the changes I made to the hello world app. So basically the stuff you have to do to go from blank hello world to an app that reproduces the issue. You can ignore it if you reproduce yourself or use the github example branch I provided.

@AathifMahir
Copy link
Owner

@KaFo the issue seems to be related this issue
dotnet/maui#9104

Will investigate this further and come with a solution as soon as possible

@KaFo
Copy link
Author

KaFo commented Dec 22, 2023

Hi. Thank you for investigating this. Seems quite a few problems with maui development end up being bugs@microsoft... But at least they gave it prio "p/1". Which means "Work that is critical for release but we can probably ship without". Hargh Hargh. :-)

@LukasKStavario
Copy link

Hi I have same problem here, any solution?

@AathifMahir
Copy link
Owner

Hi I have same problem here, any solution?

We are waiting for fix on Maui Side, as far as now, I'm not aware of any workarounds

@AathifMahir
Copy link
Owner

Hello Folks,

Update on this issue, This issue is finally Fixed with Win2D v1.2.0, we can expect to Maui to update the Win2D Dependency to v1.2.0 upcoming service releases. Once that's done, we can finally close this issue

@jeremy-visionaid
Copy link

AFAIK, the upstream issue was fixed months ago in Maui. I haven't tried the project myself, but at a quick glance it looks like MauiVersion here has been left at its default, so its value would be defined by the toolchain (currently Maui 8.0.21 assuming VS 17.10.1), currently latest Maui is 8.0.40. But the Win2D dependency could also be bumped explicitly with a PackageReference (if you're targetting 8.0.10 or later).

@FireController1847
Copy link

Is there a workaround / solution for using this library on an unpackaged app as of the current state? I noticed this issue referenced recently but the context doesn't make much sense given what I'm able to read. What is the current status of this issue in this regard?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-External Bug Something isn't working
Projects
Status: No status
Development

No branches or pull requests

5 participants