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

The extended Splashscreen rendered with Skia shows the app logo with a bad resolution #16641

Closed
ArchieCoder opened this issue May 9, 2024 · 6 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

@ArchieCoder
Copy link
Contributor

Current behavior

Windows:
image

Linux
image

Expected behavior

Perfect output especially when a SVG is provided

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

Use this test project Test.zip

Workaround

No response

Works on UWP/WinUI

None

Environment

No response

NuGet package version(s)

No response

Affected platforms

Skia (WPF), Skia (Linux X11)

IDE

No response

IDE version

No response

Relevant plugins

No response

Anything else we need to know?

No response

@ArchieCoder ArchieCoder 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 May 9, 2024
@ArchieCoder ArchieCoder changed the title The extended Splashscreen rendered with Skia shows the app logo in bad resolution The extended Splashscreen rendered with Skia shows the app logo with a bad resolution May 9, 2024
@jeromelaban
Copy link
Member

This was fixed in 5.2.110 and later by #16519, could you give it a try? Also, you can generally try with the latest pre-release bits to check if something was updated.

@ArchieCoder
Copy link
Contributor Author

ArchieCoder commented May 9, 2024

Do I need to update manually the csproj?

image

@Youssef1313
Copy link
Member

@ArchieCoder You need to update the Uno.Sdk in global.json

@ArchieCoder
Copy link
Contributor Author

@jeromelaban
Copy link
Member

Updating the global.json is done with this. The global.json issue in VS is tracked here: NuGet/Home#13127

@ArchieCoder
Copy link
Contributor Author

5.2.110 didn't exist that's why VS was not working.

With the command "dotnet outdated", it said 5.2.112 is the nearest version.

Setting with this version, the original bug is fixed! 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

3 participants