-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[Android] AddEmbeddedResourceFont Shows Exception Warning in Output Window #24059
Comments
Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! Open similar issues:
Closed similar issues:
|
I can repro this issue at Android platform on the latest 17.11.0 Preview 6.0 (8.0.71 & 8.0.70). |
Also here to confirm the issue on the latest MAUI, compiled against |
When debugging the provided MauiSampleApplication solution on Android, I also see output messages about the fonts (not just Messages in the output window: But the app just runs and shows the correct fonts. My issue is, that we are using a 3rd party control (via a nuget package) that uses an embedded font. So our issue is: using a nuget package that contains an embedded font crashes the release version of the app on some Android devices. |
Please provide a high priority for the resolution of this issue. Relevant issue: #19804 |
Description
Description:
When registering a custom font as an embedded resource in a MAUI project, the following error appears in the output window when deploying on Android:
Reference sample:
MauiSampleApplication.zip
Steps to Reproduce
Link to public reproduction project repository
No response
Version with bug
8.0.71 SR7.1
Is this a regression from previous behavior?
Not sure, did not test other versions
Last version that worked well
Unknown/Other
Affected platforms
Android
Affected platform versions
No response
Did you find any workaround?
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: