Create App Package not creating app package msixupload file

  • Thread starter Thread starter joshhunt1
  • Start date Start date
J

joshhunt1

Guest
I'm developing a UWP C# application using Visual Studio, for submission to the Microsoft Store. I've successfully submitted two versions, but I'm now having trouble building a new app package for submission.

I follow the Create App Package wizard, and it completes successfully, with no apparent errors in the build output. Except when I go to the folder the wizard says the package was created in, it either doesn't exist or it is empty.

The steps I follow in the Create App Packages wizard are:

  • How will you distribute this application: Microsoft Store as MyAppName by MyPublisherName
  • Output location is set to a known location, C:\Users\josh\dev\GhostOverlay\GhostOverlay\AppPackages\
  • Version automatically increments
  • Generate app bundle: Always
  • Packages top create and the solution configuration mappings:
    • x89: Release (x86)
    • x64: Release (x64)
    • none of the other architectures are selected
  • I include public symbol files
  • I do not Generate articats to validate the app with the Windows App Certification Kit

This was working before, and then "all of a sudden" it stopped working, and I'm unsure what I did to cause this. I've tried creating a new solution+project and copying the files across, but the issue still occured. I've cleaned the project and solution countless times, deleted the bin and obj folders, I've also tried reinstalling Visual Studio, but the issue still persists.

If I create a new solution+project, and don't copy code across, it is able to package successfully

I can provide the detailed build output (I've uploaded it to gist.github.com, but I'm unable to link to currently), which im not really able to get much useful information from. One thing I noticed is that BuildAppxUploadPackageForUap appears to be set to false? But im unsure why

My project is available on Github github.com/joshhunt/GhostOverlay

I'm completely at a loss for what's causing this, and I've ran out of things to do to try and troubleshoot

Continue reading...
 
Back
Top