Using Visual Studio 2019 to publish an update to an existing windows store application. This worked a week ago.
Our solution builds without error. When I go to create the setup package I get an error "Failed to sign 'D:\dev\MeyerMusic\MeyerTablet\TabletDistribution\bin\AnyCPU\Release\MeyerMusicTabletSetup_2.6.6.0_AnyCPU.msix'."
We are distributing the application as a Microsoft Store app under the existing app name.
Last week on this same development computer I built version 2.6.5 as well as many packages before that.
The error number is blank or missing. I do not have a reason for the failure. I only see one fact in the error message and that points to line 4574 in the file: C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Microsoft\VisualStudio\v16.0\AppxPackage\Microsoft.AppXPackage.Targets
That line is this:
<SignAppxPackage Condition="'$(AppxPackageSigningEnabled)' == 'true'"
AppxPackageToSign="$(AppxMainPackageOutput)"
CertificateThumbprint="$(PackageCertificateThumbprint)"
CertificateFile="$(PackageCertificateKeyFile)"
CertificatePassword="$(PackageCertificatePassword)"
HashAlgorithmId="$(AppxHashAlgorithmId)"
EnableSigningChecks="$(EnableSigningChecks)"
SignAppxPackageExeFullPath="$(SignAppxPackageExeFullPath)"
TempCertificateFilePath="$(TempCertificateFilePath)"
VsTelemetrySession="$(VsTelemetrySession)"
SigningTimestampServerUrl="$(AppxPackageSigningTimestampServerUrl)"
SigningTimestampDigestAlgorithm="$(AppxPackageSigningTimestampDigestAlgorithm)"
/>
Troubleshooting steps:
Attempted to build a side load package. Results in same error
Successfully built a side load package that was not signed
I have restarted Visual Studio
I have rebooted the machine
I have deleted OBJ, BIN for the entire solution
I have looked for errors in the event log but none have been found so far.
After uninstalling KB4535996 the problem was resolved.
I found this via a tip from the following post: https://developercommunity.visualstudio.com/content/problem/934967/uwp-error-failed-to-sign.html
I see below error while packaging appium project for AWS.
Unknown lifecycle phase --DskipTests=true. You must specify a valid lifecycle phase or a goal in the format
Note:
Executing packaging command on mac terminal
Tried both --DskipTests=true & -DskipTests=true (see same error for both)
Looking forward for some help. Thanks!
I work for the AWS Device Farm team.
I have seen this error when users copy-paste the command from the documentation.
We are working on updating this as there seems to be some unknown characters that get introduced.
Users have got this to work by deleting -DskipTests=true and typing it instead of copy pasting it.
Since you are on a Mac terminal you will need to use a single dash '-' for the parameter.
Apologies for the inconvenience.
Hope this helps.
I have a new empty MVC 5 project, and I try to install Nuget packages.
When I insert in the Nuget Console the command :Update-Package I got the following asnwer:
File E:\WebApp\packages\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.1.0.0\tools\uninstall.ps1 cannot be loaded because running scripts is
disabled on this system. For more information, see about_Execution_Policies at http://go.microsoft.com/fwlink/?LinkID=135170.At line:1 char:3
+ & 'E:\WebApp\packages\Microsoft.CodeDom.Providers.Dot ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : SecurityError: (:) [], PSSecurityException
+ FullyQualifiedErrorId : UnauthorizedAccess
then I start to install some new packages and got again this message:
WebApp\packages\Modernizr.2.8.3\tools\install.ps1 cannot be loaded because running scripts is disabled on this system
I saw some posts related with this message, but not related with MVC projects.
My question is:
Why I get those messages?
What can I do to fix this issue?
This issue, can appear on the server where my application will run? Some scripts to not run as expected?
I guess the specific package you are trying to install needs to run a Powershell script and for some reason, Powershell execution is disabled on your machine.
You can search google on "how to enable Powershell" for a complete guide but generally, it goes like this:
Open up a Powershell command window (just search for Powershell after pressing windows start button)
Check out current restrictions by typing Get-ExecutionPolicy
Enable PowerShell by typing Set-ExecutionPolicy remotesigned
This issue does not affect the server you are planing to install your application on.
If you encounter this installing NuGet packages from Visual Studio Package Manager Console, run Visual Studio as Administrator.
In case anybody finds this on Google and this happened to you, I suggest you first try restarting Visual Studio, particularly if the Package Manager Console has worked for you before. In VS 2019, I've noticed that, if I leave it in the background while it's loading, sometimes it'll throw that error.
For me, restarting Visual Studio and leaving it in the foreground until the Package Manager Console finished initializing solved the issue. Note that running it as administrator was not necessary.
Translation of the image text would be somewhat: This certificate has been revoked from its key store.
Certificate on my init.ps1 has expired - thus RemoteSigned will not do. For that package version to work, it would need to be set to ByPass or Unrestricted. Personally, i would not recommend doing this...
-- EDIT --
I went ahead and updated the package and found they have resigned a new cert for v 1.0.2. Issue following in NuGet console for fix:
Update-Package Microsoft.CodeDom.Providers.DotNetCompilerPlatform
open your power-shell as administration and type
Get-ExecutionPolicy
Expected result RemoteSigned
Set-ExecutionPolicy remotesigned
if it does not work, try Powershell run in administrator
I ran into a similar issue building a project and found that you MAY have to set the execution policy to remoteSigned (as others have mentioned) in BOTH powershell (x86) and powershell (x64). I was running the x64 version as administrator and Get-ExecutionPolicy returned "remoteSigned" but the x86 version hadn't been updated. Just something to try if the above answers don't work for you.
This should work
open your power-shell as administration and type
Get-ExecutionPolicy
Expected result RemoteSigned
Set-ExecutionPolicy remotesigned
Enjoy
A quick to fix this error when using Package Manager Console without VS restart and/or running as Admin is to remove the restriction for current user:
Set-ExecutionPolicy remotesigned -scope CurrentUser
After i figured out how to build the Demo Project "Upsell Management" (project), i'm struggling now with the installation in the sandbox.
I'm running a sandbox with POA 5.5-5562_update06-824 and every time i try to install it i get a Status "Validation Error":
http://i.imgur.com/2v6GEJc.png
So, is there a log file or anything to find out what is the error behind that?
'Validation error' means that package import task has failed, more details on this can be found in Operations->Tasks
If you see a validation error that you did not see while running apsbuild/apslint tool this means that either you or POA have an older version of apstools.
The best way is redeploy sandbox to latest POA version and update APS tools on your build machine (http://doc.apsstandard.org/2.1/tools/cli-tools/#cli-tools)
I tried to install ejabberd 2.1.11 for windows on my Windows system, but at the final stage of installation it given post installation error. Couple of some of the last lines in the intallation logs says:
***Executing final installation script
Error executing post installation script
C:\Program Files (x86)\ejabberd-2.1.11\bin\postinstall.cmd
./ejabberdctl: erl.exe: can't execute: (14001) Error 14001
Creating Uninstalle***r
Though the shortcuts are created on the system but trying to start the server gives following error
./ejabberdctl: erl.exe: can't execute: (14001) Error 14001
The VC++ 2008 is already installed on the system. While searching I found the following post on stackoverflow:
How to install ejabberd community version on Windows XP?
But this too did not help. Has anyone else encountered the same scenario? Your suggestion would be greatly appreciated.