Closed Osiris-Team closed 2 years ago
Thanks for the report! Was there any message showing up in the vscode output windows?
Oh dammn no clue, thats already one month ago.
Thanks anyways :) We'll look for it. Were you still able to move forward?
Nope had no clue how to fix it, thus dropped my hopes in uno.
Thanks. It seems that .NET and/or gitpod changed paths in between versions, causing this command to fail.
If you ever want to try it again, you can run the command manually this way ~/.dotnet/tools/uno-check
. Also, just so you know, you can still build apps without having uno-check running on gitpod, as all the dependencies are already setup.
Ah ok thanks!
Was following the steps for gitpod, and already failed at step 2. Was using crtl + shift + p to open the command pallete.