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

On first run, Brackets reports that it is unsupported #283

Closed
harryjohnston opened this issue Jun 13, 2023 · 1 comment
Closed

On first run, Brackets reports that it is unsupported #283

harryjohnston opened this issue Jun 13, 2023 · 1 comment

Comments

@harryjohnston
Copy link

Prerequisites

  • [yes] Can you reproduce the problem with Debug -> Reload Without Extensions?
  • [yes] Did you perform a cursory search to see if your bug or enhancement is already reported?
  • [yes] Did you read the Troubleshooting guide?

Description

On first run, Brackets version 2.2.1 complains that "The version of brackets installed in this system is unsupported. Get the latest version of Brackets here or use phcode.dev!"

(The link in the error message goes to the download for the same version of Brackets that is installed.)

We are planning to install Brackets in our computer labs but are concerned that this error message will result in unnecessary calls to our service desk.

The problem does not appear to be limited to 2.2.1, every other version I have tested also raises this error message.

Steps to Reproduce

  1. Install Brackets 2.2.1
  2. Run Brackets for the first time (or delete the folder AppData\Roaming\Brackets and then run Brackets)

Expected behavior: [What you expected to happen]

No error message should appear.

Actual behavior: [What actually happened]

Error message "The version of brackets installed in this system is unsupported. Get the latest version of Brackets here or use phcode.dev!"

Versions

Windows 10 22H2 (OS Build 19045.2965)

Brackets
Release 2.2 build 2.2.1-17943 (master c7a435e)
build timestamp: Sat Mar 11 2023 13:04:22 GMT+0530

@abose
Copy link
Member

abose commented Jun 13, 2023

Thanks for reporting the issue.

The issue is fixed now @harryjohnston . Please reopen if further assistance is needed.

@abose abose closed this as completed Jun 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants