You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! I'm a creator of .NET Meteor extension for VSCode. My extension has a Debug in Release feature that allows you to connect the mono debugger for the release apps (with trimming and AOT). It's very useful in some scenarios, when application crushes only in the release mode.
For example:
For iOS and Mac I use the _BundlerDebug=true option. Maybe there is an analog for Android?
Steps to Reproduce
dotnet build -c:Release
adb shell setprop debug.mono.connect port=10000
adb shell am start ...
Trying to connect with Mono.Debugging.Soft.ISoftDebuggerConnectionProvider.BeginConnect
E/adbd : failed to connect to socket 'tcp:10000': Connection refused
Did you find any workaround?
I know that I can use adb logcat, but this way is more convenient for me.
Relevant log output
No response
The text was updated successfully, but these errors were encountered:
JaneySprings
changed the title
A way to connect Mono Debugger for the Release builds
[Question] A way to connect Mono Debugger for the Release builds
May 11, 2024
Android application type
.NET Android (net7.0-android, net8.0-android, etc.)
Affected platform version
.NET 8+
Description
Hi! I'm a creator of .NET Meteor extension for VSCode. My extension has a
Debug in Release
feature that allows you to connect the mono debugger for the release apps (with trimming and AOT). It's very useful in some scenarios, when application crushes only in the release mode.For example:
For iOS and Mac I use the
_BundlerDebug=true
option. Maybe there is an analog for Android?Steps to Reproduce
dotnet build -c:Release
adb shell setprop debug.mono.connect port=10000
adb shell am start ...
Mono.Debugging.Soft.ISoftDebuggerConnectionProvider.BeginConnect
Did you find any workaround?
I know that I can use
adb logcat
, but this way is more convenient for me.Relevant log output
No response
The text was updated successfully, but these errors were encountered: