Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Crash when debugging Android Fabulous app using Visual Studio 2019
See original GitHub issuedotnet new -i Fabulous.Templatesdotnet new fabulous-app- Open .sln file with Visual Studio 2019
- Select Android project as startup project
- Debug with a physical Android device and wait
- Click Install on device and wait
- Click Install on device and wait
- Click Install on device and wait
- Observe blank screen being popped up
- “<appname>.Android has stopped”
Full Error
=================================================================
Native Crash Reporting
04-07 21:52:08.560 E/mono-rt ( 9704): /proc/self/maps:=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================
=================================================================
Basic Fault Adddress Reporting
=================================================================
Memory around native instruction pointer (0x8ded08b0):
04-07 21:52:08.560 E/mono-rt ( 9704): 12c00000-42c00000 rw-p 00000000 00:05 14939 /dev/ashmem/dalvik-main space (region space) (deleted)0x8ded08a0 50 1d c2 ae 5c 1d c2 ae 68 1d c2 ae 74 1d c2 ae P...\...h...t...
0x8ded08b0 18 94 09 8e 1b 00 00 00 00 eb db a5 b8 0e 10 90 ................
0x8ded08c0 b8 26 45 ae fe 03 00 00 00 01 10 00 00 00 00 00 .&E.............
0x8ded08d0 00 00 00 00 00 10 c2 ae 0c 10 c2 ae 18 10 c2 ae ................
No native Android stacktrace (see debuggerd output).
=================================================================
Managed Stacktrace:
=================================================================
=================================================================
04-07 21:52:08.560 E/mono-rt ( 9704): 7068d000-70900000 rw-p 00000000 fd:02 1528961 /data/dalvik-cache/arm/system@framework@boot.art
04-07 21:52:08.560 E/mono-rt ( 9704): 70900000-70a21000 rw-p 00000000 fd:02 1528962 /data/dalvik-cache/arm/system@framework@boot-core-libart.art
04-07 21:52:08.560 E/mono-rt ( 9704): 70a21000-70a6d000 rw-p 00000000 fd:02 1528963 /data/dalvik-cache/arm/system@framework@boot-conscrypt.art
04-07 21:52:08.560 E/mono-rt ( 9704): 70a6d000-70a9b000 rw-p 00000000 fd:02 1528964 /data/dalvik-cache/arm/system@framework@boot-okhttp.art
04-07 21:52:08.560 E/mono-rt ( 9704): 70a9b000-70aff000 rw-p 00000000 fd:02 1528965 /data/dalvik-cache/arm/system@framework@boot-bouncycastle.art
04-07 21:52:08.560 E/mono-rt ( 9704): 70aff000-70b6b000 rw-p 00000000 fd:02 1528966 /data/dalvik-cache/arm/system@framework@boot-apache-xml.art
04-07 21:52:08.561 E/mono-rt ( 9704): 70b6b000-70b6f000 rw-p 00000000 fd:02 1528967 /data/dalvik-cache/arm/system@framework@boot-legacy-test.art
04-07 21:52:08.561 E/mono-rt ( 9704): 70b6f000-70bcc000 rw-p 00000000 fd:02 1528968 /data/dalvik-cache/arm/system@framework@boot-ext.art
04-07 21:52:08.561 E/mono-rt ( 9704): 70bcc000-714d4000 rw-p 00000000 fd:02 1528969 /data/dalvik-cache/arm/system@framework@boot-framework.art
04-07 21:52:08.561 E/mono-rt ( 9704): 714d4000-7159a000 rw-p 00000000 fd:02 1528970 /data/dalvik-cache/arm/system@framework@boot-telephony-common.art
04-07 21:52:08.561 E/mono-rt ( 9704): 7159a000-715a6000 rw-p 00000000 fd:02 1528971 /data/dalvik-cache/arm/system@framework@boot-voip-common.art
04-07 21:52:08.561 E/mono-rt ( 9704): 715a6000-715b3000 rw-p 00000000 fd:02 1528972 /data/dalvik-cache/arm/system@framework@boot-ims-common.art
04-07 21:52:08.561 E/mono-rt ( 9704): 715b3000-715e4000 rw-p 00000000 fd:02 1528973 /data/dalvik-cache/arm/system@framework@boot-org.apache.http.legacy.boot.art
04-07 21:52:08.561 E/mono-rt ( 9704): 715e4000-715e5000 rw-p 00000000 fd:02 1528974 /data/dalvik-cache/arm/system@framework@boot-android.hidl.base-V1.0-java.art
04-07 21:52:08.561 E/mono-rt ( 9704): 715e5000-715e8000 rw-p 00000000 fd:02 1528975 /data/dalvik-cache/arm/system@framework@boot-android.hidl.manager-V1.0-java.art
04-07 21:52:08.561 E/mono-rt ( 9704): 715e8000-715f0000 rw-p 00000000 fd:02 1528976 /data/dalvik-cache/arm/system@framework@boot-mediatek-common.art
04-07 21:52:08.561 E/mono-rt ( 9704): 715f0000-7160f000 rw-p 00000000 fd:02 1528977 /data/dalvik-cache/arm/system@framework@boot-mediatek-framework.art
04-07 21:52:08.561 E/mono-rt ( 9704): 7160f000-716e4000 rw-p 00000000 fd:02 1528978 /data/dalvik-cache/arm/system@framework@boot-mediatek-telephony-common.art
04-07 21:52:08.562 E/mono-rt ( 9704): 716e4000-71701000 rw-p 00000000 fd:02 1528979 /data/dalvik-cache/arm/system@framework@boot-mediatek-telephony-base.art
04-07 21:52:08.562 E/mono-rt ( 9704): 71701000-71708000 rw-p 00000000 fd:02 1528980 /data/dalvik-cache/arm/system@framework@boot-mediatek-ims-common.art
04-07 21:52:08.562 E/mono-rt ( 9704): 71708000-7170d000 rw-p 00000000 fd:02 1528981 /data/dalvik-cache/arm/system@framework@boot-mediatek-telecom-common.art
04-07 21:52:08.562 E/mono-rt ( 9704): 7170d000-7178a000 rw-p 00000000 fd:02 1528982 /data/dalvik-cache/arm/system@framework@boot-miui.art
04-07 21:52:08.562 E/mono-rt ( 9704): 7178a000-717dc000 rw-p 00000000 fd:02 1528983 /data/dalvik-cache/arm/system@framework@boot-miuisystem.art
04-07 21:52:08.562 E/mono-rt ( 9704): 717dc000-71ab3000 r--p 00000000 fd:01 2039 /system/framework/arm/boot.oat
04-07 21:52:08.564 F/libc ( 9704): Fatal signal 11 (SIGSEGV), code 2, fault addr 0x8ded08b0 in tid 9704 (com.companyname), pid 9704 (com.companyname)
04-07 21:52:08.669 I/libc ( 9704): orig_dumpable: 1
Issue Analytics
- State:
- Created 4 years ago
- Comments:25 (4 by maintainers)
Top Results From Across the Web
Crash when debugging Android Fabulous app using ...
Templates dotnet new fabulous-app Open .sln file with Visual Studio 2019 Select Android project as startup project Debug with a physical ...
Read more >Android app crashes when launched in debug mode
When I run in debug mode the app crashes, but when I just run it normally it works. I think the problem happens...
Read more >Android native crash, Visual Studio 2019 16.1.2
My Android app which compiles and runs fine with Visual Studio 2017 has a native crash when compiled with Visual Studio 2019 (Version...
Read more >Quick Fix: Visual Studio 2019 Debugger Crashing When ...
Make sure the first check box (Debug items in the solution and items in specific packages) is checked. Then move into the Include...
Read more >How To Debug an Android App when it Crashes on ... - YouTube
Android Studio #13: How To Debug an Android App when it Crashes on Debug Mode. 56K views · 7 years ago ...more ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I have had the same exception on startup ( Could not load type of field 'Fabulous.ViewElement… Could not resolve type …'Microsoft.FSharp.Core.FSharpValueOption etc) happen to me a couple of times this week, but on iOS instead. Android has been fine.
In each case I have tracked down the problem to this line in my fsproj:
which needed to be replaced with
@Ryan-Palmer-CIT Could you open another issue, please? I think we need to include your fix in the templates.