mono / SkiaSharp

SkiaSharp is a cross-platform 2D graphics API for .NET platforms based on Google's Skia Graphics Library. It provides a comprehensive 2D API that can be used across mobile, server and desktop models to render images.
MIT License
4.56k stars 543 forks source link

Can't build for iOS with Xamarin Forms[BUG] #1702

Closed Pequeno0 closed 3 years ago

Pequeno0 commented 3 years ago

Description

Including SkiaSharp in the Xamarin forms project, Windows paired to a Mac, then trying to build yields the following error:

1>C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Xamarin\iOS\Xamarin.Shared.targets(975,3): error : DirectoryNotFoundException: Could not find a part of the path '/Users//Library/Caches/Xamarin/mtbs/builds/TestiOSBuildApp.iOS/8c512dc4f4826b88a51c8798b7f65927dc2afe3d8cd845a563df3fddd5f3932e/bin/iPhone/Debug/TestiOSBuildApp.iOS.app/Frameworks/libSkiaSharp.framework/_CodeSignature'.

which means it won't build the app.

It seems this _CodeSignature is not copied from the nuget package for some reason?

Code

Make a new Xamarin Forms project in Visual Studio, get the SkiaSharp package from Nuget, pair to a mac from your PC, build, see the the failure.

Expected Behavior

The _CodeSignature folder should exist.

Actual Behavior

_CodeSignature folder is missing, and the the build fails.

Basic Information

taublast commented 3 years ago

Been fighting this few days, thought that was coming from my settings. But after reformatting reinstalling Mac from scratch and having set up all the certificates again, it's the same: it's compiling-signing ok for real device until i add SkiaSharp nuget. This appeared after upgrading to XCode 12.5. Still don't know if this is a new apple's requirement for third-party libs to be imperatively signed OR a visual studio build bug OR xcode bug.. Any thoughts?

My error:

MessagingRemoteException: An error occurred on client Build169000292 while executing a reply for topic xvs/build/execute-task/XamarinTestApp.iOS/31c782e002fCodesign AggregateException: One or more errors occurred. DirectoryNotFoundException: Could not find a part of the path '/Users/Airboom/Library/Caches/Xamarin/mtbs/builds/XamarinTestApp.iOS/31c782e90715fd993ed01e15963fc6f699e2dc9661442e7b92edfc01c6ad08cb/bin/iPhoneSimulator/Debug/XamarinTestApp.iOS.app/Frameworks/libSkiaSharp.framework/_CodeSignature'. XamarinTestApp.iOS

This is a very urgent matter..

Grzesik commented 3 years ago

Hi, I have the same problem! I have two projects with SkiaSharp on two comupters and I get the same error in iOS project. Android works. I noticed also, that the common Project shows following warning: warning NU1701: Package 'SkiaSharp.Views 2.80.2' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8' instead of the project target framework '.NETStandard,Version=v2.0'. This package may not be fully compatible with your project.

I deletes all Nuget packages and reinstalled them in the project. Nothing helps.

Thanks

mrutter commented 3 years ago

Hello everybody.

I have exacty the same issue here, trying to run the iOS emulator from Visual Studio (Windows) paired with the Mac. The weird thing is that if I compile/debug from Visual Studio for Mac, everything works fine.

Right now I'm not able to debug from Visual Studio and I have to work on Mac :(

Thank you. -marcello

EDIT Please note that this issue can be related to this issue with Xamarin.iOS

monster74 commented 3 years ago

Hello. I have the same problem with SkiaSharp after updating xcode 12.5 and VS 16.9.5. DirectoryNotFoundException: Could not find a part of the path '/Users/xxxxxx/Library/Caches/Xamarin/mtbs/builds/App.iOS/6635a42b07b773f91fc2b39356bd40a5a6aa09cd70010ccd9d3e89de3a4c1a2a/bin/iPhone/Debug/device-builds/iphone9.3-14.5.1/App.iOS.app/Frameworks/libSkiaSharp.framework/_CodeSignature'. Projects without SkiaSharp build normally.

taublast commented 3 years ago

Additional info after installing VS 16.10.0 preview 4 + Xamarin.iOS '14.19.0.7'

(deleted ~\AppData\Local\Xamarin\iOS\Caches and ~\AppData\Local\Temp\Xamarin\XMA)

  1. VS 16.9.6 + Xamarin.iOS '14.19.0.7 = same issue as above

  2. VS 16.10.0 preview 4 + Xamarin.iOS '14.19.0.7' =

