[Xamarin.Android.Build.Tasks] Updating NuGet packages does not update the app #7892
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #7890
We found and issue where if you upgraded a NuGet Package it did not up date the assemblies in the
$(IntermediateOutputPath)android\assets
folder. We have a unit test which checks this particular scenario, but it was disabled on .net during the port to .net 6. We never got back to enable it.The issue it turns out is that NuGet not longer populates the
ProjectLockFile
property. As a result we never stored the_NuGetAssetsTimestamp
in thebuild.props
file. This causes the_CleanIntermediateIfNeeded
target to be skipped when it really should run.Switching over to using the
ProjectAssetsFile
property to populate the_NuGetAssetsTimestamp
property fixes the issue. Also the unit test was updated to work on both Legacy and .net.