pac pcf push installs a solution and immediately uninstalls it

(1) Share

Report

Posted on by mschafer85

Hi everybody,

I'm having a strange issue with my code component.

I've followed the instructions at https://learn.microsoft.com/en-us/training/modules/build-power-apps-component/package-code-component and built my component. However, when I use

pac pcf push --publisher-prefix marc

there's no errors on the command line and the solution gets imported successfully - but immediately uninstalled, too.

No error codes to be seen.

When I create a solution via msbuild and upload it manually, things work just fine. The solution is installed and stays installed. No automatic uninstall.

I've tried that with two different (Developer) tenants; once inside a Production environment, once inside a Developer environment. And each time I had the same issue.

Maybe anyone has an idea why this is happening? That would make my week 🙂

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (7)

Answers (1)

cchannon 4,702 Moderator on at

Like (1)

Report

That is bizarre. Is it just this one component? Like, if you write a basic Hello World, can you deploy that?

Second question, is PAC installed through VS Code or directly to windows as standalone?

Was this reply helpful? Yes No
mschafer85 42 on at

Like (1)

Report

That happens with every component I build, unfortunately - no matter the content, no matter the tenant or environment.

I've installed PAC in Windows:

But in VS Code, I've also got the Power Platform Tools extension.

Was this reply helpful? Yes No
cchannon 4,702 Moderator on at

Like (1)

Report

OK, that would be my first suspect. I don't have a good reason to suspect it, but having two different installs of the same thing, one with background updates and the other without... It's no smoking gun, but it is deserving of suspicion.

So I would uninstall both, then install one of your choice (personally, I like the Windows install because it gets earlier feature releases like the PowerFx support just introduced a few weeks ago, but the VS Code tools are definitely more stable). That will eliminate two possibilities at once: the possibility that there is a conflict between the tools and the possibility that you have an old/bad build (which happens: there have been a lot of PAC builds released with nasty bugs).

Was this reply helpful? Yes No
Verified answer

Diana Birkelbach 3,072 Most Valuable Professional on at

Like (4)

Report

Hi @mschafer85 ,
Currently there are issues with "pac pcf push". Maybe you could try to downgrade the "pac cli" and see if your issue persists.
Here the other thread for reference: https://powerusers.microsoft.com/t5/Power-Apps-Pro-Dev-ISV/PCF-Push-eror/m-p/2476718/highlight/true#M9545

Was this reply helpful? Yes No
mschafer85 42 on at

Like (1)

Report

Hi @DianaBirkelbach, @cchannon,

thanks for your suggestions!

It indeed was caused by some issue with the Microsoft PowerPlatform CLI - I downgraded the "Power Platform Tools" extension within VS Code to 2.0.3 and it worked like a charm.

Just in time for the weekend 🙂

Was this reply helpful? Yes No
Diana Birkelbach 3,072 Most Valuable Professional on at

Like (1)

Report

Hi @mschafer85 ,
I have now a better workaround. Maybe it helps in the future: https://dianabirkelbach.wordpress.com/2024/01/16/how-to-fix-pac-pcf-push-issues-with-pac-cli-newer-than-1-28-3-publisher-error-or-solution-deleted/

Was this reply helpful? Yes No
Diana Birkelbach 3,072 Most Valuable Professional on at

Like (1)

Report

Hi @mschafer85 ,

The "pac pcf push" issue is fixed with pac cli version 1.30.6. 😍
This will be available soon in VSCode too, but until then, you can use the standalone version of the pac cli.
Even the new parameter "--solution-unique-name" worked now. We can now specify which solution should be used. The publisher prefix is taken from the solution.

Was this reply helpful? Yes No