-
Notifications
You must be signed in to change notification settings - Fork 78
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
Lighting-dev plugin : Error (1): The requested resource does not exist #3010
Comments
Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support. |
Hello @elliot41 👋 It looks like you didn't include the full Salesforce CLI version information in your issue. A few more things to check:
Thank you! |
sf version --verbose --json |
Hello @elliot41 👋 None of the versions of Shared: Update to the latest version of Salesforce CLI (docs) and confirm that you're still seeing your issue. After updating, share the full output of |
Still have the issue with the updated config : sf version --verbose --json |
Hello @elliot41, I think we have to open an issue on the plugin-lightning-dev repo from now. |
Not an issue, i forced the apiversion of sf to 62.0, it works now. |
Summary
I am launching the command : sf lightning dev app
This error appears : Error (1): The requested resource does not exist
Expected result
Open the local dev server with the default org application
Actual result
Error message
Additional information
VS Code Version:
Version: 1.91.1 (user setup)
Commit: f1e16e1e6214d7c44d078b1f0607b2388f29d729
Date: 2024-07-09T22:06:49.809Z
Electron: 29.4.0
ElectronBuildId: 9728852
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Windows_NT x64 10.0.19045
SFDX CLI Version: @salesforce/cli/2.42.6 win32-x64 node-v20.14.0
**plugin lightning dev version **: lightning-dev 1.1.0
The text was updated successfully, but these errors were encountered: