Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open License File - not able to read license #1222

Closed
DataTraveler1 opened this issue Jun 12, 2022 · 6 comments
Closed

Open License File - not able to read license #1222

DataTraveler1 opened this issue Jun 12, 2022 · 6 comments
Labels
bug Something isn't working completed The issue has been completed but is not yet released. PowerShell Pro Tools Issue relates to PowerShell Pro Tools.

Comments

@DataTraveler1
Copy link
Collaborator

Describe the bug

Any attempt to add a valid license to PowerShell Pro Tools through the 'Open License File' option will fail due to a bug

To Reproduce

  1. Possess a valid license.txt for PowerShell Pro Tools
  2. Have PowerShell Pro Tools VS Code extension installed but unlicensed
  3. In VS Code, select the 'Command Palette' under 'View' (Ctrl+Shift+P)
  4. Use the command 'PowerShell Pro Tools: Open License File' to import your valid license.txt
  5. Receive below error dialog. License import process does not complete.

image

⚠This issue may also be impacting the "Install License" button from the extension Welcome Page

Workaround

  1. Open license.txt in notepad and copy the entire contents into your clipboard (Ctrl+A, Ctrl+C)
  2. Navigate to the PowerShell Pro Tools extension settings and manually enter the license data into the dialog (see screenshot below)

image

Expected behavior

The valid license file should be accepted and imported without error.

Screenshots

image

figure shows the Open License File command from the command palette

Version

VS Code 1.67.2
PowerShell Pro Tools for VS Code 2022.5.2

@DataTraveler1 DataTraveler1 added bug Something isn't working PowerShell Pro Tools Issue relates to PowerShell Pro Tools. labels Jun 12, 2022
@adamdriscoll
Copy link
Member

This issue has been mentioned on Ironman Software Forums. There might be relevant details there:

https://forums.ironmansoftware.com/t/received-trial-license-but-i-cant-install-it-in-vs-code-on-win-10/4394/5

@DataTraveler1
Copy link
Collaborator Author

Install-PoshProToolsLicense can also be used to install the license, of course

⚠Be sure to note that the -License parameter requires the content of the license file and not a path to the license.txt file.

image

@adamdriscoll
Copy link
Member

@DataTraveler1 - Can you send me the license you are using via email or something? I can't reproduce this.

@DataTraveler1
Copy link
Collaborator Author

@adamdriscoll - A sample license file has been sent along with an animated .gif to more clearly demonstrate the issue

@adamdriscoll
Copy link
Member

@DataTraveler1 Thanks!

@adamdriscoll adamdriscoll added the completed The issue has been completed but is not yet released. label Jun 14, 2022
@adamdriscoll
Copy link
Member

I've removed Open License File. Install License Key should be used instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working completed The issue has been completed but is not yet released. PowerShell Pro Tools Issue relates to PowerShell Pro Tools.
Projects
None yet
Development

No branches or pull requests

2 participants