powerplatform-build-tools: Solution import with Canvas App fails with error 'CanvasApp import: FAILURE: No file with that name found'
We’re using the Power Platform Github Actions for our ALM processes, which I understand are wrapper around the PAC CLI.
The ‘import-solution’ action is failing currently with the following error:
The reason given was: CanvasApp import: FAILURE: No file with that name found Microsoft PowerPlatform CLI Version: 1.28.3+g4ba7dfd
The command which fails via Github Actions is:
Calling pac cli inputs: solution import --path D:\a\....solution_managed.zip --async true --force-overwrite true --publish-changes false --skip-dependency-check false --convert-to-managed false --max-async-wait-time 60 --activate-plugins true --skip-lower-version false --import-as-holding true --settings-file .....\deploymentsettings.json
Our commit process involves invoking the following commands via Github Actions (all of which succeed and do not unpack Canvas Apps)
Calling pac cli inputs: solution export --name solution --path D:....\solution.zip --overwrite true --managed false --async true --max-async-wait-time 60
Calling pac cli inputs: solution export --name solution --path D:\.....\solution_managed.zip --overwrite true --managed true --async true --max-async-wait-time 60
Calling pac cli inputs: solution unpack --zipFile D:\....\solution.zip --folder D:.....\solution --packageType Both --errorlevel Info --singleComponent None --useLcid false --useUnmanagedFileForMissingManaged false --disablePluginRemap false --allowDelete true --allowWrite true --clobber true
Calling pac cli inputs: solution unpack --zipFile D:\.....\solution.zip --folder D:\.....\solution --packageType Both --errorlevel Info --singleComponent None --useLcid false --useUnmanagedFileForMissingManaged false --disablePluginRemap false --allowDelete true --allowWrite true --clobber true
Our build process involves invoking the following commands via Github Actions (all of which succeed and do not repack Canvas Apps)
Calling pac cli inputs: solution pack --zipFile /home/runner/work/....../solution.zip --folder /home/runner/work/...../solution --packageType Both --errorlevel Info --singleComponent None --useLcid false --useUnmanagedFileForMissingManaged false --disablePluginRemap false
All of this setup was working fine until yesterday
About this issue
- Original URL
- State: closed
- Created 6 months ago
- Reactions: 1
- Comments: 20 (4 by maintainers)
We are investigating this issue.
@greggdavenport The solution provided works as a workaround! Hope Microsoft will patch this sooner than later
@StefDeBisschop , in the community forum mentioned above, some members said deleting the additionalUri node from the canvas apps metadata XML was a good workaround. I have also found this to be the only solution that works for me, and I’ve used this in several repos.
I have been able to reproduce this issue and our engineering team is working on the fix. In the meantime, you can force PAC CLI ver: 1.29.11 by using below:
I’m having the same problem. Any update??? Thanks.
@RobertMadar As this doesn’t appear to be a platform issue, my official support request was closed as that is not the right channel. I’m told via other channels that the appropriate MS team (I’m guessing the team that looks after the PAC CLI, PPBT and/or Github Actions) is looking at this. I’ll follow up next week.
Hello, have similiar problem with Import part. Do you have any news?
Solution Importing… Microsoft PowerPlatform CLI Version: 1.25.2+g1c4a1b8 Online documentation: https://aka.ms/PowerPlatformCLI Feedback, Suggestions, Issues: https://github.com/microsoft/powerplatform-build-tools/discussions
Error: CanvasApp import: FAILURE: No file with that name found CanvasApp import: FAILURE: No file with that name found
Thanks for following up @bananabrann for following up.
I have verified that a manually exported solution from the source development environment successfully imports manually into the target environment. And as you have highlighted, even exporting the solution from the source environment using an automated process and then importing this to the target succeeds. The failure occurs if you unpack the exported solution, repack it and then attempt to import this repacked version to the target environment.
The challenge I have is that our current setup is designed to be source control centric with an emphasis on end to end traceability as this gives us confidence over the versions of artifacts that are deployed. Therefore, we do not hold the exported solution anywhere and rely on our build process to generate the solution to be deployed.
I may have to adopt an approach similar to what you describe in your workaround for now, but I am still waiting on Microsoft to come back to me on this.
@parvezghumra This is the issue our team is having too; I’ve been talking in #677. Seems similar enough 🤷♂️ I haven’t confirmed 2.0.47 works because of our bureaucratic processes to update the build tools from 2.0.5 on ADO Marketplace
Currently our workaround is to import manually across our environments. It’s a pain, but the world is punishing me for taking other technology for granted 😝