Forum Discussion
MSIX Packaging Tool 2023.118 Font issue
The new version of the Packaging tool is creating an invalid package for this situation. This did not happen in 2022.1101.
The application is the same "LotsOfFonts" app that I provided when p...
Thanks for the response. I'm not sure which version I originally shared, so I tried packaging a different version, and obtained the same issue, but with a different font in the package.
In the installation, there are two font files:
AlphaFridgeMagnets .ttf
AlphaFridgeMagnetsAllCap.ttf
In the package VFS\Fonts folder is only one (renamed)
AlphaFridgeMagnets20
And based on the size this seems to be the one with the space in the name.
In the AppXManifest, there are two font entries:
VFS\Fonts\AlphaFridgeMagnets20.ttf
VFS\Fonts\AlphaFridgeMagnetsAllCap.ttf
Looking at the log file area from the MMPT, the ingredients only contains the one file, and the log file shows processing the one file as well. So I would assume the problem occurs in the period between end of capture and creation of the ingredients file, which is the renaming of invalid characters were taking place.
Oddly, while the MakeMsix command cannot create a package with those missing files that are referenced (it fails on AppXManifest validation), the MakeAppX used in the MMPT does not seem to mind.
I have a tool that detects and fixes the package for the missing files, so I'm not all that concerned about this issue, but there does seem to be an issue with that code.
This isn't a huge deal to me as my tooling catches the missing entries
In the installation, there are two font files:
AlphaFridgeMagnets .ttf
AlphaFridgeMagnetsAllCap.ttf
In the package VFS\Fonts folder is only one (renamed)
AlphaFridgeMagnets20
And based on the size this seems to be the one with the space in the name.
In the AppXManifest, there are two font entries:
VFS\Fonts\AlphaFridgeMagnets20.ttf
VFS\Fonts\AlphaFridgeMagnetsAllCap.ttf
Looking at the log file area from the MMPT, the ingredients only contains the one file, and the log file shows processing the one file as well. So I would assume the problem occurs in the period between end of capture and creation of the ingredients file, which is the renaming of invalid characters were taking place.
Oddly, while the MakeMsix command cannot create a package with those missing files that are referenced (it fails on AppXManifest validation), the MakeAppX used in the MMPT does not seem to mind.
I have a tool that detects and fixes the package for the missing files, so I'm not all that concerned about this issue, but there does seem to be an issue with that code.
This isn't a huge deal to me as my tooling catches the missing entries
Hi,
We have tested this. Both the fonts you have mentioned are present in the Appx Manifest and Package Files and are installed with the msix package as expected.
Ensure you are :
1. Using the latest build of Msix Packaging Tool available in Microsoft store.
2. Converting the application to .msix using MPT in a clean environment.