Compiling signing from Windows finishes without errors, when trying to deploy to:

a - simulator: fails without any error description b - real device: fails with:

error MT1006: Could not install the application '/Users/Airboom/Library/Caches/Xamarin/mtbs/builds/XamarinTestApp.iOS/31c782e90715fd993ed01e15963fc6f699e2dc9661442e7b92edfc01c6ad08cb/bin/iPhone/Debug/XamarinTestApp.iOS.app' on the device 'iPhone nicky': Package Inspection Failed Error (error: 0xe8000051).

PackageInspectionFailed: Failed to load Info.plist from bundle at path /private/var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.08ASXq/extracted/XamarinTestApp.iOS.app/Frameworks/libSkiaSharp.framework``

Well to me it looks like a Visual Studio for Windows bug. Agree?

peder1896 commented 3 years ago

Hi I have the same problem I can deploy from Visual Studio for Mac 8.9.10 (build 4) but not from Visual Studio 16.9.6 I then get the foolowing error: MessagingRemoteException: An error occurred on client Build169000294 while executing a reply for topic xvs/build/execute-task/xxxxxx.iOS/05a14ae002fCodesign AggregateException: One or more errors occurred. DirectoryNotFoundException: Could not find a part of the path '/Users/xxxxxxx/Library/Caches/Xamarin/mtbs/builds/xxxxxx.iOS/05a14ae99af88b6e851484e35f30dfcb0d88549771d3e6791c11d2d825147791/bin/iPhone/Debug/xxxxxxx.iOS.app/Frameworks/libSkiaSharp.framework/_CodeSignature'

cbs-cbt commented 3 years ago

Hello, Same problem here. Tried with a brand new Xamarin.Forms solution. As soon as SkiaSharp.Views.Forms NuGet package is added to the solution iOS project won't compile. But downgrading to SkiaSharp.Views.Forms version 1.68.3 will work again

gureAngel commented 3 years ago

Hello, Same problem here. Tried with a brand new Xamarin.Forms solution. As soon as SkiaSharp.Views.Forms NuGet package is added to the solution iOS project won't compile. But downgrading to SkiaSharp.Views.Forms version 1.68.3 will work again

I tried downgrading the version to 1.68.3 and it still doesn't work.

In the emulator does not give me any error, but when I want to run it on the physical device I still have the same error:

MessagingRemoteException: An error occurred on client Build169000294 while executing a reply for topic xvs/build/execute-task/xxxxxxxxxxxx.iOS/ed22858002fCodesign AggregateException: One or more errors occurred. DirectoryNotFoundException: Could not find a part of the path '/Users/xxxx/Library/Caches/Xamarin/mtbs/builds/xxxxxxx.iOS/xxxxxxxxxx/bin/iPhone/Debug/xxxxxxxx.iOS.app/Frameworks/libSkiaSharp.framework/_CodeSignature'.

cbs-cbt commented 3 years ago

I tried downgrading the version to 1.68.3 and it still doesn't work.

In the emulator does not give me any error, but when I want to run it on the physical device I still have the same error:

MessagingRemoteException: An error occurred on client Build169000294 while executing a reply for topic xvs/build/execute-task/xxxxxxxxxxxx.iOS/ed22858002fCodesign AggregateException: One or more errors occurred. DirectoryNotFoundException: Could not find a part of the path '/Users/xxxx/Library/Caches/Xamarin/mtbs/builds/xxxxxxx.iOS/xxxxxxxxxx/bin/iPhone/Debug/xxxxxxxx.iOS.app/Frameworks/libSkiaSharp.framework/_CodeSignature'.

Hello gureAngel, Indeed I haven't tried it on a physical device, it sure doesn't work. Thank you for trying

dmsi-leonidl commented 3 years ago

Hi there,

Having the same issue with SkiaSharp.Views.Forms 2.80.2. iOS build failed with the error: DirectoryNotFoundException: Could not find a part of the path '/Users/developer/Library/Caches/Xamarin/mtbs/builds/MInspect.iOS/3f461d8a077ea1533355063303276a96508c09fa0c4d9422a2d65b43a569ef81/bin/iPhone/Debug/MInspect.iOS.app/Frameworks/libSkiaSharp.framework/_CodeSignature'.

