RE: Exercise - Use the Power Apps CLI - "PowerAppsTools_lab" not listed

Question

I am having trouble with this learning module.

I cannot successfully push the PCF to the Dev environment. It does not show up in solutions, although it does show up in solutions > history.

From VS Code, using the pac solution list command, the PCF simply doesn't show up:

I've checked the environments, and can't see any problems there.

I do see that the PCF has temp in the name

Solution: bin/Debug/PowerAppsToolsTemp_lab.zip generated.    

Which is different from the exercise guide. I saw this in the code when building :

Checking if the control 'lab_lab.FirstControl' already exists in the current org.
Using full update.
Creating a temporary solution wrapper to push the component.
Building the temporary solution wrapper.

Hoping someone can help.

Answer 1

Hi Garrett Wong,

It seems the issue is with the temporary solution created during the push process. Here's what could be happening: 

1.Temporary Solution Wrapper: The output indicates that a temporary solution wrapper was generated (PowerAppsToolsTemp_lab.zip). This is a common step used by the CLI to push the component, but sometimes it may not push as a permanent solution right away. 

2.Check Solution History: Since you can see it in the Solution History, this suggests that the push command is being partially successful, but not completing the final step of permanently installing the solution. 

3.Clear Temporary Solutions: Try the following steps to resolve the issue: 

Run the command: 

pac solution cleanup

This will remove any temporary or partial solutions. 

Re-run the push command: 

pac pcf push --publisher-prefix lab

4.Ensure Proper Environment: Verify that you are working in the correct environment by running: 

pac org who

Ensure that the Dev environment is selected and properly authenticated. 

5.Build Output Name: The temporary file (PowerAppsToolsTemp_lab.zip) may indicate an issue with the solution naming convention during the push. Try renaming the component to ensure it follows consistent naming and doesn't end up as a temporary file. 

Let me know if you need further assistance 

If you have found the answer provided to be helpful, please click on the "Accept answer/Upvote" button so that it is useful for other members in the Microsoft Q&A community.        

Thank you.

Answer 2

The other way to solve this is to manually (re)run the CLI commands to import and publish the solution. When using the pac command, a zip file for the solution would have been created in the working directory of your local machine. The zip file can be found in the directory - <your working folder>\obj<name of your project>\bin\debug

That is :

pac solution import --path <path to your solution zip file on your local machine>

pac solution publish