After getting lot of recommendation from people about using visual studio code. Steps to reproducePrerequisite to run sonar analysis: we need to have Java 8 on mac. But I'll submit it here in Mono first based on a guess that it might be possible to fix the issue by adjusting the debugger in some way. One thought I had based on the involvement of Android.OS.AsyncTask was that it might involve the Java interop layer. I'm not sure yet where the root of this problem is.Attempt to repeat steps 4 and 5 five times.Test case: RepeatedBreakpointAsyncTask.zip(This is just a new template Xamarin.Android app with a minimal example AsyncTask.) Current behaviorOn one of the repetitions of step 6, Visual Studio opens a Break Mode tab that says:The selected debug engine does not support any code executing on the current thread (e.g. After Visual Studio pauses on the breakpoint, run Debug > Continue Tap the envelope icon button in the lower right of the app. Set a breakpoint on the first line of AsyncTask1.RunInBackground() (at MainActivity.cs line 16).
![]() On which platforms did you notice thisVisual Studio 2019 version 16.5 IntPreviewMono Debugging for Visual Studio 16.5.506 (c3636c8)Xamarin 16.5.000.363 SDK 10.2.0.16 (d16-5/48f0fe7), which uses 062f0abI was able to reproduce the same behavior with Visual Studio 2019 version 16.1.6.Mono Debugging for Visual Studio 16.1.1 (2473f22)Xamarin 16.1.0.545 SDK 9.3.0.23 which uses 3a07bd4Likely related reports (oldest to newest):Regression between Visual Studio 2017 version 15.9 and Visual Studio 2019 version 16.1:After seeing these Visual Studio Developer Community reports, I thought it would be interesting to check the behavior of this test case on Visual Studio 2017 too.Indeed, I was not able to reproduce this problem in Visual Studio 2017 version 15.9. For example, Visual Studio highlights the current execution line in the editor, and Debug > Step Over allows stepping to the next line. On the other devices and emulators, I could remove that line and still reproduce the issue.The first time the breakpoint is hit, the debugger behaves as expected. Open dmg file on mac os xAndroid 10 (API level 29) x86_64, Google Play emulator ( system-images android-29 google_apis_playstore x86_64):I will try a few experiments to see if I can narrow down which specific component has changed behavior.$ git diff -shortstat 53a841ff.5b8247e29 files changed, 572 insertions(+), 13 deletions(-)$ git diff -shortstat 1cdb9c20.7c9e215824 files changed, 2393 insertions(+), 396 deletions(-)$ git diff -shortstat a6a7f5c0.8021f3fb16 files changed, 98 insertions(+), 25 deletions(-)$ git diff -shortstat e8d054bf.e1c7a729220 files changed, 9758 insertions(+), 3165 deletions(-)$ git diff -shortstat 2ff89885.d90665a4612 files changed, 20193 insertions(+), 10239 deletions(-)Breakpoints are not working in emulator or when physical device attached. Android 9.0 Pie (API level 28) arm64-v8a, Google Pixel 3 Android 7.1 Nougat (API level 25) x86_64, Google APIs emulator ( system-images android-25 google_apis x86_64) Android 7.1 Nougat (API level 25) x86, Google APIs emulator ( system-images android-25 google_apis x86) Android 7.1 Nougat (API level 25) armeabi-v7a, Motorola Moto E4 ![]()
0 Comments
Leave a Reply. |
AuthorChristopher ArchivesCategories |