Skip to content
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.

Sign up for GitHub

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

Jump to bottom

PA3999: Could not find ComponentManifest #485

Open
1 task
robertobudelo-armacell opened this issue Jul 18, 2023 · 14 comments
Open
1 task

PA3999: Could not find ComponentManifest #485

robertobudelo-armacell opened this issue Jul 18, 2023 · 14 comments
Assignees
@landonmsft
Labels
bug Something isn't working

Comments

@robertobudelo-armacell
Copy link

robertobudelo-armacell commented Jul 18, 2023 •
edited by landonmsft
Loading

  • Please attach a sample .msapp to this Issue which demonstrates the issue you are experiencing. (Please do not attach any file which may contain sensitive personal or company data.)
    Can attach the msapp on request

Describe the bug

Power Platform Build Tools on Azure DevOps (2.0.29)

Error: Error   PA3999: Could not find ComponentManifest for 
Error   PA3011: Roundtrip validation on unpack failed. 
You have found a bug; this is not a specific bug, rather an indicator that some bug has been encountered.
Please open an issue and log the entirety of this error log at https://github.com/microsoft/PowerApps-Language-Tooling

To Reproduce

PowerPlatformUnpackSolution

Screenshots

If applicable, add screenshots of error messages to help explain your problem.

Additional context

.msapp created on Dataverse for Teams
@robertobudelo-armacell robertobudelo-armacell added the new An Issue created that needs to be looked at by the team label Jul 18, 2023
@tomjschneider
Copy link
Contributor

Hey @robertobudelo-armacell , would you mind sharing your sample .msapp with me? You can email it to paadvmakers AT microsoft DOT com

@tomjschneider
Copy link
Contributor

Hey @robertobudelo-armacell, just wanted to check back and see if you could share an .msapp where you experience this issue with the email address above?

@robertobudelo-armacell
Copy link
Author

robertobudelo-armacell commented Jul 26, 2023 via email

@robertobudelo-armacell
Copy link
Author

robertobudelo-armacell commented Jul 26, 2023 via email

@tomjschneider
Copy link
Contributor

@robertobudelo-armacell That is a link to your personal SharePoint, which requires authentication. Could you attach the .msapp directly? Thank you.

@robertobudelo-armacell
Copy link
Author

robertobudelo-armacell commented Jul 26, 2023 via email

@tomjschneider
Copy link
Contributor

Not sure why, but I am not receiving your email at that address. Could you send to tschneider AT microsoft DOT com? Apologies for the confusion.

@robertobudelo-armacell
Copy link
Author

robertobudelo-armacell commented Jul 26, 2023 via email

@robertobudelo-armacell
Copy link
Author

robertobudelo-armacell commented Jul 27, 2023 via email

@tomjschneider
Copy link
Contributor

@robertobudelo-armacell It did, thanks! I'll get this app in front of the team so we can take a look.

@landonmsft landonmsft added bug Something isn't working and removed new An Issue created that needs to be looked at by the team labels Aug 3, 2023
@landonmsft landonmsft self-assigned this Aug 9, 2023
@buckthebug
Copy link

Hi, we are facing the same. Did you solve that?

@spplante
Copy link

spplante commented Jan 25, 2024 •
edited
Loading

Same issue here, it works without the "Process Canvas Apps" option checked, which explodes the .msapp into real source YAML files. If you uncheck this option the unpack task runs fine, if you check it, it fails.

Note that the option is still marked as "Preview", but it was previously working without a problem.

@Sharukh-maker
Copy link

How to fix this error [PA3999: Could not find ComponentManifest

@LiDengHui
Copy link

We also encountered PA3999, we found that there is a custom component named the same name as other default components, "button", then we deleted the component, the program is normal, then we tried to rename "radio", there is the same problem, so presumably it is a renaming problem. Then we tried to rename "radio" and had the same problem, so we assumed it was a renaming issue, hope this helps!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@landonmsft landonmsft

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@LiDengHui @spplante @buckthebug @Sharukh-maker @tomjschneider @landonmsft @robertobudelo-armacell