-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NitroPDFIncNitroPDFPtyLtd version 5.1.0.2 #14551
NitroPDFIncNitroPDFPtyLtd version 5.1.0.2 #14551
Conversation
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hello @sanikdah, Please investigate a fix and resubmit the Pull Request. You may also try using the Windows Package Manager Manifest Creator. |
Don't use comma (,) in name |
Huh, is there any info on why it didn't install without user input? It did when I was testing it locally. |
The |
Alright, I'll see if I can deal with that tomorrow, its already past midnight for me and I have to go to bed once I get this last piece of software up. |
Alright so now let me deal with the commas in the name and files. |
Can you show me how to make the URL not expire? I tried just getting rid of the ?Expires=1622391378 part and that without the ? and still didnt work. |
ok nevermind I found one that won't expire |
alright and the sha256 matches |
…ml to NitroPDFIncNitroPDFPtyLtd.installer.yaml
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hello @sanikdah, Please verify the manifest file is compliant with the package manager 1.0 manifest specification. You could also try our Windows Package Manager Manifest Creator Preview. For details on the specific error, see the details link below in the build pipeline. |
I'm just gonna remake it this is such a pain to edit. |
winget validate --manifest <path>
?winget install --manifest <path>
?Note:
<path>
is the name of the directory containing the manifest you're submitting.Microsoft Reviewers: Open in CodeFlow