Skip to content
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

Uno-check 1.26.1.0 states there were a problem detected, but no problems are shown #18776

Closed
digger73 opened this issue Nov 13, 2024 · 7 comments
Labels
difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. kind/bug Something isn't working triage/untriaged Indicates an issue requires triaging or verification

Comments

@digger73
Copy link

digger73 commented Nov 13, 2024

Current behavior

Updated VS2022 (17.12.0) to newest release along with uno-check.
Running uno-check results in:
! There were one or more problems detected. Please review the errors and correct them and run uno-check again.

But no problems are shown during the checks. See below screenshot. Running uno-check again doesn't change the below result.

image

Expected behavior

If an problem is detected it would be shown by uno-check

How to reproduce it (as minimally and precisely as possible)

Update VS2022 to 17.12.0
Update uno-check to 1.26.1.0
Run uno-check, the described behavior occurs.

Workaround

No response

Works on UWP/WinUI

None

Environment

No response

NuGet package version(s)

No response

Affected platforms

No response

IDE

Visual Studio 2022

IDE version

17.12.0

Relevant plugins

No response

Anything else we need to know?

No response

@digger73 digger73 added difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. kind/bug Something isn't working triage/untriaged Indicates an issue requires triaging or verification labels Nov 13, 2024
@jeromelaban
Copy link
Member

Thanks for the report, can you run using --verbose ?

@digger73
Copy link
Author

digger73 commented Nov 13, 2024

Thanks for the report, can you run using --verbose ?

Just done that, which results in:

Install the [8.0.401] .NET SDK or update [C:\Users\dlerche.SUZLON\AppData\Local\Temp\uno-check-a749ae0e\global.json] to match an installed SDK.

Learn about SDK resolution:
https://aka.ms/dotnet/sdk-not-found
System.Exception: Workload command failed: `dotnet workload update --print-rollback`
  at async (ValueTuple<string, string, string>[[]] id) DotNetCheck.DotNet.DotNetWorkloadManager.GetInstalledWorkloads()
     in /_/UnoCheck/DotNet/DotNetWorkloadManager.cs:102
  at async Task<DiagnosticResult> DotNetCheck.Checkups.DotNetWorkloadsCheckup.Examine(SharedState history) in
     /_/UnoCheck/Checkups/DotNetWorkloadsCheckup.cs:95
  at async Task<int> DotNetCheck.Cli.CheckCommand.ExecuteAsync(CommandContext context, CheckSettings settings) in
     /_/UnoCheck/CheckCommand.cs:178
────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

Checkup had Error status: dotnetworkloads-8.0.401

dotnetworkloads-8.0.401: Workload command failed: `dotnet workload update --print-rollback`
! There were one or more problems detected.
Please review the errors and correct them and run uno-check again.

Press Enter to finish...

If have attached the comple uno-check with --verbose.
Uno Platform Check v1.26.1.log

@jeromelaban
Copy link
Member

Thanks. This explains the issue. .NET 9 has been released as part of 17.12, and .NET 8 is not present on your system anymore. We'll be publishing a new update of uno.check today, but in the meantime, can you try running:

dotnet tool update -g uno.check --version 1.27.0-dev.8

Then run uno-check again?

Thanks!

@digger73
Copy link
Author

Using the dev versio

Thanks. This explains the issue. .NET 9 has been released as part of 17.12, and .NET 8 is not present on your system anymore. We'll be publishing a new update of uno.check today, but in the meantime, can you try running:

dotnet tool update -g uno.check --version 1.27.0-dev.8

Then run uno-check again?

Thanks!

Using the dev version solved the problem, along with updating maui etc. to the newer released version from Microsoft :)

I guess I was to fast regarding updating VS to the new version. Thx.

@jeromelaban
Copy link
Member

Thanks for the update. When you're mentioning updating to the newer released version, do you mean as a nuget package reference?

@digger73
Copy link
Author

Did the visual studio update through VS Help->"check update" functionality in the VS UI.

@jeromelaban
Copy link
Member

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. kind/bug Something isn't working triage/untriaged Indicates an issue requires triaging or verification
Projects
None yet
Development

No branches or pull requests

2 participants