[0.4.12-pre] SKCanvasView Compile error
sk1llsh0t opened this issue · 8 comments
Description
Maybe you are already aware of this issue but after updating to 0.4.12-pre, I am getting a couple compile errors on Android. Downgrading back to 0.4.11 fixes the issue.
Expected Behavior
Successful compile
Actual Behavior
Error is thrown at compile time
Basic Information
- Version with issue: 0.4.12-pre
- Last known good version: 0.4.11
- IDE: JetBrains Rider
- Platform Target Frameworks:
- Android: 34
- Dotnet: 8.0.203
- Target Devices:
- Samsung XCover6 Pro
Screenshots
See screenshot of errors in Description
Make sure you have the latest version of Skiasharp, clean your bin and obj and restart VS, this is not an issue with the plugin but a issue on your machine
My project doesn't use skiasharp so I shouldn't have to install that package. I'll see if deleting everything in bin/obj folders fix the issue. I'll let you know.
Your project uses FreakyControls, hence it uses skiasharp indirectly, make sure you update it to the latest at times vs doesn't do it
I shouldn't have to maintain dependencies of dependencies. Then I need to keep track to the right versions of implicit dependencies to use for all my dependencies. It should implicitly pull in the right dependencies based on what is referenced. I shouldn't have to explicitly add a package to my project i'm not using directly. It is a recipe for disaster.
I found this article which is my exact issue.
dotnet/maui#19645
This project appears to have had the same issue: fdmomtaz/WeightTracker-DotNetMaui#1
They had to make some changes to the project to take care of this error as well.
Based on the weighttracker project mentioned above, he did the following commits to fix the issue...
fdmomtaz/WeightTracker-DotNetMaui@b096670
fdmomtaz/WeightTracker-DotNetMaui@4d1e1ba
If i have time, i'll fork your develop branch, add these changes and see if the problem goes away. I'll let you know if it works...
I shouldn't have to maintain dependencies of dependencies. Then I need to keep track of the right versions of implicit dependencies to use for all my dependencies. It should implicitly pull in the right dependencies based on what is referenced. I shouldn't have to explicitly add a package to my project I'm not using directly. It is a recipe for disaster.
As much as I agree there are times when this breaks and we have no control over this...