-
Notifications
You must be signed in to change notification settings - Fork 528
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
Updating NuGet packages does not update the app #7890
Labels
Area: App+Library Build
Issues when building Library projects or Application projects.
Comments
mattleibow
added
Area: App+Library Build
Issues when building Library projects or Application projects.
needs-triage
Issues that need to be assigned.
labels
Mar 16, 2023
Oh snap, this test is disabled in .NET 6+: It must have been broken because it uses Xamarin.Forms. So something maybe has been wrong here since .NET 6? |
I'll update that test to make use of say NewtonSoft.Json it probably doesn't need to be Xamrain.Forms |
dellis1972
added a commit
to dellis1972/xamarin-android
that referenced
this issue
Mar 17, 2023
… the app Fixes dotnet#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 the `build.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.
dellis1972
added a commit
to dellis1972/xamarin-android
that referenced
this issue
Mar 20, 2023
… the app Fixes dotnet#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 the `build.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.
dellis1972
added a commit
that referenced
this issue
Mar 21, 2023
… the app (#7892) 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 the `build.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.
ghost
locked as resolved and limited conversation to collaborators
Apr 20, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Android application type
.NET Android (net7.0-android, etc.)
Affected platform version
All
Description
I have noticed that when I update nugets in my maui app, the dll updates do not reach the final device.
Steps to Reproduce
I have a GitHub Action here with a test case script:
The output of 7. is still 13.0.1
Did you find any workaround?
Rebuild
Relevant log output
The text was updated successfully, but these errors were encountered: