import-solution action fails with 'Unrecognized GUID Format' error

[priyanka-agrawal2885]

Reference Issue: microsoft/powerplatform-build-tools#1041

The microsoft/powerplatform-actions/import-solution GitHub Action is erroring out in our deployment workflows with the error: Unrecognized GUID Format.

After a lot of research, we found out that the solution being exported using the microsoft/powerplatform-actions/export-solution GitHub Action doesn't contain GUIDs within their environment variable definition json files. And while importing the solution to an environment for the first time, it tries to look for GUIDs of the environment variables created, due to which we are getting this error. We could find out that this issue has been worked upon in the pac CLI version 1.35 where invalid GUIDs are ignored without throwing any error. But the pac CLI version being used under the latest versions of microsoft/powerplatform-actions GitHub Actions is 1.34.4 due to which we are receiving Unrecognized GUID Format error and all our related workflows are failing. This is impacting our deployments in various environments including production.

import-solution:
authenticated successfully.
Validating connection...
Connected to... QA
Default organization: QA
Authentication profile created
* UNIVERSAL : *** Public ***

Calling pac cli inputs: solution import --path D:\a\pp-case\pp-case\release\artifact***.zip --async true --force-overwrite true --publish-changes true --skip-dependency-check false --convert-to-managed false --max-async-wait-time 60 --activate-plugins true --skip-lower-version false --settings-file deployment-settings-qa.json
Connected as ***
Connected to... QA

Solution Importing...
Microsoft PowerPlatform CLI
Version: 1.34.4
Online documentation: https://aka.ms/PowerPlatformCLI
Feedback, Suggestions, Issues: https://github.com/microsoft/powerplatform-build-tools/discussions

Error: Unrecognized Guid format.

Error: error: 1
Error: error: 1
Error: failed: Connected as ***

[sagargadamsetti]

I am also running into the same error.

[petrochuk]

This is fixed in PAC CLI 1.35 and above

[priyanka-agrawal2885]

Thanks @petrochuk for your response. I could find this out that this issue is due to the older version of pac CLI. It is fixed in versions 1.35 and above.

But even the latest version of the microsoft/powerplatform-actions is still using pac CLI 1.34.4. There has been no update provided to the actions with the latest version of pac CLI. Due to this, we had to modify our GitHub workflows and replace these actions with the pac commands.

When can we expect an update to the microsoft/powerplatform-actions, supporting the latest version of pac CLI beneath it?