VS 2019 16.9.6 XF v5.0.0.2012

Works fine if I rolled back SkiaSharp.Views.Forms to v1.68.3.

Thanks

taublast commented 3 years ago

Can confirm it compiles, signs and deploys OK on real iPhone with an older SkiaSharp.Views.Forms v1.68.3 🙉

Tested with VS 16.9.6 + Xamarin.iOS '14.19.0.7 + XCode 12.5

The interesting part is that the latest SkiaSharp.Views.Forms 2.80.2 nuget was causing no trouble before we upgraded to latest XCode and latest VS..

gureAngel commented 3 years ago

Downloading the project, reloading it, downgrading the version to 1.68.3, it worked again.

IGx89 commented 3 years ago

In case it helps, I ran into the exact same issue with https://www.nuget.org/packages/Xamarin.Google.iOS.Cast/. Strange thing is, I was on 16.9.6 and it was working, but after upgrading to 16.10.0 and downgrading back to 16.9.6 (due to another Xamarin bug) this issue started happening. Could have been triggered by me clearing cache/build folders as part of the upgrade/downgrade.

ahoke-cr commented 3 years ago

I had this issue pop up randomly today when trying to deploy to my iPhone instead of the Simulator. Now I cannot fix it.

taublast commented 3 years ago

After upgrading Visual Studio to 16.10.0 + Xamarin.iOS 14.20.0.1 it finally builds and signs ok, from Windows, using SkiaSharp.Views.Forms 2.80.2.

EDITED: Forgot to delete bin obj after replacing old nuget, it's still not deploying with lastest skia.. "PackageInspectionFailed: Failed to load Info.plist from bundle"

joehanna commented 3 years ago

I have the same problem on VS Mac (latest version) but I don't even use SkiaSharp. Release mode is fine on both simulator and device, but not Debug. Wondering if it is not related to SkiaSharp at all.

ahoke-cr commented 3 years ago

I have the same problem on VS Mac (latest version) but I don't even use SkiaSharp. Release mode is fine on both simulator and device, but not Debug. Wondering if it is not related to SkiaSharp at all.

If you delete the build folder for release I think you will encounter the issue on release as well. It only started happening after I cleared my build folder when trying to fix another issue.

boris-df commented 3 years ago

Same Issue:

Just create a new App-Project (for example with the tabbed app template)

Now add SkiaSharp Package Version 2.x upwards

When you change the SkiaSharp Package to Version 1.68.3 - Die app compiles and starts again.

FWIW - VS 16.10 seems to have it's own bugs too! So I see that the apps doesn't have icons anymore and someone wrote, that the cannot upload Builds to Apple anymore because of this (see: https://developercommunity.visualstudio.com/t/Cant-deliver-to-the-appstore-since-last/1436223)

I don't know if this has to do with the problems we see with skiasharp 2.x currently

ysmoradi commented 3 years ago

16.11 Preview 1 Xamarin iOS 14.20.0.1 XCode 12.5 (12E262)

The same issue )":

Elinareso commented 3 years ago

Same issue after upgrade x-Code to 12.5 and VS 16.10, Skia 2.80.0

Severity Code Description Project File Line Suppression State Error MessagingRemoteException: An error occurred on client Build169000292 while executing a reply for topic xvs/build/execute-task/ProjectName/c8561a8002fCodesign AggregateException: One or more errors occurred. DirectoryNotFoundException: Could not find a part of the path '../c8561a8a7bfbc1a65b4c3ab6271481afb331465d1040423802a41c646a20d0bc/bin/iPhone/Debug/device-builds/iphone10.2-14.4.2/../Frameworks/libSkiaSharp.framework/_CodeSignature'.

ysmoradi commented 3 years ago

16.11 Preview 1 Xamarin iOS 14.20.0.1 XCode 12.5 (12E262)

The same issue )":

Note that on the same macos machine that I connect to it while developing iOS apps, I've installed the latest stable version of vs for mac, and vs for mac is able to build / run the exact same project successfully.

MDGMDGMDG commented 3 years ago

Uninstalling nuget packages v. 2.80.2 of SkiaSharp, SkiaSharp.Views and SkiaSharp.Views.Forms and reinstalling v. 1.68.3 I was able to build run debug on Simulator (only directly on the Mac server).

Visual Studio 2019 16.10 Xcode 12.5 Xamarin iOS 14.20.0.1

taublast commented 3 years ago

If one inspects the content of nugets the main difference between 2.80.2 (fails) and 1.68.3 (works) is that the first one is including native framewok with appropriate plist, the latter does not, explaining why it works. Talking about the not working version while with the latest Xamarin.iOS it compiles, it fails to deploy with a "PackageInspectionFailed: Failed to load Info.plist from bundle". Searching web about it have found two main possible causes:

1 Multi-targeting - "Each probject has its own info.plist file. One of them was being copied into the bundle, causing the issue.") cause: (https://developer.apple.com/forums/thread/22330). Maybe it's skia sharp nuget project that has invalid settings (that became incompatible with newest xcode) of some new microsoft code is causing this incorrect behavior.

2 Duplicated framework in the compiled binaries, maybe from skia config, maybe cause of MS linker: https://stackoverflow.com/questions/40327935/failed-to-load-info-plist-from-bundle

Any thoughts about this direction?

nowlights commented 3 years ago

Hello,

same problem here with SkiaSharp on Windows...

on mac i can debug normally

Rippletank commented 3 years ago

Just to add another data point, this bug blocks deployment of Release builds for me on actual device with the PackageInspectionFailed error. But I don't get the error with a development key using a debug configuration build. I have separate development and deployment keys installed both pointing to the same app id. This is from both PC and using VS for mac.

There's been a wave of bugs I've had to wade through since starting on ios testing, was hopeful that another plist related bugfix ( https://developercommunity.visualstudio.com/t/XamarinForms-ios:-IOException:-Sharing-/1355811 ) was going to fix it but still there's this issue with distribution builds.

Has anyone had any luck with preview releases of skiasharp? They seem to be quite regular.

ahoke-cr commented 3 years ago

Has anyone had any luck with preview releases of skiasharp? They seem to be quite regular.

@Rippletank I ended up downgrading to SkiaSharp 1.68.0 in my iOS project while keeping the shared project and Android project at 2.80.2.

Toine-db commented 3 years ago

When I downgrade to Svg.Skia using SkiaSharp 1.68.x then it works fine on the emulator. If I upgrade afterwards to 2.80.2 SKaiSharp the debug for emulators work fine as well.

But when I try to build 2.80.2 debug for a real iPhone everything goos wrong, from that point the emulator doesnt work any more....untill I downgrade and upgrade to 2.80.2 again... strange

So I can develop, but I can not build releases anymore because the need to be build on iPhone device configuration... :-(

nelutzu91 commented 3 years ago

@Toine-db and all others what have issues.... Downgrading to VS 16.9.2 worked for me. I was able to debug ios emulator, ios physical device. In my environment, I have VS professional 16.10, where I code... and VS enterprise 16.9.2 where I build iOS :D PS: if you want to spend some time, you can try downgrading VS one version at a time, maybe you find a newer version than 16.9.2 which works. Since I only tried 16.9.6 which didn't work and then I switched to 16.9.2, which worked for me before.

Hope this helps.

Toine-db commented 3 years ago

@Toine-db and all others what have issues.... Downgrading to VS 16.9.2 worked for me. I was able to debug ios emulator, ios physical device. In my environment, I have VS professional 16.10, where I code... and VS enterprise 16.9.2 where I build iOS :D PS: if you want to spend some time, you can try downgrading VS one version at a time, maybe you find a newer version than 16.9.2 which works. Since I only tried 16.9.6 which didn't work and then I switched to 16.9.2, which worked for me before.

Hope this helps.

What version of Skiasharp are you using? Because I already downgraded to Vs 16.9.2, and debug on emulator only works but not on real devices.

dmsi-leonidl commented 3 years ago

Latest VS 2019 (16.10.2) update seems to fix the issue. I updated SkiaSharp.Views.Forms to 2.80.2 and was able build and deploy iOS project.

nelutzu91 commented 3 years ago

@Toine-db and all others what have issues.... Downgrading to VS 16.9.2 worked for me. I was able to debug ios emulator, ios physical device. In my environment, I have VS professional 16.10, where I code... and VS enterprise 16.9.2 where I build iOS :D PS: if you want to spend some time, you can try downgrading VS one version at a time, maybe you find a newer version than 16.9.2 which works. Since I only tried 16.9.6 which didn't work and then I switched to 16.9.2, which worked for me before. Hope this helps.

What version of Skiasharp are you using? Because I already downgraded to Vs 16.9.2, and debug on emulator only works but not on real devices.

SkiaSharp.Views.Forms 2.80.2 :)

Toine-db commented 3 years ago

@Toine-db and all others what have issues.... Downgrading to VS 16.9.2 worked for me. I was able to debug ios emulator, ios physical device. In my environment, I have VS professional 16.10, where I code... and VS enterprise 16.9.2 where I build iOS :D PS: if you want to spend some time, you can try downgrading VS one version at a time, maybe you find a newer version than 16.9.2 which works. Since I only tried 16.9.6 which didn't work and then I switched to 16.9.2, which worked for me before. Hope this helps.

What version of Skiasharp are you using? Because I already downgraded to Vs 16.9.2, and debug on emulator only works but not on real devices.

SkiaSharp.Views.Forms 2.80.2 :)

Thanks, I just noticed I was using 16.9.6 instead of 16.9.2, seems this is what Im going todo today ;-)

