Update Skia version to 1.68.1

[jairbubbles]

Please note that the NuGet package still needs to be generated and pushed to nuget.org. This PR is only the easy part :-D

I guess we'll need to wait on @EraYaN

Fixes #2

[jairbubbles]

Using docker to build was working fine but I first tried to use WSL which was way more complex and I ended up doing manually what was already done in the different scripts 😞

Anyway it's now compiling and I could generate the .nupkg properly.

Here it is (renamed as .zip): Jellyfin.SkiaSharp.NativeAssets.LinuxArm.1.68.1.zip

[jairbubbles]

@EraYaN can you push the package to NuGet ? (at least in beta so that we can test)

[manzajaro]

Hi,

I have the same issue #2 , How can I update jellyfin?

I have launched "compile-libSkiaSharp.sh" and "cross-compile-libSkiaSharp.sh" and both fail.

"./compile-libSkiaSharp.sh: line 13: /build/buildtools/linux64/gn: No such file or directory"
"./cross-compile-libSkiaSharp.sh: line 62: ./bin/gn: cannot execute binary file: Exec format error"

Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
aarch64

Thanks

[jairbubbles]

@manzajaro I would recommend to compile using docker by running build-in-docker.sh but obviously you need to install docker on your machine before.

[EraYaN]

I have asked @anthonylavado to upload the nupkg (since I can't myself), should appear somewhere this week.

[manzajaro]

Will it be available in the next jellyfin update?

[jairbubbles]

I have asked @anthonylavado to upload the nupkg (since I can't myself), should appear somewhere this week.

@EraYaN Cool, in the meatime I'll try to generate a local docker ARM image and make sure it does indeed fix the issue.

Will it be available in the next jellyfin update?

I certainly hope so!

[EraYaN]

It's validating now, should be up on NuGet within 24 hours.

[Juansero29]

I strangely had this problem too on version 1.68.1 with Xamarin.Forms on Visual Studio 2019 yesterday. I was deploying on a physical iPhone SE. Cleaning obj/bin on the .iOS project, then rebuilding, and redeploying did the trick!