I recently moved to a new workstation and cannot target an Adobe Application using VSCode and Extendscript Debugger. The workstaton previously had CS 6 installed on it, but now we use CC. I'm using Ilustrator 2019.
I can target Illustrator:
Target Menu Works
Illustrator 2019 shows up in the bar along the bottom:
AI 2019 looks like it is the target
But, then when I run the DeBugger it says CS 6 isn't running and I can't run CC2019?
Asked to target CS6?
Using MacOS 10.12.6
VSCode 1.50.1
ExtendscriptDebugger 1.1.2
I think you need to check the launch.json file to set the targetSpecifier version number.
For example, for After Effects 2020, I use this configuration to debug. This object is found in the configruations array in the launch.json file:
{
"type": "extendscript-debug",
"request": "launch",
"name": "My app debug",
"program": "${workspaceFolder}/Scripts/source.jsx",
"trace" : true,
"targetSpecifier": "aftereffects-17.0",
"engineName": "main",
"preLaunchTask": "debug-my-app",
"dontBreakOnErrors" : true
}
So, likely you need to find out the value for the targetSpecifier for the version of Illustrator you want the debugger to target.
Related
OS and Version: Windows 10 Build 19042.985
VS Code Version: 1.56.2
C/C++ Extension Version: v1.4.0-insiders
other extensions: remote-ssh
I've been working with remote-ssh on a raspberry and c/c++ extension without any issue, all of a sudden I cannot start the debugger. Nothing changed, configuration files are the same as before but now when I start the debugger, I see for a couple of seconds the top debugging bar and then it disappears. No message on the console, nothing.
For this purpose, I created a simple project from scratch, and even there, the same issue appears.
To Reproduce
launch.json
{
"version": "0.2.0",
"configurations": [
{
"name": "(gdb) Launch",
"type": "cppdbg",
"request": "launch",
"program": "${workspaceFolder}/a.out",
"args": [],
"stopAtEntry": false,
"cwd": "${workspaceFolder}",
"environment": [],
"logging": { "engineLogging": true },
"externalConsole": true,
"MIMode": "gdb",
"miDebuggerPath": "/usr/bin/gdb",
"setupCommands": [
{
"description": "Enable pretty-printing for gdb",
"text": "-enable-pretty-printing",
"ignoreFailures": false
}
]
}
]
}
main.c
#include <stdio.h>
int main(){
printf("ciao\n");
return 1;
}
Compile with gcc -g main.c
As I stated before, this workflow worked for me, from one second to another it stopped working as intended and I have no idea why and how to fix it, any help is appreciated.
What I tried
reinstall vscode
reinstall the c/c++ extension and delete by hand the extension folder
numerous reboots
Updates
I have tried with the wsl-remote extension and it is working as expected.ù
Tried to uninstall gdb from host and launch the debug session, the message "gdb" not found does not even appear as it should
I was in similar situation and couldn't find relevant resolutions:
Quick Answer:
After upgrade to VS Code 1.56.2, make sure to remove old breakpoints and create new breakpoint and at-least have 1 breakpoint and launch.json available.
Lengthy details:
I have similar issue for python scripts when I start the "debugger bar" I see it for a couple of seconds the top debugging bar and then it disappears. Bu then no message on the console, nothing. I tried reinstalling VS Code, enabling/disabling extension, various restart.
OS and Version: Mac OSX Version 11.4 (20F71)
VS Code Version: 1.56.2
Extension: Python v2021.5.842923320 by Microsoft
RootCause:
What I did know for sure that I updated my VS Code, and after that this mysterious issue start happening, so when to release log of VS Code 1.56.2. I found below release log
Debug view displayed on break#
The default value of the debug.openDebug setting is now
openOnDebugBreak so that on every breakpoint hit, VS Code will open
the Debug view. The Debug view is also displayed on first session
start.
So VS code Version 1.56 release, debugger will only show when at-least 1 breakpoint is found. However, looks like there is issue with their internal code checking for historical breakpoint data after VS Code upgrade..
https://code.visualstudio.com/updates/v1_56#_debug-view-displayed-on-break
I had this same issue in python. The fix for python was changing to a valid interpreter due to a python library not being installed. Make sure that the interpreter is correct and then try again.
This may be caused by a faulty installation of the VS Code C/C++ extension. When launching VS Code, if the message "Unable to start the C/C++ language server. IntelliSense features will be disabled" appears, this is probably the cause. Was able to fix the installation in this case by installing a previous version of the C/C++ extension as per this answer.
I had the same problem (though the debug bar would show up for a second and then disappear). I was using a conda env with python 3.6. I updated to 3.8, with the same dependencies, and it started working.
I'm trying to run my app on Chrome but I'm getting these errors. Also installed windows visual c++ update but still not working
f5:
Unable to launch browser : spawn unknown
"version": "0.2.0",
"configurations": [
{
"type": "pwa-chrome",
"request": "launch",
"name": "Launch Chrome against localhost",
"url": "http://localhost:8080",
"webRoot": "${workspaceFolder}"
}
]
}
Flutter run -d chrome :
CreateProcessW failed 14001
Oops; flutter has exited unexpectedly: "ProcessException: The application has failed to start because its side-by-side configuration is incorrect.
Please see the application event log or use the command-line sxstrace.exe tool for more detail.
Command: C:\Users\abc\AppData\Local\Google\Chrome\Application\chrome.exe
--user-data-dir=C:\Users\abc\AppData\Local\Temp\flutter_tools.282fd59e\flutter_tools_chrome_device.1c0b2e2a --remote-debugging-port=1636
--disable-background-timer-throttling --disable-extensions --disable-popup-blocking --bwsi --no-first-run --no-default-browser-check
--disable-default-apps --disable-translate http://localhost:1573".
A crash report has been written to D:\LaughBit\laughbit\flutter_06.log.
This crash may already be reported. Check GitHub for similar crashes.
https://github.com/flutter/flutter/issues?q=is%3Aissue+ProcessException%3A+The+application+has+failed+to+start+because+its+side-by-side+configuration+is+incorrect.+Please+see+the+application+event+log+or+use+the+command-line+sxstrace.exe+tool+for+more+detail.%0D%0A%0A++Command%3A+C%3A%5CUsers%5Cabc%5CAppData%5CLocal%5CGoogle%5CChrome%5CApplication%5Cchrome.exe+--user-data-dir%3DC%3A%5CUsers%5Cabc%5CAppData%5CLocal%5CTemp%5Cflutter_tools.282fd59e%5Cflutter_tools_chrome_device.1c0b2e2a+--remote-debugging-port%3D1636+--disable-background-timer-throttling+--disable-extensions+--disable-popup-blocking+--bwsi+--no-first-run+--no-default-browser-check+--disable-default-apps+--disable-translate+http%3A%2F%2Flocalhost%3A1573
To report your crash to the Flutter team, first read the guide to filing a bug.
https://flutter.dev/docs/resources/bug-reports
Create a new GitHub issue by pasting this link into your browser and completing the issue template. Thank you!
https://git.io/JOSer
Go to Google Chrome File location, let say on Windows 10/11, or even in a shortcut icon -> Right-click -> Properties -> Open File Location.
You will see two applications of the chrome: chrome.exe and chrome_new.exe.
Run the chrome_new.exe and it will delete and replace the previous chrome.exe.
After that, you will now be able to start and use Google Chrome again.
I am having the setup that my flutter-sdk lives inside the projects root because I am using a version management system (FVM). When I run my programs from the console I run 'fvm flutter run' from the console but I also want to be able to start a debugging session with that SDK in the projects root ...
therefore my question is if it is possible to specify the SDK path for launching a Flutter App in debug mode and if how would i do it?
In vscode press ctrl+shift+p, search for 'set flutter sdk', and you can identify your Flutter installations and dart as well. You can edit this manually also in the settings.json.
You can try this, and create a launch.json, by going to Run in VScode menu, then Add Configurations,
add the following, mind you, your project's directories.
{
"configurations": [
{
"program": "lib/main.dart",
"name": "YOUR APP NAME",
"cwd": "/home/u/Projects/fireflutter/live-projects/YOUR_PROJECT_FOLDER/",
"type": "dart",
"request": "launch",
"flutterMode": "debug",
"args": [
// "--web-port",
// "8080",
// "--no-sound-null-safety",
// pass your arguments here, whatever you would type
//in the terminal when you would use i.e
//flutter run --no-sound-null-safety[I love null safety by the way,
//but this is a common problem for people who still want to opt out of it.
],
}
],
"dart.flutterSdkPath": "/home/u/Downloads/sdks/flutter",
"dart.sdkPath": "/home/u/Downloads/sdks/flutter/bin/dart",
}
If you get an error saying Error: spawn /bin/sh ENOENT, it means that your path is incorrect, and you have to fix either your program or cwd or name. Please update on the result of this.
I am new with Flutter, and I am trying to view my new project with Android Emulator. I've installed Dart, Flutter, and Android Studio correctly, but when I try to start the project in Visual Studio (without and with debugging mode), and choosing the correct emulator I get the following error:
Your launch config references a program that does not exist. If you
have problems launching, check the "program" field in your
".vscode/launch.json" file.
I have read in the documentation that it is possible to fix this by adding:
"program": "lib/main.dart",
instead of:
program : bin/main.dart
But still does not work.
First of all, your question says you are going to run Flutter web project in android emulator.
From this, I am guessing that you are using Flutter beta version. With that version, you can't run your project on android emulator.
Second, to run Flutter project on VSCode, you need to add launch.json file for some configuration like this.
{
"version": "0.2.0",
"configurations": [
{
"name": "Flutter - Current",
"request": "launch",
"type": "dart"
}
]
}
When the code is not running, I can add breakpoint (round red circle), but as soon as it goes into debug mode, it turns into unverified breakpoint (grey hollow circle) and doesn't work at all. However, the same project works well on other systems.
I've no idea what the problem is or what the solution would be.
I've tried reinstalling flutter SDK numerous times, and have gone through a lot of links on SOF and GitHub regarding this, but none has been helpful enough.
Environment - VS Code,
Flutter version: 1.17.2
Flutter doctor -
[✓] Flutter (Channel stable, v1.17.2, on Mac OS X 10.15.3 19D76, locale en-GB)
[✗] Android toolchain - develop for Android devices
✗ Unable to locate Android SDK.
Install Android Studio from: https://developer.android.com/studio/index.html
On first launch it will assist you in installing the Android SDK components.
(or visit https://flutter.dev/docs/get-started/install/macos#android-setup for detailed instructions).
If the Android SDK has been installed to a custom location, set ANDROID_SDK_ROOT to that location.
You may also want to add it to your PATH environment variable.
[✓] Xcode - develop for iOS and macOS (Xcode 11.3.1)
[!] Android Studio (not installed)
[✓] VS Code (version 1.45.1)
[✓] Connected device (1 available)
! Doctor found issues in 2 categories.
My launch.json File -
{
// 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": [
{
"name": "Flutter: Run all Tests",
"type": "dart",
"request": "launch",
"program": "./test/"
},
{
"name": "Dart: Run all Tests",
"type": "dart",
"request": "launch",
"program": "./test/"
},
{
"name": "Dart",
"type": "dart",
"request": "launch",
"program": "bin/main.dart"
},
{
"name": "Dart: Attach to Process",
"type": "dart",
"request": "attach"
},
{
"name": "Flutter",
"request": "launch",
"type": "dart"
}
]
}
Also, If you know any good alternatives to VSCode and Android Studio for Flutter, please share.
i came from mac and always use fn + f5, on windows that means start withouth debugggin, that was my mistake.
"version": "0.2.0",
"configurations": [
{
"name": "Flutter",
"request": "launch",
"type": "dart",
"flutterMode": "debug"
}
]
}
This is my launch.json file ... changing "flutterMode" from profile to debug solved the issue ... if you dont have this line adding it could help.
For anybody running into this problem while trying to debug external libraries or sdk code: Make sure you checked "Dart: Debug External Libraries" and "Dart: Debug Sdk Libraries" under Settings > Extensions > Dart & Flutter as described here.
You can also add the following to your settings.json
"dart.debugExternalLibraries": true,
"dart.debugSdkLibraries": true,
Clicking Run on the top menu in VS code and selecting 'Enable all breakpoints' worked for me. Though you have to place your breakpoint first.
You can also try placing your breakpoint and save your code, then leave the emulator running and close and restart your vs code IDE and run the app with debugging.
For flutter-web I had to change back to <base href="/"> within the web/index.html. A custom href lead to a none-debuggable project.
Navigate to the Run Tab and select Dart & Flutter from the drop down menu, finally hit the play button.
Your main.dart file's path is not specified right.
so in this block
"name": "Dart",
"type": "dart",
"request": "launch",
"program": "bin/main.dart"
please use
"program": "lib/main.dart"
I was also facing the same issue, I am looking for the exact reason but removing the launch.json file worked for me.
Have faced the same issue, resolved by stopping the current active session and click on RUN and select START DEBUGGING. This worked for me.
I faced the same problem with debug in certain dart files, but the other files I could.
Then I realized that it happened when I call another file and this trick would help:
Instead of typing:
import '../form/productdetail.dart';
I replaced with:
import 'package:myapp/form/productdetail.dart';
and it helped.
I had a similar problem. I solved by completely uninstalling and reinstalling Vscode + remove the data. See here
In my case, the parents folder contains special character (#):
.../#Projects/my_project/
Remove the # and the debug goes well:
.../Projects/my_project/
I had a similar problem. My platform is Ubuntu 20.04. I was setting the breakpoint in vscode expecting the vscode debugger to work immediately, but no. After an hour of googling, I hit the Flutter docs on the DevTools page.
To resolve :
Open your flutter project in vscode.
Follow the 'Install from VS Code' section of the docs to install DevTools.
Start your emulator, wait for it to completely load up.
Select Run => Start Debugging.
Check that app is running as expected in the emulator.
Select commandPalette => Dart:Open DevTools => 'Open DevTools in web browser'. The DevTools dashboard opens in a new browser tab.
Select the Debugger tab.
Open the relevent code file and add your breakpoint by clicking the leftmost breakpoint column at the required line.
Progress your app by clicking the emulator UI. Vscode debugger should stop at your breakpoint.
Use the vscode debugging controls thereafter.
Try to rebuild your launch.json file.
Remove the old file from the .vscode directory in vscode, then goto Run and Debug window and create a new launch file.