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.

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

[CoE Starter Kit - BUG] Compliance Center error "does not have an AppPackage" #9215

Closed
1 task done
MartinWGT opened this issue Nov 4, 2024 · 3 comments
Closed
1 task done
Assignees
Labels
bug Something isn't working coe-starter-kit CoE Starter Kit issues

Comments

@MartinWGT
Copy link

Does this bug already exist in our backlog?

  • I have checked and confirm this is a new bug.

Describe the issue

Started getting an error when opening the Developer Compliance Center. The app cannot be used. This is for all users including the service account that owns the app.
The error points at the 'Developer Compliance Center Canvas App page'.

Error Code: AppMetadataParserFailed

AppLogicalName admin_developercompliancecenterapppage_775de does not have an AppPackage
UciError: AppLogicalName admin_developercompliancecenterapppage_775de does not have an AppPackage at s (https://xxxx.crm11.dynamics.com/uclient/scripts/app.js?v=1.4.9334-2410.2:33:976836) at https://xxxx.crm11.dynamics.com/uclient/scripts/custompage.js?v=1.4.9334-2410.2:4:23193

However, our developer environment works ok.

Image

Expected Behavior

The app should open without any errors.

What solution are you experiencing the issue with?

Governance

What solution version are you using?

3.25 (September 2024)

What app or flow are you having the issue with?

Developer Compliance Center

What method are you using to get inventory and telemetry?

Cloud flows

Steps To Reproduce

Open the Developer Compliance Center app.

Anything else?

No response

@MartinWGT MartinWGT added bug Something isn't working coe-starter-kit CoE Starter Kit issues labels Nov 4, 2024
@Jenefer-Monroe
Copy link
Collaborator

Hello, other users hit this as well. It was some bug in the upgrade process. Please see #9056
They fixed it by doing a classic overwrite re-install. Please see #9056 (comment)

@MartinWGT
Copy link
Author

Thanks Jenefer, I will try that.

@MartinWGT
Copy link
Author

Redploying the Governance solution using the classic method has worked, thank you. #9056

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working coe-starter-kit CoE Starter Kit issues
Projects
Status: Done
Development

No branches or pull requests

2 participants