Hi,
I have an issue when I update a component library from my consuming Canvas app.
Of course, everything was functional, this misbehavior started yesterday.
I open the Canvas app (git from Azure Repos) and I see the banner saying "Component library updates available". Fine, it's my recent published changes catched by the app. So I click "Review". In the popup, I confirm I want to update the component library.
Then, the infamous "Loading" dialog is shown and it stays there.
The Component library contains around 15 components, it's mostly formatted controls, no big deal, normally it takes something line 10-15 seconds to update.
How may I see what is going on under the hood? Where the update process is hanging? What is causing this issue?
I took a look at the Browser's Console and there is Crash Reports there. There is many errors saying:
Refused to set unsafe header "Content-Length"
Crash Reports concerns the following FileNames:
- /_common/global.ashx
- /main.aspx
- /_static/_controls/globalquickcreate/globalquickcreatebehavior.js
| File name | Message |
| main.aspx | Error initializing component with element id='crmHistoryManager' and with type='Mscrm.HistoryManager': Failed to read a named property 'href' from 'Location': Blocked a frame with origin "https://_____.dynamics.com" from accessing a cross-origin frame. |
| global.ashx | Uncaught SecurityError: Failed to read a named property 'Xrm' from 'Window': Blocked a frame with origin "https://_____.dynamics.com" from accessing a cross-origin frame. |
| globalquickcreatebehavior.js | Uncaught SecurityError: Failed to read a named property 'Mscrm' from 'Window': Blocked a frame with origin "https://_____.dynamics.com" from accessing a cross-origin frame. |
Note: I have masked the Dynamics URL, it's not _____ in the Browser console.
I tried to locate a JS variable or something that might contains more details, but I couldn't find anything helpful.
Is someone can help me finding why the Component Library Update process stays in "Loading..." forever?
Is there somewhere I can find more details on where is the hiccup in the update process ?
Thanks,
