-
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
MSBuild:UpdateGeneratedFiles takes 40 seconds for a single layout file change #4273
Comments
@cosminstirbu at the first sight, it seems your issue might be similar to #4095, can you check if the information provided there helps you? |
I had a look at that issue which suggests that there might be some missing However, if I search the log of
Just to make it as clear as possible - the issue happens when I update a layout file and save the change (which triggers "Updating resources ..." |
I feel you.. It is a real pain compared to how gradle works for example. I feel like this is not something that can be fixed for larger projects unless they change the tool.. |
@grendello - any news on this issue? I know you guys are busy with plenty of stuff but I feel that build performance (and other developer productivity areas) should be high priority. Thanks, |
@cosminstirbu I'm sorry, we really have a lot on our hands right now, but it's not an excuse to not take care of all the issues. Can you attach a binlog of the build which takes such a long time for you? (build with |
I've attached a (private) verbose tex log in the initial ticket. If you don't have access to it, then please give me an email address where I can send you the verbose text log as it contains private information. Also please notice that I'm not invoking an actual build action - I'm simply editing a layout .xml file and I hope the text log is good enough, if not, if you can provide some guidance on how I can invoke |
This issue will be fixed via #4190 One of the problems was we were not using the incremental capabilities of |
Thank you for your updates. Looking forward to see this fix in a near future stable version of Xamarin.Android. |
Release status update A new Preview version has now been published that includes the fix for this item. The fix is not yet included in a Release version. I will update this again when a Release version is available that includes the fix. Fix included in Xamarin.Android 10.3.99.230. Fix included on Windows in Visual Studio 2019 version 16.7 Preview 1. To try the Preview version that includes the fix, check for the latest updates in Visual Studio Preview. Fix included on macOS in Visual Studio 2019 for Mac version 8.7 Preview 1. To try the Preview version that includes the fix, check for the latest updates on the Preview updater channel. |
Release status update A new Release version of Xamarin.Android has now been published that includes the fix for this issue. Fix included in Xamarin.Android SDK version 11.0.0.3. Fix included on Windows in Visual Studio 2019 version 16.7. To get the new version that includes the fix, check for the latest updates or install the most recent release from https://visualstudio.microsoft.com/downloads/. Fix included on macOS in Visual Studio 2019 for Mac version 8.7. To get the new version that includes the fix, check for the latest updates on the Stable updater channel. |
Hello,
We have a relatively large Xamarin.Android project (it is approx. 2 years old and we have approx. 270 .xml resource files as it can be seen in the attached Diagnostics log).
The issue is that when we update a layout file, 'MSBuild:UpdateGeneratedFiles' takes approximately 40 seconds to run, mainly due to Aapt2Compile task.
Can you please have a look at the build log and investigate if you can make any improvements around this area?
This is my local setup:
P.S. - since the build log contains sensitive information, please use this ticket to download it: https://developercommunity.visualstudio.com/content/problem/896179/android-msbuildupdategeneratedfiles-takes-40-secon.html
If you don't have access to that ticket, please give me an email address that I can use to share the log.
Thanks,
Cosmin
The text was updated successfully, but these errors were encountered: