Answered

Library components not updating

(0) Share

Report

Posted on by spamtomas

Library components not prompting to update in apps anymore, just started today, changing the studio authoring version doesn't make a difference. Importing the component again into an app imports an old version

i actually found a way to manually force updating a library, by going to insert menu. Although it appears the app cant find any component library's, this was working yesterday and today just not. Clearly there is something wrong on MS backend

Categories:

Building Power Apps

I have the same question (0)

All responses (3)

Answers (1)

Verified answer

spamtomas 85 on at

Like (1)

Report
Copy link

Link copied!

Ok a really frustrating morning but my only option was to roll back my app to a previous save, which seems to have fixed it. Really worrying it can just break like that and force me to lose work. My comfort using these components is shaken now

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

Hi,

I'm having the same problem. Can you tell me how did you do this part:

"i actually found a way to manually force updating a library, by going to insert menu. "

Thank you.

Was this reply helpful? Yes No
hjaf 487 on at

Like (0)

Report
Copy link

Link copied!

Creating a copy of a component in the library, for example to replace it with a new component while retaining the old version, can lead to the component of the same name in the app not being updated. Perhaps because it is using some internal id (like "TemplateGuid", which is not visible in power apps studio), or the update process fails because it hits some naming conflict we're not made aware of.

I think perhaps the studio naming convention of automatically adding _1 to copies is also being used internally during the update and update check process, where the conflict happens when there is already a component in either library or app with _1. In any case this is just guessworks and speculation as we get little information beyond errors like "something went wrong", or even better: "there are no components to be updated"

I think an alternative is to unpack the app / solution and component library to determine if there are some possible naming conflicts in the code.

Was this reply helpful? Yes No