SignTool Error: Invalid option: /fd - vb.net

I publish my exe and activate auto updates.
But when I compile the exe, there is an error:
Severity Code Description Project File Line Suppression State Error An
error occurred while signing: Failed to sign
bin\Debug\app.publish\myapp.exe. SignTool Error: Invalid option: /fd
So I couldn't publish.
When I try to uncheck "Sign the ClickOnce manifest" the error is gone
but I couldn't install the package because Windows doesn't allow and the Windows Defender SmartScreen blocks my app because there's no certificate.
I have to add a certificate from "Sign the ClickOnce manifest" but now it gives the "SignTool Error: Invalid option: /fd" error.
How can I solve this problem?

I had to change the Signature Algorithm to sha1RSA from sha256RSA

I did just the opposite as Stefano - changed it from sha256RSA to sha1RSA - and then it allowed me to publish without the error.
Just changing the signature algorithm may do the trick.

I encountered the same error message when migrating an old ClickOnce project from VS2018 to VS2017. It seems my VS2018 was using an old version of SignTool.
I found (and succeeded with) a tip to change registry key HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Microsoft SDKs\Windows to make Windows to use newer SDK (in my situation SDK v8.1A was the most recent).
The original tip can be found here: https://social.msdn.microsoft.com/Forums/en-US/a39b9f82-aaec-4bbd-8cb2-3cade50796ba/an-error-occurred-while-signing-failed-to-sign-bindebugapppublishprogramexe-signtool-error (scroll down to answer by nikidimi)

Go to the myapp.csproj file, which is the project file, and search for 'SignManifests' PropertyGroup, change the value to false, and the error disappears. This worked for me.

Related

Unable to find package 'Swashbuckle.AspNetCore.SwaggerUI.6.2.3'

I'm using swagger, but I have this problem according to the documentation. The nuget package has not been downloaded successfully. What should I do?
This is the error message:
Severity Code Description Project File Line Suppression State Error
The feed'nuget.org [https://api.nuget.org/v3/index.json]' lists
package'Swashbuckle.AspNetCore.SwaggerUI.6.2.3' but multiple attempts
to download the nupkg have failed. The feed is either invalid or
required packages were removed while the current operation was in
progress. Verify the package exists on the feed and try again. Unable
to find package'Swashbuckle.AspNetCore.SwaggerUI.6.2.3'.
Update:
I try to use the command:Install-Package Swashbuckle.AspNetCore -Version 6.2.3
Error:
Maybe a problem on your internet connection? Package seems exist (https://www.nuget.org/packages/Swashbuckle.AspNetCore.SwaggerUI/6.2.3).

Cannot add a new app to fabric

I am unable to add a new iOS app to fabric by following the instructions of the Fabric macOS plug in.
I have followed all of the instructions found at Crashlytics documentation
When running the app, I receive this error:
2018-03-12 14:22:24.090838-0400 [19139:8550117] [Crashlytics] Version 3.10.1 (129)
2018-03-12 14:22:24.636050-0400 [19139:8550293] [Fabric] unable to complete application configure: Error Domain=FABNetworkError Code=-5 "(null)" UserInfo={status_code=422, type=2, request_id=fbc432572e6f0e10f21d2ddc24c7f272, content_type=text/html; charset=utf-8}
I have tried searching StackOverflow and following answers, but no luck avoiding this error message.
Any ideas on this error message?
I had this problem and discovered that my 'visible' (in Xcode) info.plist was not a file in my root directory, and was an out of date version from earlier development activity. I am not sure why my correct/current info.plist did not display in Xcode. I found the current info.plist in Finder (it was in the root directory in Finder, just not appearing in Xcode). I dragged the file from Finder to Xcode and accepted all the defaults in the dialog that appeared. Then I simply built and ran the current scheme and all worked as it should.
Note: It appears that for some time I have been updating the 'invisible' info.plist directly from my apps Target / Info tab.
Make sure to include all dependency then throw a force crash or runtime error and do not forget to turn on your data or internet connection.

Flash Builder - Platform conversion failed error during release build

This is a very annoying problem while generating release build files. Here is the steps I did while building:
Select Project > Export Release Build
Select Signed Native Installer
Import certificate
Click Next.
I always got the following error:
https://forums.adobe.com/servlet/JiveServlet/showImage/2-6524012-651585/build_error.png
Platform conversion failed. Process exited with error 5. Output was
"[ErrorEvent type="error" bubbles=false cancelable=false eventPhase=2
text="Unhandled exception Error: EndUpdateResource: Windows Error #5"
errorID=0]
I have the following setup:
OS: Windows 8.1
System type: 64-bit
Flash Builder Version: 4.6 Premium
Installed FB: FlashBuilder_4_6_LS10.exe
Please help. This is giving me a lot of headaches for a couple of days now.
Additionally, here's the stack trace:
java.io.IOException: Platform conversion failed. Process exited with
error 5. Output was "[ErrorEvent type="error" bubbles=false
cancelable=false eventPhase=2 text="Unhandled exception Error:
EndUpdateResource: Windows Error #5" errorID=0] " at
com.adobe.air.nai.NativePackager.conversionFail(NativePackager.java:222)
at
com.adobe.air.nai.NativePackager.invokePlatformConversion(NativePackager.java:203)
at
com.adobe.air.nai.NativePackager.createPackage(NativePackager.java:92)
at
com.adobe.flexbuilder.multisdk.apollo.export.AIRNativeInstallerPackager.create(AIRNativeI
nstallerPackager.java:129) at
com.adobe.flexbuilder.exportimport.releaseversion.ExportReleaseVersionManager.doExport(Ex
portReleaseVersionManager.java:586) at
com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportReleaseVersionWizard$1.run(Exp
ortReleaseVersionWizard.java:208)
I also suspect this is because of the following settings:
Eclipse.ini
https://forums.adobe.com/servlet/JiveServlet/showImage/2-6525217-651726/eclipse.png
...
-startup plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
--launcher_library plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.100.v20110502.jar
...
Notice that the plugin used is not intended for x64 processors.
#ActionScript3030 is correct, for anyone finding this later on, if you re-link your Library Paths (even if they look correct) this should rectify your issue.
The issue is caused by the links not being able to resolve to their GUID counterparts in your AppData/Local folder. This happens quite commonly when you create a new user profile and try to copy over your old user profiles information.
I already figured this out. I created a virtual machine with windows 7 32bit operating system and I'm happy now :)
If you initially created your project on a different system then try to compile it in another system, the class source and swc paths may not match. These paths could be there but not being implemented in code, so you will not get any run time errors while debugging, but it will give you the error 5 during compilation.
Solution:
Remove the idle paths not directly in use in your code. You can identify them by simply checking the path.
Found the same issue when trying to use Microsoft Essential Security on my Windows 7 x32. When i uinstall it - problem gone. So try to check your firewall settings if stucking the same problem.
Just to add an alternative solution (I'm on an x64 Windows and want to keep build exported for x64), in my case the error popped up when building the project with the AIR SDK defined in the app.xml (an older one, 3.9) and went away when I explicitly used a newer SDK (19).
(Disclaimer: I used the command line adt tool from the SDK to build, not Flash Builder).
A little late, but might possibly help someone.
I had the same error recently with FlashDevelop. Figured out that the my path was too long. When I renamed some long folder and file names, the error disappeared.
Try to disable UAC on Windows 8. Change it to "Never notify". The problem

Trying to debug custom FxCop rule fails because FxCopCmd can't load the assembly (CA0055)

I'm trying to debug a custom FxCop rule I wrote by following this FAQ: http://blogs.msdn.com/b/codeanalysis/archive/2007/05/16/faq-how-do-i-debug-a-custom-rule.aspx ("Debugging within Visual Studio or via command-line" section)
Initially I got some errors about missing references, but I managed to fix those by using the following command line:
FxCopCmd.exe /searchgac /d:"SomeDir" /file:"MyAssembly.dll" /rule:"MyCustomRules.dll" /console
Now, I'm getting the following error:
Project : error : CA0055 : Could not load MyAssembly.dll. Signature is not valid.
Project : error : CA0052 : No targets were selected.
I made sure that MyAssembly.dll is signed with my test signing certificate, and that all of the certificates in the certification path are in the "Trusted Root Certification Authorities" (of the current user) but it doesn't help.
Does anyone know what this error means?
Thanks!

installation of "mono for android" fails with "OSStatus error -67053" on Mountain Lion

I installed last night "Mountain Lion", which caused XCode to fail. When I installed a new XCode version, "Monotouch" and "Mono for android" disappeared...
I could reinstall monotouch quite fast, but I am unable to install "mono for android". After clicking on "Install MonoForAndroid" I get
"Der Vorgang konnte nicht abgeschlossen werden (OSstatus-Fehler -67053)", which means something like
"could not finish this, (OSstatus-error -67053)"
All I could find with google was [1] which says that this could mean "errSecCSResourceRulesInvalid".
Anyway, I still have no idea what to do now. Is someone here able to tell me what I can do to get Mono4Android running again? Thanks ALOT!!
[1] = https://developer.apple.com/library/mac/#documentation/Security/Reference/CodeSigningRef/Reference/reference.html
The error -67053 means:
invalid resource specification rule(s)
I found one way to resolve this error: Edit the file Info.plist inside the application bundle and remove the CFBundleResourceSpecification property.
In the settings is an option that you can only install apps from the Mac App Store. It seems that this option is turned on by default. To solve the problem you just need to turn it off.