You’re offline. This is a read only version of the page.
I have a bunch of custom pages in my environment and lately, the changes in the custom pages have not been reflected regardless of whether publishing the app or publishing all. I have tried clearing the cache to check if there is any issue with solution layers but nothing seems to solve. Has anyone faced this issue too? Used to work perfectly fine before.
In addition to the custom page not reflecting updates, I attempted to create a new app and add it to the model-driven app. Unfortunately, this also failed, and the error displayed below occurred.
Error Code: AppMetadataParserFailed
Session Id: b309a790-e30f-4735-9106-ad62aa49232c
Activity Id: 459cda53-6947-40ab-a60f-cf054a894ea2
Timestamp: Mon Feb 26 2024 22:39:21 GMT+0545 (Nepal Time)
Child Canvas app is not found in root app manifest
UciError: Child Canvas app is not found in root app manifest at s (https://content.powerapps.com/resource/uci-infra/scripts/app.5554154d9ba03c1f981e9d0cdf8026f7.js:33:940289) at https://content.powerapps.com/resource/uci-infra/scripts/custompage.273a96f2276a4a7b4edfd9e887f2ee07.js:4:224356
I speculate that this issue may be related to the underlying problem.
I ended up creating a brand-new model driven app. Like a few other critical bugs with custom pages I've found, Microsoft was not helpful, and it was clear I was working with techs who had very limited knowledge of their systems.
Just to be sure - you are working with a managed or unmanaged solution? You mentioned solution layers and that would be important if working with managed solutions. If you are, be sure to remove the unmanaged layers from your custom page and model driven app.
You can try deleting your existing model driven app and creating a new model driven app. Be sure to use the existing site map and solution so you get all your customizations back. This should allow the associations to get refreshed.
Hey,
this is a problem multiple users faced lately.
In order to fix this for your app there is a workaround:
So try adding a new dummy custom page, publish the app, remove (delete) the dummy page and publish again, then add your correct page again and publish again.
This should resolve the issue.
#1
mmbr1606
22
Super User 2025 Season 1
#2
stampcoin
17
#3
ankit_singhal
11
Super User 2025 Season 1
Share
Report
All responses (
Answers (
