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)

[Timsen]

Just created an A-level case on this - and finally got someone on the horn.

Apparently, Microsoft PowerApps support is currently experiencing a severe backlog buildup in their support, and they have had several similar incidents as those reported here.

I was suggested to reenable the retiring "import/export components" feature, but this did not solve anything, and I was promised an update email for the case to receive further info - this has not yet been received.

[arpost]

Appreciate the update. Good to know you got a reply and they are aware. Having been in customer service myself, I feel for the frontline support team members. Wouldn't want to be in their shoes right now.

[Shuski]

Replying to keep track of this as I've just started encountering this and I can't do any further updates to my apps...literally at a show-stopper level right now.

One thing I noticed though; My environment is using modern controls by default. With "Try out the modern controls" turned off, and the other "Replace classic (legacy) controls in the insert menu" in experimental tab off as well. This is happening in both my canvas app and component library. 

An odd thing about this is that the canvas app doesn't have the "Replace classic (legacy) controls in the insert menu" option appear in the experimental tab, no matter what the "Try out the modern controls" is set to?

^ Video attached showing what I mean.

Both seemed to have also randomly updated to 3.23051.23 automatically on the 17th? (Or another dev updated it to try out modern controls at some point and can't remember).

[obstinateowl]

I'm having the same issue, previously updates to the component library worked fine when imported to any of my apps. Recently however this started to fail with the exact same, very unhelpful, error you are getting. Additionally, it seems to proceed with importing the update despite the error and breaks the entire app leaving just a blank grey screen. 

[Timsen]

This is exactly what I am talking about - I do not use modern controls, but I am using the "Behavior" output on the component library (to get button callbacks to my main app).

My support case is not really having any traction, and I am starting to wonder if Component Libraries are mature enough yet to be used for anything but experimental stuff.

[obstinateowl]

Ya I'm the same, the Behavior outputs are pretty critical to how I'm using components. 

Interestingly enough, I experimented with creating a new app and importing the library, and the import worked fine... So I then went and made a minor change to the component (adjusted the default value of an input property) and republished. Went to the brand new app that had successfully imported the component library a minute before, and what do you know the same update error I had before. 

And ya I'd agree, not having the updates to existing component libraries working is a massive flaw that is going to prevent me from further development. Very frustrating since it has been overall working well for months. 

[Timsen]

According to Microsoft, they have released an internal bug-fix yesterday, that should solve the issue.
In my app, it does appear that I now am able to update component libraries again. I will be testing some more, but this does look promising.

Too bad though, that it had to take more than a week for MS to acknowledge the issue and another week to get it fixed.

[Dindzhov991]

Is everything resolved now for you ? I just had the same issue today again.