Power Platform Community Forum Thread Details

All my custom pages are not loading. This started some time today, while I was editing one of the custom pages.

This seems like an environment issue, the custom pages in my other environments are fine.

Tried clearing cache, error still persists.

Anyone has experienced similar issues?

Error Code: AppMetadataParserFailed
Session Id: xxxxx
Activity Id: xxxx
Timestamp: Wed May 07 2025 15:59:57 GMT-0400 (Eastern Daylight Time)

AppLogicalName xxxxx does not have an AppPackage

UciError: AppLogicalName xxxxx does not have an AppPackage at s (https://content.powerapps.com/resource/uci-infra-web/scripts/app.413228e3b75f1b2b75edc08882cab99d.js:33:937947) at https://content.powerapps.com/resource/uci-infra-web/scripts/custompage.1655ac8a54b6f6ebf758cda2cf4970b8.js:4:102594

===

Update: Still not working. After some time, I got a different error message indicating the Dataverse Accelerator app could not be loaded. To isolate the issue, I deleted the Dataverse Accelerator solution following the linked document.

Now all I get is an infinite loading screen (see below) when attempting to open any custom page within a model-driven app.

Categories:

Microsoft Dataverse with Power Apps

@JoannaMERP

The error you're encountering — AppMetadataParserFailed with the message "AppLogicalName xxxxx does not have an AppPackage" — typically indicates a problem with the metadata or deployment of the app in your specific environment. Since you mentioned that:

The issue only occurs in one environment.
Other environments are working fine.
It started after editing a custom page.

This strongly suggests a corruption or misconfiguration in the app metadata in that environment.

Possible Causes and Fixes

Here are some steps and considerations based on similar issues reported by others:

Check if the AppPackage is Missing or Corrupted:
- Go to the Power Apps Maker Portal for the affected environment.
- Try to export the app and see if it throws any errors.
- If export fails, the app metadata might be corrupted.
Revert or Restore the App:
- If you have version history enabled, try restoring a previous version of the app from before the issue started.
Re-import from a Working Environment:
- Export the working version of the app from another environment.
- Import it into the affected environment as a new app or overwrite the broken one.
Check for Environment-Specific Dependencies:
- Ensure that all custom connectors, environment variables, and data sources used in the custom page are correctly configured in the affected environment.
Clear App Cache and Session Storage:
- You mentioned clearing the cache, but also try clearing session storage or using an incognito window to rule out client-side issues.
Raise a Microsoft Support Ticket:
- If the issue persists and you suspect a backend issue, especially if the app metadata is not recoverable, contact Microsoft support with the Session ID, Activity ID, and Timestamp.