.NET 9 Android: Very slow build times #27375
Replies: 9 comments 3 replies
-
For me it is also frequent "Waiting for Debugger to Attach" and freezed VS when breakpoint is hit. ='( |
Beta Was this translation helpful? Give feedback.
-
I am experiencing frequent issues with the Android Emulator while working with .NET MAUI. The emulator often stops working and gets stuck on "Waiting for Debugger to Attach." Even after resetting the emulator and applying the suggested fixes, the issue persists, making development highly frustrating. The time spent troubleshooting emulator problems significantly impacts productivity. I would like to request Microsoft to investigate and provide a more stable solution for the emulator to ensure a smoother development experience. |
Beta Was this translation helpful? Give feedback.
-
Anything we can do here? Working with Android is impossible right now. Build times are like 10 minutes in debug and then the build often won't start on the device. This is huge problem for us. Who can help here? |
Beta Was this translation helpful? Give feedback.
-
@davidortinau I want to bring this to your attention. Is there anything you can provide here on how to solve the long build times? |
Beta Was this translation helpful? Give feedback.
-
Are you building with |
Beta Was this translation helpful? Give feedback.
-
Perhaps @jonathanpeppers would know. |
Beta Was this translation helpful? Give feedback.
-
Well, in Visual studio windows, it is building iOS, Windows, even if you target Android. Which will make things even slower. |
Beta Was this translation helpful? Give feedback.
-
I am realizing an improvement in Net9's start times, both in Windows and Android. In the already open Android emulator, I see the logo after 16 seconds and the start page after 26 seconds when making one change on a C# page. Start with IDE, Hotreload on. When i first tested Net9 in November, i had more than 500 Warnings so i decided to return to Net8. Now, with no Xaml pages left, i decided to switch to Net9 again and it works well. I use MVVM but not the MVVM Toolkit. The release build needs more than 7 minutes. That is indeed too long. One should actually test the release more often because you can't rely on it behaving like the debug version. I do this far too seldom, perhaps once a month. I should do it daily. In the past, when i had slow start times, i found a too old license key for the syncfusion controls. I would check your Nugets for problems. |
Beta Was this translation helpful? Give feedback.
-
Ok, no problem. My understanding was the start time after changing something (F5). I thought this is relevant for working (with debugger). Build with F6 is indeed slower, but this is the same for all platforms because it builds all platforms. My App build time after one change in code (F6): Complete rebuild Solution in debug Complete Build Main App in Release: CPU not very fast, 100% all the time, 32GB Ram |
Beta Was this translation helpful? Give feedback.
-
When upgrading our project from .NET 8 to .NET 9 the build times on local debug massively increased. It's easily 4x-5x slower making working with Android a pain. Also after the long build the app will often not start on the device and I need to start a 10 minutes build again.
Anyone else noticed this? Any ideas how to fix it?
Beta Was this translation helpful? Give feedback.
All reactions