Toine-db commented 3 years ago

@nelutzu91 You are a lifesaver, because of your comment I noticed the slight version difference and downgraded further from 16.9.6 to 16.9.2. and now everything works with Svg.Skia using SkiaSharp 2.80.2

Emulators, real devices and even building releases and creating archives.

Thanks!

reinhardsual commented 3 years ago

Latest VS 2019 (16.10.2) update seems to fix the issue. I updated SkiaSharp.Views.Forms to 2.80.2 and was able build and deploy iOS project.

It does fix the issues for me. (16.10.2)....

Magendanz commented 3 years ago

I get the following in my build log, but I believe it's the same issue. Icon issues are resolved with VS 2019 16.10.2, but this remains.

PackageInspectionFailed: Failed to load Info.plist from bundle at path /var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.iyFP2M/extracted/TRF.iOS.app/Frameworks/libSkiaSharp.framework; Extra info about "/var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.iyFP2M/extracted/TRF.iOS.app/Frameworks/libSkiaSharp.framework/Info.plist": Couldn't stat /var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.iyFP2M/extracted/TRF.iOS.app/Frameworks/libSkiaSharp.framework/Info.plist: No such file or directory

If I try to upload to the App Store, I get this:

"altool" exited with code 1.
Invalid Bundle Structure - The binary file 'TRF.iOS.app/Frameworks/libSkiaSharp.framework/libSkiaSharp' is not permitted. Your app can’t contain standalone executables or libraries, other than a valid CFBundleExecutable of supported bundles. Refer to the Bundle Programming Guide at https://developer.apple.com/go/?id=bundle-structure for information on the iOS app bundle structure.
Toine-db commented 3 years ago

I get the following in my build log, but I believe it's the same issue. Icon issues are resolved with VS 2019 16.10.2, but this remains.

PackageInspectionFailed: Failed to load Info.plist from bundle at path /var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.iyFP2M/extracted/TRF.iOS.app/Frameworks/libSkiaSharp.framework; Extra info about "/var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.iyFP2M/extracted/TRF.iOS.app/Frameworks/libSkiaSharp.framework/Info.plist": Couldn't stat /var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.iyFP2M/extracted/TRF.iOS.app/Frameworks/libSkiaSharp.framework/Info.plist: No such file or directory

If I try to upload to the App Store, I get this:

"altool" exited with code 1.
Invalid Bundle Structure - The binary file 'TRF.iOS.app/Frameworks/libSkiaSharp.framework/libSkiaSharp' is not permitted. Your app can’t contain standalone executables or libraries, other than a valid CFBundleExecutable of supported bundles. Refer to the Bundle Programming Guide at https://developer.apple.com/go/?id=bundle-structure for information on the iOS app bundle structure.

Try using VS 16.9.2

ahoke-cr commented 3 years ago

I updated to 16.9.10 but am now unable to deploy to either the simulator or a physical iPhone. I'm getting a package inspection error when deploying to a physical phone, and no specific error when deploying to the simulator. This is incredibly frustrating and I'm losing dev time trying to fix these issues that should not be issues.

ahoke-cr commented 3 years ago

Try using VS 16.9.2

@Toine-db where did you find the installer for 16.9.2? I can only find it for 16.9.10.

nelutzu91 commented 3 years ago

Try using VS 16.9.2

@Toine-db where did you find the installer for 16.9.2? I can only find it for 16.9.10.

@ahoke-cr , https://docs.microsoft.com/en-us/visualstudio/releases/2019/history#release-dates-and-build-numbers Unfortunately you cannot install community version, only Enterprise or Professional.

In my environment, I installed professional for dev and enterprise for building apple stuff :)

Magendanz commented 3 years ago

Try using VS 16.9.2

Note that there's no easy roll-back feature with VS. You need to uninstall the current release and then do a clean install of the archived release, losing many of your configuration settings and cached credentials in the process. Frankly, I'm not willing to risk destabilizing a dozen other projects that I maintain on this workstation just to work around this bug. At this point I'm trying to scrounge up another build machine...or build in AppCenter.

Toine-db commented 3 years ago

Try using VS 16.9.2

Note that there's no easy roll-back feature with VS. You need to uninstall the current release and then do a clean install of the archived release, losing many of your configuration settings and cached credentials in the process. Frankly, I'm not willing to risk destabilizing a dozen other projects that I maintain on this workstation just to work around this bug. At this point I'm trying to scrounge up another build machine...or build in AppCenter.

You are absolutely right, but because of to much issues with Vs in the past I kept all my VS install very basic with only resharper. All other tools I use are not connected to VS anymore.

dmsi-leonidl commented 3 years ago

@Magendanz

Try using VS 16.9.2

Note that there's no easy roll-back feature with VS. You need to uninstall the current release and then do a clean install of the archived release, losing many of your configuration settings and cached credentials in the process. Frankly, I'm not willing to risk destabilizing a dozen other projects that I maintain on this workstation just to work around this bug. At this point I'm trying to scrounge up another build machine...or build in AppCenter.

I am not sure if this can help but if your app is XF and not Xamarin.iOS try to remove unnecessary SkiaSharp references from all platform specific projects. In my case doing that and updating VS 2019 to the latest build along with updating all Nuget packages fixed all iOS deployment issues.

Magendanz commented 3 years ago

I am not sure if this can help but if your app is XF and not Xamarin.iOS try to remove unnecessary SkiaSharp references from all platform specific projects. In my case doing that and updating VS 2019 to the latest build along with updating all Nuget packages fixed all iOS deployment issues.

I actually tried that yesterday, but the shared library in my XF project needs a Nuget package with a dependency on SkiaSharp and SkiaSharp.Views.Forms 2.80.2 or higher. Even though SkiaSharp isn't explicitly installed or referenced in the iOS platform project, it still gets linked in.

ahoke-cr commented 3 years ago

Instead of downgrading from VS 16.10.2, I have maintained a reference to SkiaSharp 1.68.2 exclusively in my iOS-specific project. Android and the shared Xamarin project continue to reference SkiaSharp 2.80.2. I also had ARMv7s in my iOS Build under Supported Architectures which was causing issues with SkiaSharp, so my app is now only targeting ARMv7 + ARM64.

Maybe we can get a package update that actually fixes this issue for everyone instead of being forced to hack around a bad package release.

ojuniour commented 3 years ago

yep. I don't have SkiaSharp installed and for some reason it is still getting referenced in relation to the error.

ahoke-cr commented 3 years ago

@ojuniour make sure you are clearing build caches on both your Mac build host and your dev machine. After that, clean and rebuild the solution.

ojuniour commented 3 years ago

@ojuniour make sure you are clearing build caches on both your Mac build host and your dev machine. After that, clean and rebuild the solution.

What's the most effective way of clearing out cache on the Mac if I'm connecting my build through VS on windows.

ahoke-cr commented 3 years ago

@ojuniour I use Google Remote Desktop to remotely connect to my Mac build host. You can also use SSH to execute commands on your Mac. More details here

ojuniour commented 3 years ago

@ojuniour I use Google Remote Desktop to remotely connect to my Mac build host. You can also use SSH to execute commands on your Mac. More details here

Clearing both caches don't work either.

ahoke-cr commented 3 years ago

Clearing both caches don't work either.

@ojuniour I would manually check your csproj files for any references, as well as verifying that you don't have any other packages that also reference SkiaSharp. Make sure you're clearing your bin and obj folders in your Xamarin iOS platform project. You can also go to AppData folders and remove the package caches to ensure that there's no way the SkiaSharp.dll could be referenced during build.