-
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
Android Release build crashes on device but Debug build runs #19165
Comments
+1 |
Verified this issue with Visual Studio 17.10.0 Preview 3 (8.0.20 & 8.0.0-rc.2.9530). Can repro this issue on Android device (api33). |
I'm checking every release made by this repo since prev year. Not a single handles this. Every time I start my app in Debug it works. Switch to Release and getting crush with exact same error. Even Debug build can't start. Only via Visual Studio Debug through USB |
same issue here, if any info is helping to find a fix or workaround please have a look. Otherwise it can be closed since this is open already. |
I believe the debug log window in VS will show errors with bindings. Let me know if the errors do not show in the debug window. |
I will attempt to retest this issue in the next few days |
The exception info available at app crash in Android device log (when manually launched on device) is now helpful. But see below. The steps to reproduce still have undesired behavior (tested on Samsung device w/Android 13, also OnePlus device w/Android 14).
I suggest this issue remain open until:
`Version 17.13.0 Preview 1.0 After adding a typo/missing style to MainPage.xaml (see step 2 of Steps to Reproduce) No Build errors/warnings about the missing style (e.g. none in Build Output) CASE 1 Debug the app on device from Visual Studio CASE 2 Manually launch the same debug build on the device (Android device log) Time Device Name Type PID Tag Message CASE 3 Manually launch the Release build on the device (Android device log) Time Device Name Type PID Tag Message |
Running the app in debug on Windows, I get an exception at startup:
Not sure why nothing is logged on Android. |
@StephaneDelcroix should missing styles be logged to the console and/or the XAML errors window? |
I had the same issue myself. If you search on the internet, there are quite a lot of complaints about this. Gtidev1 is right. Both the debug and release versions should generate an easy-to-understand exception, even on Android. From my point of view, it's a clear bug if the debug build just ignores unresolvable style names. So I cannot quite understand the decision to remove the "bug" flag. Even if it works on Windows, there is still this bug when working on Android, and the whole reason for MAUI is multi-platform. But please know, I appreciate your work on MAUI. |
Description
Unexpected release build crash on Android device (after the same code works on the device as a debug build)
Steps to Reproduce
<Entry Style="{StaticResource MisssingStyle}" Text="Placeholder" />
Link to public reproduction project repository
No response
Version with bug
8.0.3
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 13
Did you find any workaround?
After working for some time (after a typo) running Debug builds, finding the bug takes too long. The Android logcat info is useless. I did not see any useful warning/error info using the default configuration of the developer environment either.
Requests:
Can the developer environment indicate in the editor window some warning/error for a resource that is a typo / missing
Can the build process indicate in the output some warning/error for a resource that is a typo / missing
Can the behavior (on device) of the Release build and Debug build be made the same for a resource that is a typo / missing (either both builds work or both builds fail)
Possibly related issues:
#15602
#8928
Relevant log output
The text was updated successfully, but these errors were encountered: