-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
A sample app stops working after the 1st run #23374
Comments
Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! Open similar issues:
Closed similar issues:
|
Thanks for adding the log! Just to be clear, from which run is this log? I would be very curious about some logcat from when you try to restart the app and it crashes and see what is in there. Is that this log? If not, could you get that and add it please? I have never seen this happening myself. @jonathanpeppers ? |
@jfversluis yes, this is the log from step 6: hit F5 to run the app again - the app crashes |
You can enable more logging with: # clear the log
adb logcat -c
# enable extra logging
adb shell setprop debug.mono.log default,debugger,assembly,mono_log_level=debug,mono_log_mask=all
# cause the crash
# save the log & share the file here:
adb logcat -d > log.txt Then the app should print out more info? Usually, it should print out some message that says why it exited. |
I see this in the logs:
|
That sounds like Is the device close to disk space full? Can you factory reset it? If it's an emulator, try deleting and recreating it. |
This is a physical device, not an emulator - see the bug description. The device has around 100GB of free storage. Native Android apps run from Android Studio work without problems. The same goes for Flutter apps. Attached is the log with mono debugging enabled. |
@lszl84 it sounds more like "something went wrong installing this one app" Unrelated to what app framework you were using, did you already try manually uninstalling the app? |
Yes, I manuall uninstalled the app before re-running it from VSCode and capturing the logs. |
So, let's try one more thing, and save a binary build log: https://aka.ms/binlog
Thanks. |
Interestingly, everything seems to work well when running the app with the command you provided. Can it be a VSCode/MAUI extension issue? |
It looks like there isn't a way to save a log like this inside VS Code yet: |
This issue has been verified using Visual Studio Code(1.90.2). Can be reproduced on Android(11) device platform. |
Can you confirm is this is still an issue for you with more recent versions? Did you uncover more information? |
Hi @lszl84. We have added the "s/needs-info" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time. |
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate. |
Description
Running a sample MAUI app on a physical Android 9 device works only the 1st time. Subsequent runs crash the app (when run from vscode) or hang the app (when run manually from home screen). Reinstalling does not help. Only cleaning with
dotnet clean
andrm -rf bin obj
.Steps to Reproduce
dotnet new maui
code .
When trying to run the app manually by touching the icon on the home screen, the app opens up but is stuck on the splash screen.
You can see the problem in this video: https://www.dropbox.com/scl/fi/75fkq7js992vulneyyic5/IMG_0235.MOV?rlkey=lcccgyyuvzsf6szzoi7eour0w&st=4vryubyv&dl=0
Device details:
HUAWEI M5 SHT-W09
EMUI version 9.1.0
Android version 9
Link to public reproduction project repository
No response
Version with bug
8.0.40 SR5
Is this a regression from previous behavior?
Not sure, did not test other versions
Last version that worked well
Unknown/Other
Affected platforms
Android
Affected platform versions
Android 9
Did you find any workaround?
No
Relevant log output
The text was updated successfully, but these errors were encountered: