Updating Component Library fails: "there was a problem importing.... (null,null,null ....)

[Timsen]

I am building a Canvas app that relies on a component library.

The library has been working fine until now (and also works fine in a different app/solution), however starting last week, I get an error when trying to update/refresh the library (see attached).

This completely breaks the canvas app, and I am only able to get it working again, by quitting without saving - or reverting to a previous version of the app.

I have tried rolling back both the Canvas app and the Component Library to known working versions, but this does not fix the issue.

Obviously I have tried all the basic things like different browsers, clearing caches etc. to no avail.

Anyone have any insights or suggestions? - I have raise a MS ticket, but no response from them yet.

Also see related thread: Error updating components library when library ha... - Power Platform Community (microsoft.com)

[timl]

@Timsen 

Have you enabled or do you use modern controls in your app? I've seen some reports of similar errors related to modern controls.

[Timsen]

@timl 
Nope - no fancy stuff at all - just the standard controls.
The issue started very suddenly between thursday and friday last week, and coincides with a change in version on the powerapps side (from 3.23044.15 to 3.23051.23), however reverting to previous versions on both library and canvas app and even restoring to previous versions of the app/component does nothing to resolve the issue.

I have tested the component library in a different app, and that works fine - I have also tried creating a new component library and using that in my canvas app - and that ALSO works fine.
It seems to be the specific app and specific library having some sort of reference somewhere, that botches the update and breaks the canvas app.

[timl]

@Timsen - Many thanks for clarifying this. There definitely is a bug here. Hopefully Microsoft support can work out the cause and provide a fix.

[KASCHN]

I logged a similar issue too. The only difference is I am in a custom page not a proper canvas app. Kind of at a loss what to do. I can remove the component and delete the reference to it and add back in as a new version of the component. But, I have to copy again all of my property configuration which is a pain and defeats the purpose. I have tried with component libraries with and without modern controls and am seeing this issue, regardless. 

Here is the link.

[arpost]

Has anyone heard boo back from Microsoft on this? Still haven't gotten replies on two different support tickets.

[Timsen]

Nope - I raised one ticket - no response, then another, and got the usual "triage" questions, and was told that the issue had to be escalated - but since then - complete radio silence, and no way to nudge the ticket.

[arpost]

This is all really strange. Previously, I found Microsoft's support to be fairly prompt in their responses, but I've seen a significant downward shift in support experience over the last few months or so. Makes me wonder if their support teams have had a workforce reduction or something.

Either way, here's hoping we get an update. And that I get a reply to my two tickets this week. Maybe.

[KASCHN]

I also raised a ticket last week and even built them a solution that demonstrated the issue. Haven't heard anything. Maybe they are busy fixing it...

[Timsen]

@KASCHN could you describe the solution you created - I would like to reproduce it on my tenant.
I have still not heard a peep from Microsoft - starting to wonder if their support chain has failed completely around the Component Library.