Merge failure due to wrong PRI file about wsapackagingtool HOT 3 OPEN

Weird enough, it allows me to install the msix by itself.

Since it seems that the current version is region-locked to the US or something, I had to download an old version (Android 11) from a link given by Microsoft that's not region-locked, but this one presented a different issue: once I replace the temp files with the output from the GApps integration script (using OpenGApps, as I can't find any MindTheGApps compiled for Android 11 in x86_64 systems, and the more modern versions are not backwards compatibe), the repack script succeeds in creating the msix files, but fails in creating the msixbundle from them, returning a generic error about wrong manifest. Once again, the msix by itself installs without issue and the app runs, so I don't know why the bundle cannot be created.

from wsapackagingtool.

Weird enough, it allows me to install the msix by itself.

Since it seems that the current version is region-locked to the US or something, I had to download an old version (Android 11) from a link given by Microsoft that's not region-locked, but this one presented a different issue: once I replace the temp files with the output from the GApps integration script (using OpenGApps, as I can't find any MindTheGApps compiled for Android 11 in x86_64 systems, and the more modern versions are not backwards compatibe), the repack script succeeds in creating the msix files, but fails in creating the msixbundle from them, returning a generic error about wrong manifest. Once again, the msix by itself installs without issue and the app runs, so I don't know why the bundle cannot be created.

You need to extract the original .msixbundle package by dragging it to unpack.cmd, then replace the IMAGE (starting from 2302 VHDX) files: system, system_ext, vendor, product with the same files from the build with gapps and assemble by double-clicking on repack.cmd

from wsapackagingtool.

So it's only the image files. Nice to know for when I need to update my GApps version.

I have found that, somehow, contrary to what I've been told, upgrading the app doesn't mess with my custom installation; Play Store does break, but that's only due to the autoupdate function that tries to replace the open-source GApps with the official app, but any app that depends on Play Services (and by extension, Google Play Services) stills works.

Given that the newer versions of WSA do not work for me, I need to force downgrade it every time it updates itself using a clean msixbundle, and yet I've haven't found any new issues I did not with manual patched updates.

from wsapackagingtool.