I just updated to Windows 10 SDK 10.0.15063 and running into a problem creating app packages for the Windows Store. It seems to complete the x86 and x64 portion, but fails for the ARM portion:
Error: File 'C:\somepath\bin\ARM\Release\App_184.108.40.206_scale-100.appx' not found.
Using Visual Studio 2017 Community. Not even sure where to begin on how to fix this. Any thoughts?
This error does not show up when I pick "Never" for "Generate app bundle:" in the "Create App Packages" wizard, but I do want an app bundle to submit to the Store.
Added a solution by Daniel Jacobson (MSFT) · Apr 07 at 01:49 AM
We are working on a fix for this issue as quickly as we can, but we have identified a workaround for you. To workaround this issue, please take the following steps:
1. Download and extract storepackageworkaround.zip to any location
2. Close all instances of Visual Studio
3. Open the Developer Command Prompt for Visual Studio 2017 in Administrator mode
4. In the command prompt, navigate to the location where you extracted these files
5. Run Apply.cmd
This will update the file that introduces this issue. If you still encounter this issue or have problems with the script, please reply to this issue.
Daniel - Program Manager for Visual Studio
Added a solution by steve foxover · Apr 10 at 11:10 PM
Worked for me as well. It makes me a little nervous with this bug as well as the "[Inspector] Error preparing project for inspection: System.NullReferenceException: Object reference not set to an instance of an object." bug that just blows away your output window. Seems like QA should have caught these. I might need to test VS 2017 or at least the updates on a test machine for a bit before using it on my main DEV environment.
Added a solution by Visual Studio Team · Apr 17 at 05:42 PM
This issue has been fixed and is now available in our latest update. You can download the update via the in-product notification or from here: https://www.visualstudio.com Thanks to everyone who provided feedback, votes and solutions for this problem.
Added a solution by Allan Smith · Apr 11 at 05:53 PM
While this bug sure was a pain in the ass, I must say that having the workaround available so quickly, and also this medium to provide feedback, see the status of the fix, and optimistically getting the fix out in earnest... bravo MSFT. Thanks @Daniel Jacobson (MSFT)!
Intellisense false positive with #define
Visual Studio 2017 Update fails
Trouble while installing VS 2017 community
Typo in Default.rd.xml