-
-
Notifications
You must be signed in to change notification settings - Fork 978
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
[Community Toolkit] Android Bug: "ReferencePath" does not define a value for metadata "CopyLocal" - Any thoughts or solutions? #2198
Comments
My experience with Stride has been purely Desktop but I did get a working version running in Android with just Stride a while ago.
@VaclavElias would you have any thoughts on why just adding the toolkit would introduce this dependancy? I can try to create an android example when I have time after work, I'm assuming its just some config issues since I dont think this should cause any new issues Stride didnt already have. |
I have no idea but toolkit is not using a regular Stride project configuration file, that means, Stride will skip certain If it is this case, it might be easy to find out, but one would need to debug Stride code with the example above and then it might be easty to initilize whatever is missing manually or we would need to put our heads together and find out what needs to be done in Stride code base itself :) Toolkit, code only part is still trying to figure out, what needs to be initiliazed so all works the same like from a regular Stride project 🤣. And it started from nothing and adding whatever is needed, whatever we find on the way.. |
The "CopyLocal" bug is a engine/build bug. This targets file (Stride.Core.PostSettings.Dependencies.targets) was changed from "CopyLocal" to "ReferencePath.CopyLocal" stride/sources/targets/Stride.Core.PostSettings.Dependencies.targets Lines 16 to 22 in 4a263c4
However, my understanding is this targets file (Stride.Core.targets) did not sync those changes stride/sources/core/Stride.Core/build/Stride.Core.targets Lines 137 to 147 in 4a263c4
As per the note directly above, it says "Important: Please keep in sync with Stride.Core.PostSettings.Dependencies.Targets" For an immediate workaround: Double clicking on those errors will open the targets file from the nuget package, then change the first %(CopyLocal) to %(ReferencePath.CopyLocal) and the second to %(ReferenceDependencyPaths.CopyLocal)
to
|
Nice work @Basewq! Are you working on a PR for this? If not I can create one.
Tagging @xen2 because this change was made in PR #1616, how in sync do we need to keep the two files? |
I'm not, feel free to make one. |
Fixed in #2220 |
Version
Release: Stride Community Toolkit NuGet 1.0.0-preview.20
Platform(s): Android
Context
I am attempting to create an integration pathway with Maui to allow crossplatform gaming for iOS/Android/Windows with Microsoft Maui as discussed here.
I am using the Community Toolkit as it can be added to an existing .NET 8 project with a simple NuGet. A code only approach should allow easy integration.
Bug
However, unfortunately, if I create a default Maui project in Visual Studio 2022 and add the Stride Community Toolkit NuGet, even with no other steps taken (not even using Stride, just add package), I can no longer build the project to Android.
Switching the build target to Android leads to Visual Studio reporting the following bug and refusing to build:
Given this is in
obj
I presume this has something to do with the Community Toolkit itself and something must be fixed inside there. Any thoughts?Screenshot
Screenshots

Repro Code
Repro Project
/~https://github.com/jonmdev/MauiStride
To Reproduce
Goal
Expected behavior
Need to be able to build to Android with Community Toolkit installed without error in order to continue integration attempts.
I am eager to try to make this a reality. Thanks for any help.
The text was updated successfully, but these errors were encountered: