Unanswered

PowerApps Build Tools import solution endless loop

(0) Share

Report

Posted on by FH-Inway

I've set up a small pipeline, which exports an unmanaged solution as managed solution from environment A and imports it to environment B. The pipeline runs up to the PowerApps Import Solution task, which displays the following log:

Starting: PowerApps Import Solution

==============================================================================

Task : PowerApps Import Solution

Description : PowerApps Import Solution

Version : 0.1.7

Author : Microsoft

Help : [More Info](https://aka.ms/buildtoolsdoc)

After that, I can see in environment B that the solution has been imported, because it appears in the list of solutions.

But the pipeline task never finishes. Instead, the log keeps growing and repeats the following message over and over again:

=====================================================================##[section]Starting: PowerApps Import Solution

==============================================================================

Task : PowerApps Import Solution

Description : PowerApps Import Solution

Version : 0.1.7

Author : Microsoft

Help : [More Info](https://aka.ms/buildtoolsdoc)

Any ideas what could be causing this? The pipeline task is configured as shown in the attached screenshot.

Categories:

Power Apps Pro Dev & ISV

PowerAppsBuildToo...

I have the same question (0)

All responses (8)

Answers (2)

v-yutliu-msft on at

Like (0)

Report
Hi @FH-Inway ,

Using solutions has many limitations, please check these tips:

The solutioning experience is available only online and for environment version 9.1.0.267 and later.

Canvas app triggered flows are not available in solutions.

If a canvas app is packaged in a managed solution, it can't be edited and re-published in the target environment. Use unmanaged solutions if the apps require editing in the target environment.

Connections require authentication and consent, which requires an interactive user session and therefore cannot be transported via solutions. After importing your solution, play the app to authenticate connections. You can also create the connections in the target enviornment prior to importing the solution.

Canvas apps shared as co-owner to an Azure Active Directory (AAD) security group can't be added to solutions. Unshare the app before adding it to a solution.

Canvas apps won't display in the classic solution explorer. Use the modern experience.

Canvas app access (CRUD and security) is managed entirely in Power Apps and not in the Common Data Service database.

Database operations such as backup, restore, and copy are not supported for canvas apps and flows. These operations can corrupt canvas apps and flows.

Deleting a managed solution does not rollback to a different canvas app version. Instead, all versions of the app are deleted.

Importing a solution containing a flow will not automatically create or associate required connections. The flow must be edited to fix the connections.

If using managed solutions, this creates an active customization in the unmanaged layer. Therefore subsequent solution updates to the flow will not be reflected.

Flows created from solutions will not be displayed in the "Team Flows" list. They must be accessed through a solution.

Button triggered flows are not available in solutions.

Flows triggered from Microsoft 365 applications such as Excel are not available in solutions.

Flows that connect to SharePoint are not available in solutions.

Flows in solutions don't support delegated authentication. For example, access to a flow is not automatically granted based on having access to the SharePoint list the flow was created from.

Custom connectors created outside solutions cannot be added to solutions at this time.

Here's a doc about this in details for your reference:

https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/use-solution-explorer#known-limitations

Best regards,

Was this reply helpful? Yes No
FH-Inway 18 on at

Like (0)

Report

Thanks for the information. Unfortunately, it does not answer my question. It seems you want to suggest that due to the many limitations, solutions should not be used. Can you suggest an alternative how an ALM (application lifecycle management) can be done for customizations without solutions?

Was this reply helpful? Yes No
David Jenni Microsoft Employee on at

Like (0)

Report

[cross-post of same answer to this Q in VS Marketplace for the PA BuildTools Extension]
@FH-Inway you're running an async import solution (which is perfectly fine). The underlying code will wait until the org service returns a "succeeded" or "failed" status. On the latter (failed status), the task will retry several times (the task code and status code cannot distinguish between retryable and fatal errors returned from the service).
Please rerun your pipeline with the failing/endless loop import but this time with "enabled system diagnostics" checked when queueing the pipeline.
Attach that task's diagnostic log to this thread here (the logging should already be free of secrets/PII but pls double check before posting the log here). Alternatively, email it to me directly (davidjen at my msft email)
.David

Was this reply helpful? Yes No
FH-Inway 18 on at

Like (0)

Report

I reported the issue also in the Q&A section of the PowerApps Build Tools entry in the Visual Studio Marketplace. I was asked to run the pipeline again with "enabled system diagnostics" and provide the log of that run. The log is attached to this message. The text in the log repeats in an endless loop.

ImportSolution.zip

Was this reply helpful? Yes No
David Jenni Microsoft Employee on at

Like (0)

Report

@FH-Inway unfortunately, your previous ImportSolution only seems to set the AzDO system steps to diagnostic, but didn't set the task level variable: System.Debug (it seems yaml vs classic pipelines do that different?)
Please rerun your repo, this time when queuing the pipeline job, explicitly set/add this variable:
System.Debug needs to be set to true
thanks!

Edit: unfortunately, that doesn't yield to show the info I was looking for 😞
Can you contact me on my msft email (davidjen@) so I can point you to a prerelease version that has more diagnostic instrumentation)? thx

Was this reply helpful? Yes No
FH-Inway 18 on at

Like (0)

Report

@DavidJen , thanks for the reply. I ran the pipeline again with the System.Debug variable set to true, but the log is the same as before.

I will send your email the whole log package of the pipeline after I canceled it. Note that the log of the import solution step doesn't show the endless loop in this case (not sure why).

PowerAppsBuildToo...

Was this reply helpful? Yes No
Verified answer

David Jenni Microsoft Employee on at

Like (1)

Report

Closing the loop on this thread after an offline debugging session with @FH-Inway (thanks!):
The asynchronous ImportSolution probes for completion by polling the import's statusCode. Florian's CRM environment is localized to German, the statusCode is localized as well but the code expects the English status code.
A future 0.1.8 release will have this fixed soon.

Was this reply helpful? Yes No
Verified answer

David Jenni Microsoft Employee on at

Like (1)

Report

version 0.1.9 with a fix for this issue has been released earlier today
https://marketplace.visualstudio.com/items?itemName=microsoft-IsvExpTools.PowerApps-BuildTools&ssr=false

Was this reply helpful? Yes No