I am facing this issue: "Error deploying or retrieving source: The file or directory that you tried to deploy or retrieve isn't in a package directory that's specified in your sfdx-project.json file"
There is another post with this similar error but not able to fix with those answers.
https://salesforce.stackexchange.com/questions/380221/error-deploying-or-retrieving-source
I am using:
jdk 17
sfdx-cli/7.181.1 win32-x64 node-v18.12.1
Version: 1.74.1 (user setup)
Commit: 1ad8d514439d5077d2b0b7ee64d2ce82a9308e5a
Date: 2022-12-14T10:30:51.966Z
Electron: 19.1.8
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Windows_NT x64 10.0.22621
Sandboxed: No
Windows 11
Another issue is
{ "packageDirectories": [
{
"path": "force-app",
"default": true
}
],
"name": "IvannaDevs",
"namespace": "",
"sfdcLoginUrl": "https://login.salesforce.com",
"sourceApiVersion": "55.0"
}
Any ideas about what is wrong here?
Related
Recently i am not able to use the Vlocity VScode extension. I tried to uninstall the extension and salesforce one and then VS code also. Reinstalled everything from scratch and able to work with Salesforce extension but not able to connect the org for vlocity. Even cleaned the alias and logged out from all the orgs in terminal and started with just one org but no luck. I am attaching the screenshot. Please let me know if there is something that is missing from my end or if this is a known issue.
OS : MAC (12.6.1) Monterey
SF cli : sfdx-cli/7.180.0 darwin-x64 node-v18.12.1
Vs Code Version : 1.74.0 (Universal)
Commit: 5235c6bb189b60b01b1f49062f4ffa42384f8c91
Date: 2022-12-05T16:43:37.594Z (1 wk ago)
Electron: 19.1.8
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Darwin x64 21.6.0enter image description here
I have not used Flutter for a few months so when I wanted to create a new project I upgraded to Flutter 3 and VS Code to
Version: 1.67.2 (user setup)
Commit: c3511e6c69bb39013c4a4b7b9566ec1ca73fc4d5
Date: 2022-05-17T18:15:52.058Z
Electron: 17.4.1
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: 9.8.177.13-electron.0
OS: Windows_NT x64 10.0.19043
My problem is "stful" and "stless" does not create the widgets.
Flutter Doctor. No issues found.
I have tried to Google it with no responce. Any help will be appreciated.
I am using VSC:
Version: 1.65.2
Commit: c722ca6c7eed3d7987c0d5c3df5c45f6b15e77d1
Date: 2022-03-10T15:36:26.048Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Linux x64 5.13.0-35-generic snap
I want to debug my react application that uses web3 to connect to ethereum blockchain.
I created the following launch.json:
{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [
{
"type": "pwa-chrome",
"request": "launch",
"name": "Debug React ",
"url": "http://localhost:3000",
"webRoot": "${workspaceFolder}"
}
]
}
When I start my application with npm run start it runs correctly in my chrome browser, where metamask is installed.
However, when pressing the debug launch config a new emtpy chrome window starts, that has no metamask tooling installed, like the following:
Any suggestions how to start my installed chrome browser?
I appreciate your replies!
I have probably around 25 odds extensions installed on my VSCode.
However some of my extensions are disabled - they seems to change a bit every time I start the VSCode and there is no option to enable it.
The only work around I have at the moment is to uninstall and install again to get it enabled.
I don't see any pattern. Why is this the case?
VSCode version:
Version: 1.47.3 (system setup)
Commit: 91899dcef7b8110878ea59626991a18c8a6a1b3e
Date: 2020-07-23T13:12:49.994Z
Electron: 7.3.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.19042
Though not obvious to end users like you, each extension releases has a minimal VSCode version required.
For example, the Microsoft C/C++ extension showed in your screen shot is of version 1.5.1, which depends on VSCode 1.53.0 and above,
"engines": {
"vscode": "^1.53.0"
},
https://github.com/microsoft/vscode-cpptools/blob/1.5.1/Extension/package.json#L14
Since you are using a much older version (1.47.3), this extension can only be disabled to avoid conflicts.
All of a sudden, the debuggger stops at return ma.invoke(obj, args);in the java.lang.reflect.Method.class file.
And it ignores my own breakpoints.
I'm under release:
Version: 1.36.1
Commit: 2213894ea0415ee8c85c5eea0d0ff81ecc191529
Date: 2019-07-08T22:55:08.091Z
Electron: 4.2.5
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Linux x64 5.0.0-050000-generic snap
I have the following extensions:
Name: Java Extension Pack
Id: vscjava.vscode-java-pack
Description: Popular extensions for Java development and more.
Version: 0.7.1
Publisher: Microsoft
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=vscjava.vscode-java-pack
Name: Language Support for Java(TM) by Red Hat
Id: redhat.java
Description: Java Linting, Intellisense, formatting, refactoring, Maven/Gradle support and more...
Version: 0.47.0
Publisher: Red Hat
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=redhat.java
Name: Debugger for Java
Id: vscjava.vscode-java-debug
Description: A lightweight Java debugger for Visual Studio Code
Version: 0.20.0
Publisher: Microsoft
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=vscjava.vscode-java-debug
Doing a Java: Clean the Java language server workspace solved the issue.