-
Notifications
You must be signed in to change notification settings - Fork 533
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
[Xamarin.Android.Build.Tasks] Crash when using NetStandard and Xamarin.Forms #850
Conversation
This should add a "test" to ensure that this fix works. See also: Commit: 0809427 Perhaps the test should simply be adding |
build |
Tests are in #846 |
build |
@jonpryor the APk Tests failing here seem to be SSL related and TimeZone related.. not sure they would be caused by this PR though. So I have no idea why they are happening.. |
build |
Might be the Locale tests |
…n.Forms Fixes https://bugzilla.xamarin.com/show_bug.cgi?id=57342 Commit 8f2ae24 attempted to fix this issue. However it made the assumption that `@(ReferenceCopyLocalPaths)` contained the same items as `@(ReferencePath)`. However it did not. So we should use a combination of the two to figure out what assmeblies are needed. We need to disgard reference assemblies though, we do this by checking for the appropriate attributes before we add the assembly to the list of items we want to package.
c5b3baf
to
cd358ec
Compare
@jonpryor fixed :) |
…n.Forms (#850) Fixes: https://bugzilla.xamarin.com/show_bug.cgi?id=57342 Commit 8f2ae24 attempted to fix this issue. However it made the assumption that `@(ReferenceCopyLocalPaths)` contained the same items as `@(ReferencePath)`. However it did not. So we should use a combination of the two to figure out what assmeblies are needed. We need to disgard reference assemblies though, we do this by checking for the appropriate attributes before we add the assembly to the list of items we want to package.
Fixes https://bugzilla.xamarin.com/show_bug.cgi?id=57342
Commit 8f2ae24 attempted to fix this issue. However it made the
assumption that
@(ReferenceCopyLocalPaths)
contained the sameitems as
@(ReferencePath)
. However it did not. So we should usea combination of the two to figure out what assmeblies are needed.
We need to disgard reference assemblies though, we do this by
checking for the appropriate attributes before we add the assembly
to the list of items we want to package.