-
Notifications
You must be signed in to change notification settings - Fork 526
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
Debugger gives up waiting for assemblies to load. #9210
Comments
Eventually, after my walk I've run the app again and again, eventually it just gets far enough to trigger the Android "Wait or Kill" dialog for slow apps. Tapping wait allowed it to run, but this comes up maybe one in 10-15 attempts and you have to catch it quick. I believe at this stage my employer is considering adding MAUI related mental health cover for the developers!! |
@RobTF so is the problem that the app takes a long time to launch? Are you doing work on the main, UI thread? I would consider recording a It could be your code, but it could also be something else like MAUI or the BCL. There are 177 |
@jonathanpeppers they are |
Mono invokes assembly preload hooks in reverse registration order: android/src/native/monodroid/monodroid-glue.cc Lines 683 to 691 in 07cb311
so the "load from override dir" hook should be invoked first, and thus we shouldn't see any of the load failure warnings |
I don't think the messages themselves cause the ANR, though, it must be something else. Either, as @jonathanpeppers suggested, too much work being done on the main thread (and assembly loading itself wouldn't take that much time, unless there's a very, VERY, big image to load and individual assemblies load in well under a millisecond on a midrange device) or there's a deadlock somewhere which causes the connection to time out. |
@RobTF if you don't use Hot Reload, can you try setting the |
Android framework version
net8.0-android
Affected platform version
VS 2022
Description
When launching an app on Android I'm beginning to get this as the app grows;
It takes so long to spin up the app with all the assembly loading stuff the debugger times out.
Apologies in advance for the sarcasm but it's somewhat therapeutic. This sort of thing has plagued the iOS side of things for a while with the watchdog giving up on execution and killing the app before the debugger can latch properly.
Steps to Reproduce
4a. Quietly celebrate as you get one more relatively trouble-free cycle of your > 1 minute long dev loop for some minor code change.
-- or --
4b. Wipe away tears of frustration as useless exception dialog pops up from the depths of the toolchain and yet another mobile development issue raises its head. Try not to look at the clock as it reminds you of the amount of your life you're wasting battling with the tooling.
Did you find any workaround?
Go for a walk and forget about it for half an hour.
Relevant log output
The text was updated successfully, but these errors were encountered: