Quick Pad 5.2.0

[yaira2]

• Have you signed the Contributor License Agreement?
• Have you checked that there aren't other open pull requests for the same manifest update/change?
• Have you validated your manifest locally with winget validate <manifest>, where <manifest> is the name of the manifest you're submitting?
• Have you tested your manifest locally with winget install -m <manifest>?

---

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ghost]

This submission has moved to manual review.

[KevinLaMS]

Clean up image

[ghost]

Greetings. This package fails because it is dependent on some frameworks, and we do not support the dependencies yet. See issue: microsoft/winget-cli#163
In the meantime, if you include the dependencies in your package, it should pass.

[yaira2]

@KevinLaMS Being that WinGet will support installing apps from the store, I don't think it's worth investing so much for this package right now. Is there a process to remove an app from WinGet or do I just need to delete the folder for it?

[KevinLaMS]

I think what we should do is keep this PR active as active so that once dependencies are done, we can add this if we want.
I agree, the 404 error we get with the current package is not good. It would be great if you want to put through the RM for that package.

[yaira2]

I think what we should do is keep this PR active as active so that once dependencies are done, we can add this if we want.
I agree, the 404 error we get with the current package is not good. It would be great if you want to put through the RM for that package.

I removed the outdated package for Quick Pad over here #5627.

[vedantmgoyal9]

@denelon @KevinLaMS This PR can be closed as the version of the manifest being used is 0.1.0.

[yaira2]

@denelon @KevinLaMS This PR can be closed as the version of the manifest being used is 0.1.0.

How can that be resolved?

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ghost]

Hello @yaichenbaum,
The package manager bot determined that the metadata was not compliant.

Please verify the manifest file is compliant with the package manager 1.0 manifest specification.
Make sure the ID is of the form publisher.appname and that the folder structure is manifests\partition\publisher\appname\version.
Note: The path and "PackageIdentifier" are case sensitive.
Be sure to use a tool like VSCode (https://code.visualstudio.com/) to make sure the manifest YAML syntax is correct.

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.

[ghost]

Hello @yaichenbaum,
This pull request has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 7 days of this comment.

[yaira2]

@vedantmgoyal2009 I'm not sure why this isn't working, any ideas?

[quhxl]

The folder should be manifests\q\QuickPad\QuickPad\5.2.0 and not manifests\QuickPad\QuickPad\5.2.0

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[arjun-msft]

@yaichenbaum this appears to be a paid app, after I install it and run it, it is blocked and takes me to the store. We are unable to install paid apps at the moment, I believe we are blocked on this: microsoft/winget-cli#908.