Breakpoints for Flutter are broken - flutter-web

I've been trying to get breakpoints to function in VS Code. I'm on the latest version of the stable channel of Flutter, as well as VS Code and the extensions for Dart and Flutter.
I know this question has been asked and answered several times, but all those answers have just been voodoo fixes. Thus I ask again, as none worked for me.
Yes I'm doing F5 and not Ctrl+F5. Yes I tried reinstalling the extensions and VS Code and flutter and Windows.
Yes the breakpoints still become unverified as soon as VS Code connects to chrome. My project is web-only.
I know this is an unfixable issue and that even though its been fixed multiple times on github.

Yup, currently its a bug. Follow this issue for updates.

Related

Can't use specific Icons in imported flutter project

this might be a quick one.
I've imported a Flutter project which a colleague created via VS Code into Android Studio (via Git - Bitbucket).
(I've worked on another new Flutter project just this day.)
The problem is: some icons he used aren't found by the compiler for me.
Examples of working icons:
Icons.pregnant_woman
Icons.person
Icons.calendar_today
Not working:
Icons.qr_code
Icons.biotech
Also, no matter in which file I'm in, there's a hint window above stating: 'Pub get' has not been run and I get the option to run get dependencies (pub get) or upgrade dependencies (pub upgrade).
When I first imported the project, the compiler didn't even know what Flutter is. After I executed pub get the first time, most of the errors were gone. The only ones missing are the few icons. But the hint saying I didn't do pub get is still there which was never like this in my other projects.
What can I do?
Btw, pub outdated says dev_dependencies: all up-to-date and
Dependencies are all on the latest resolvable versions.
Newer versions, while available, are not mutually compatible.
I run into this problem a while ago. The way I managed to solve it is:
go to Vs code setting and search flutter create and disable Flutter Create Offline
I hope this is helpful!
Got it! Turns out I changed some internal flutter file some while back and it wouldn't upgrade the flutter version automatically until I did "flutter upgrade -force".

Intellisense problems with node.js development with Visual Studio 2017

Usually we're in a microsoft stack development but for the project purposes we need to develop in node.js in visual studio 2017.
There are some things we don't understand at all but are quite annoying.
We've installed node.js tools for Visual Studio 2017 but intellisense work for some things and doesn't for others.
2 main problems we're facing:
For example, for some node modules (router, express, etc...) intellisense works fine. For others (mongorito, for examlple, but its not mongorito specific, there are many others also) we don't get any intellisense nor we can navigate through its definitions ('go to definition').
For any file we open we get alot of TSxxx error messages. something like this:
Don't know if its important but with the same setup we had our team members to work on angular 2/4 projects (that use node modules, of course) and everything worked fine.
So, if anyone has a piece of advice we would highly appreciate it. And please explain it like for a complete idiots.
PS.
Don't know if its important, but i must say that solution builds, all tests are good and all runs as it should. Its IDE problem.
So, for everyone having the problem i'll post the solution here.
Problem was in typescript version. Now, that comes with a few details.
In Visual studio pre 15.2 you can't have typescript versions switching. So, i first updated VS to 15.2.
After that, i've installed Typescript SDK with latest typescript (2.4.1. i think at the moment).
Then go to Tools > Options > TextEditor > Javascript/Typescript > Intellisense > Here choose typescript version from the drop down.
[I'll leave answer unaccepted for a bit for the case someone comes with a better solution]

Same code from support7Demos behaves different on different devices on AppCompat DayNight Mode 23.2.0

I have downloaded the Android Support 23.2.0 and imported support7Demos under directory /Android/sdk/extras/android/support/samples/Support7Demos without making any changes. After importing the necessary dependencies, it builds successfully and generate an apk. I installed the apk on Smartisan T1 with API 19. The day night mode works as expected. But it does not work on Nexus 5 with API 23.
Please be noticed that the code is from the Android official Support V7 sample, I did not make any changes at all.
The same apk installed on different devices work different.
This is the link to download the apk to check it out.
You could also check out the two videos that recorded to see the difference.
Is it a bug? And if it is a bug, is there any workaround?
To those who still wonders the answer, here it is :
It's issue with AppCompatActivity.java of support library which is fixed now.
It is the official answer quoted from the bug logged in here

How to completely remove dottrace

Currently I have licenses for the following JetBrains products:
ReSharper 8.2.0.2160
Dotcover 2.7.1.238
I recently needed to use Dottrace, so installed the latest version from the JetBrains website. However I found this is incompatible with the other, earlier products, so uninstalled it.
Except it didn't uninstall properly. I still see dottrace menus, which still appear to function, and ReSharper is still broken. I have tried completely uninstalling and then re-installing Visual Studio (together with resharper and dotcover), yet this has still not improved anything. I still see Dottrace menus and ReSharper is still broken.
I've tried the JetBrains support forums (https://devnet.jetbrains.com/message/5536694#5536694), but they have not been helpful. Has anyone here experienced a similar issue, or have ideas as to how it can be resolved?
I'm starting to get desperate. Is there any way I can fix my development environment short of completely re-installing windows?
The problem was solved by JetBrains support. In case anyone else has the same issue, all you need to do to solve it, is to delete the directory:
C:\Users[user_name]\AppData\Local\Microsoft\VisualStudio[version_number]\Extensions\JetBrains

The parameter is incorrect

When I try to add a service reference to my project in Visual Studio I keep getting the error " The parameter is incorrect" I know it's not the code because it doesn't happen on my coworkers computer. I have uninstalled and reinstalled Visual Studio to see if the problem is with my installation. But that doesnt seem to fix it.
I am using visual Studio 2012.
Did anyone come across this issue before? Please help!
I had this problem with a project that was copied out of ClearCase. the .csproj file still had the reference telling visual studio that its still under CC. I removed the following references and it worked.
<SccProjectName>Rational ClearCase</SccProjectName>
<SccLocalPath>Rational ClearCase</SccLocalPath>
<SccAuxPath>Rational ClearCase</SccAuxPath>
<SccProvider>Rational ClearCase</SccProvider>
I had the same issue after updating SQLite plugin for windows phone.
It seems like the sqlite-net-wp8 project (which is a wrapper to work with the plugin) had some import method from that plugin and when the version changed the wrapper didn't work anymore.
The solution was to downgrade the sqlite plugin to a version that is compatible with the wp8 wrapper.
Edit: The wrapper had an update so I've upgraded both the plugin and wrapper and now the issue is fixed.
If it shows any project in your solution with "(failed)" next to it's name try to remove it and re-add it to your solution and it will tell you what the issue exactly is.
In addition to Frisons answer - the issue works aswell the other way round:
If you are using ClearCase, make sure that the entries mentioned by Frison are available in your project file. I just had this case that one of the projects in my solution did not (however) had these entries and i got the very same error. Adding these lines fixed this issue for me.
I got the same error for WindowsPhone project, after make a clear manifest the error disappeared.

Resources