Crashing at startup in Debug, Release is fine

akevanakevan CAMember ✭✭

I'm running Xamarin Studio on OS X Mavericks, building an Android app with latest API version (19?), running it on Galaxy S4. I can run my app on the device in Release just fine. When I try to run in debug mode with some breakpoints, the app just crashes, the ActivityManager kills it after a bunch of failures. I'm new to this stuff so hopefully someone can pick out what my problem might be... here's the logcat

01-10 23:15:21.914: D/dalvikvm(8672): Trying to load lib /data/app-lib/Recon.Recon-1/libmonodroid.so 0x428b7158
01-10 23:15:21.914: D/dalvikvm(8672): Added shared lib /data/app-lib/Recon.Recon-1/libmonodroid.so 0x428b7158
01-10 23:15:21.924: W/libc(8672): WARNING: generic atexit() called from legacy shared library
01-10 23:15:21.924: D/Mono(8672): Image addref mscorlib[0x6ffe3d38] -> mscorlib.dll[0x6ffaf258]: 1
01-10 23:15:21.924: D/Mono(8672): AOT failed to load AOT module mscorlib.dll.so: Cannot load library: load_library(linker.cpp:746): library "/data/data/Recon.Recon/lib/mscorlib.dll.so" not found
01-10 23:15:21.934: D/AndroidRuntime(8675): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
01-10 23:15:21.934: D/AndroidRuntime(8675): CheckJNI is OFF
01-10 23:15:21.934: D/AndroidRuntime(8675): setted country_code = Canada
01-10 23:15:21.934: D/AndroidRuntime(8675): setted countryiso_code = CA
01-10 23:15:21.934: D/AndroidRuntime(8675): setted sales_code = RWC
01-10 23:15:21.934: D/AndroidRuntime(8675): readGMSProperty: start
01-10 23:15:21.934: D/AndroidRuntime(8675): readGMSProperty: already setted!!
01-10 23:15:21.934: D/AndroidRuntime(8675): readGMSProperty: end
01-10 23:15:21.934: D/AndroidRuntime(8675): addProductProperty: start
01-10 23:15:21.944: D/dalvikvm(8675): Trying to load lib libjavacore.so 0x0
01-10 23:15:21.944: D/Mono(8672): GC_MAJOR: (mature allocation failure) pause 0.67ms, total 0.64ms, bridge 0.00ms major 112K/32K los 0K/0K
01-10 23:15:21.944: D/Mono(8672): Assembly mscorlib[0x6ffe3d38] added to domain RootDomain, ref_count=1
01-10 23:15:21.954: D/dalvikvm(8675): Added shared lib libjavacore.so 0x0
01-10 23:15:21.954: D/Mono(8672): Image addref Recon[0x40053af8] -> Recon.dll[0x6ffbb2d0]: 1
01-10 23:15:21.954: D/Mono(8672): Assembly Recon[0x40053af8] added to domain RootDomain, ref_count=1
01-10 23:15:21.954: D/Mono(8672): AOT failed to load AOT module Recon.dll.so: Cannot load library: load_library(linker.cpp:746): library "/data/data/Recon.Recon/lib/Recon.dll.so" not found
01-10 23:15:21.954: W/monodroid-gc(8672): GREF GC Threshold: 46800
01-10 23:15:21.954: D/Mono(8672): Image addref Mono.Android[0x7015cbd8] -> Mono.Android.dll[0x40056960]: 1
01-10 23:15:21.954: D/Mono(8672): Assembly Mono.Android[0x7015cbd8] added to domain RootDomain, ref_count=1
01-10 23:15:21.954: D/Mono(8672): AOT failed to load AOT module Mono.Android.dll.so: Cannot load library: load_library(linker.cpp:746): library "/data/data/Recon.Recon/lib/Mono.Android.dll.so" not found
01-10 23:15:21.954: D/dalvikvm(8675): Trying to load lib libnativehelper.so 0x0
01-10 23:15:21.954: D/dalvikvm(8675): Added shared lib libnativehelper.so 0x0
01-10 23:15:21.954: W/Mono(8672): The request to load the assembly mscorlib v2.0.5.0 was remapped to v2.0.0.0
01-10 23:15:21.954: D/Mono(8672): Unloading image mscorlib.dll [0x70186b80].
01-10 23:15:21.954: D/Mono(8672): Assembly Ref addref Mono.Android[0x7015cbd8] -> mscorlib[0x6ffe3d38]: 2
01-10 23:15:21.974: W/MonoDroid(8672): Xamarin/Android Trial Mode Active
01-10 23:15:21.974: D/Mono(8672): DllImport attempting to load: '/system/lib/liblog.so'.
01-10 23:15:21.974: D/Mono(8672): DllImport loaded library '/system/lib/liblog.so'.
01-10 23:15:21.974: D/Mono(8672): DllImport searching in: '/system/lib/liblog.so' ('/system/lib/liblog.so').
01-10 23:15:21.974: D/Mono(8672): Searching for '__android_log_print'.
01-10 23:15:21.974: D/Mono(8672): Probing '__android_log_print'.
01-10 23:15:21.974: D/Mono(8672): Found as '__android_log_print'.
01-10 23:15:21.984: W/Mono(8672): The request to load the assembly System.Core v2.0.5.0 was remapped to v3.5.0.0
01-10 23:15:21.984: D/Mono(8672): Image addref System.Core[0x70437db8] -> System.Core.dll[0x4017d820]: 1
01-10 23:15:21.984: D/Mono(8672): Assembly System.Core[0x70437db8] added to domain RootDomain, ref_count=1
01-10 23:15:21.984: D/Mono(8672): AOT failed to load AOT module System.Core.dll.so: Cannot load library: load_library(linker.cpp:746): library "/data/data/Recon.Recon/lib/System.Core.dll.so" not found
01-10 23:15:21.984: D/Mono(8672): Assembly Ref addref Mono.Android[0x7015cbd8] -> System.Core[0x70437db8]: 2
01-10 23:15:21.984: W/Mono(8672): The request to load the assembly mscorlib v2.0.5.0 was remapped to v2.0.0.0
01-10 23:15:21.984: D/Mono(8672): Unloading image mscorlib.dll [0x408580d8].
01-10 23:15:21.984: D/Mono(8672): Assembly Ref addref System.Core[0x70437db8] -> mscorlib[0x6ffe3d38]: 3
01-10 23:15:21.994: D/Mono(8672): Assembly Ref addref Recon[0x40053af8] -> Mono.Android[0x7015cbd8]: 2
01-10 23:15:22.144: D/dalvikvm(8675): Note: class Landroid/app/ActivityManagerNative; has 169 unimplemented (abstract) methods
01-10 23:15:22.194: D/AndroidRuntime(8675): Calling main entry com.android.commands.am.Am
<b>**01-10 23:15:22.234: I/ActivityManager(700): Killing proc 8672:Recon.Recon/u0a10208: force stop Recon.Recon**</b>
01-10 23:15:22.234: W/ContextImpl(700): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1323 com.android.server.am.ActivityManagerService.cleanUpApplicationRecordLocked:12306 com.android.server.am.ActivityManagerService.handleAppDiedLocked:3528 com.android.server.am.ActivityManagerService.removeProcessLocked:4733 com.android.server.am.ActivityManagerService.killPackageProcessesLocked:4511 
01-10 23:15:22.244: W/ContextImpl(700): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1323 com.android.server.am.ActivityManagerService.computeOomAdjLocked:14816 com.android.server.am.ActivityManagerService.computeOomAdjLocked:14476 com.android.server.am.ActivityManagerService.updateOomAdjLocked:15107 com.android.server.am.ActivityManagerService.updateOomAdjLocked:15299 
01-10 23:15:22.244: W/ContextImpl(700): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1323 com.android.server.am.ActivityManagerService.computeOomAdjLocked:14822 com.android.server.am.ActivityManagerService.computeOomAdjLocked:14476 com.android.server.am.ActivityManagerService.updateOomAdjLocked:15107 com.android.server.am.ActivityManagerService.updateOomAdjLocked:15299 

Many thanks...

«1

Posts

  • akevanakevan CAMember ✭✭
    edited January 2014

    Ok I started clean with a new "Android Application" solution. The one with the "click me" button.

    I could not set a breakpoint and debug this either, still crashed at startup, with my project set to target framework 4.2 (the "latest installed" API). My device is Android 4.2.2, I've confirmed from the "About Device" section of my Samsung Galaxy S4.

    I checked some sample apps from Xamarin, they worked fine. But they were set to an older version, Froyo 2.2.

    If I reduce my apps target framework the debugging works, but I have to drop it down to Honeycomb 3.1 before I can debug with breakpoints and not crash at startup.

    Shouldn't it work with 4.2??

  • akevanakevan CAMember ✭✭

    For anyone else who stumbles on this... turned out to be a problem with the S4 I was using. I have no idea what it was, but I switched to a different phone (a Nexus 5, same Android version) and everything works fine.

  • NaboNabo SEMember ✭✭

    Hi! I have the same problem (HTC One X, Android version 4.2.2). Debugging from the XStudio (4.2.3) with Android (4.12.1) on a Mac. Don't have another phone to switch to so I'd really like this to work.

    Forwarding debugger port 8935 Forwarding console port 8936 Detecting existing process [libc] WARNING: generic atexit() called from legacy shared library [Mono] Image addref mscorlib[0x5b96dc50] -> mscorlib.dll[0x5b965e20]: 1 [Mono] AOT module 'mscorlib.dll.so' not found: Cannot load library: load_library(linker.cpp:745): library "/data/data/TestApp.TestApp/lib/mscorlib.dll.so" not found [Mono] GC_MAJOR: (mature allocation failure) pause 0.68ms, total 0.66ms, bridge 0.01ms major 96K/32K los 0K/0K [Mono] Assembly mscorlib[0x5b96dc50] added to domain RootDomain, ref_count=1 [Mono] Image addref TestApp[0x5b59c010] -> TestApp.dll[0x5b6858b0]: 1 [Mono] Assembly TestApp[0x5b59c010] added to domain RootDomain, ref_count=1 [Mono] AOT module 'TestApp.dll.so' not found: Cannot load library: load_library(linker.cpp:745): library "/data/data/TestApp.TestApp/lib/TestApp.dll.so" not found [monodroid-gc] GREF GC Threshold: 46800 [Mono] Image addref Mono.Android[0x5b9422e8] -> Mono.Android.dll[0x5b59c808]: 1 [Mono] Assembly Mono.Android[0x5b9422e8] added to domain RootDomain, ref_count=1 [Mono] AOT module 'Mono.Android.dll.so' not found: Cannot load library: load_library(linker.cpp:745): library "/data/data/TestApp.TestApp/lib/Mono.Android.dll.so" not found [Mono] The request to load the assembly mscorlib v2.0.5.0 was remapped to v2.0.0.0 [Mono] Unloading image mscorlib.dll [0x5b59d470]. [Mono] Assembly Ref addref Mono.Android[0x5b9422e8] -> mscorlib[0x5b96dc50]: 2 Loaded assembly: TestApp.dll Loaded assembly: Mono.Android.dll [External] [Mono] The request to load the assembly System.Core v2.0.5.0 was remapped to v3.5.0.0 [Mono] Image addref System.Core[0x5b8faea8] -> System.Core.dll[0x5b8fa610]: 1 [Mono] Assembly System.Core[0x5b8faea8] added to domain RootDomain, ref_count=1 [Mono] AOT module 'System.Core.dll.so' not found: Cannot load library: load_library(linker.cpp:745): library "/data/data/TestApp.TestApp/lib/System.Core.dll.so" not found [Mono] Assembly Ref addref Mono.Android[0x5b9422e8] -> System.Core[0x5b8faea8]: 2 [Mono] The request to load the assembly mscorlib v2.0.5.0 was remapped to v2.0.0.0 [Mono] Unloading image mscorlib.dll [0x5d77ad70]. [Mono] Assembly Ref addref System.Core[0x5b8faea8] -> mscorlib[0x5b96dc50]: 3 Loaded assembly: System.Core.dll [External] [Mono] Assembly Ref addref TestApp[0x5b59c010] -> Mono.Android[0x5b9422e8]: 2 [Mono] DllImport attempting to load: '__Internal'. [Mono] DllImport loaded library '(null)'. [Mono] DllImport searching in: '__Internal' ('(null)'). [Mono] Searching for '_monodroid_gc_wait_for_bridge_processing'. [Mono] Probing '_monodroid_gc_wait_for_bridge_processing'. [Mono] Found as '_monodroid_gc_wait_for_bridge_processing'. [Mono] DllImport searching in: '__Internal' ('(null)'). [Mono] Searching for '_monodroid_get_identity_hash_code'. [Mono] Probing '_monodroid_get_identity_hash_code'. [Mono] Found as '_monodroid_get_identity_hash_code'. Loaded assembly: MonoDroidConstructors [External] [Mono] The request to load the assembly mscorlib v2.0.5.0 was remapped to v2.0.0.0 [Mono] Unloading image mscorlib.dll [0x5d7e0008]. [Mono] Assembly Ref addref TestApp[0x5b59c010] -> mscorlib[0x5b96dc50]: 4 Resolved pending breakpoint at '/Users/mats/Projects/Xamarin/DogTracks/TestApp/MainActivity.cs:25,1' to void TestApp.MainActivity.OnCreate (Android.OS.Bundle bundle) [0x00020]. [Mono] DllImport searching in: '__Internal' ('(null)'). [Mono] Searching for '_monodroid_gref_inc'. [Mono] Probing '_monodroid_gref_inc'. [Mono] Found as '_monodroid_gref_inc'. [Mono] DllImport searching in: '__Internal' ('(null)'). [Mono] Searching for '_monodroid_gref_log_new'. [Mono] Probing '_monodroid_gref_log_new'. [Mono] Found as '_monodroid_gref_log_new'.

  • NaboNabo SEMember ✭✭

    Same problem from Xamarin Studio on a PC. Anybody...?

  • LarryMasonLarryMason USMember

    Got this error message after installing latest Xamarin Studio release 4.2.3 (build 60) today. Running app on a Lenovo with Android 4.1.2. Do not have another phone to try it on. Anybody know what's up?

  • LarryMasonLarryMason USMember

    Solution is to quit Xamarin Studio and restart it.

  • NaboNabo SEMember ✭✭

    Nope, restarting the Xamarin Studio isn't the solution for me. I also now have verified that debugging an android java project from eclipse works fine on the HTC One X. On the same machine with the same phone won't let me debug from the Xamarin Studio. I thought that it might be a phone issue but it seems it's now related to the Xamarin software.

  • NaboNabo SEMember ✭✭

    Hm, I'm using a HTC One X? Do you mean that this answer applies to me as well?

  • JonathanPryorJonathanPryor USXamarin Team Xamurai

    Hm, I'm using a HTC One X? Do you mean that this answer applies to me as well?

    It shouldn't; the HTC One X doesn't have Samsung KNOX (afaik), so i don't know why the /data/data/@[email protected]/files/.__override__ directory would not be created.

    Diagnostic build output would be appreciated for the install, e.g. via:

    msbuild /t:Install /v:diag ProjectName.csproj > b.txt
    
  • NaboNabo SEMember ✭✭
    edited April 2014

    Thanks for getting back. I'll update the log setting and post the output here.

  • NaboNabo SEMember ✭✭
    edited April 2014

    See the attached file for log output...

  • JonathanPryorJonathanPryor USXamarin Team Xamurai

    @MatsNs‌: Thank you for the build log output. Unfortunately, it's just the build log, not the Install log; it's executing the SignAndroidPackage target:

    Project "/Users/mats/Projects/Xamarin/MyGpsApp/MyGpsApp.Droid/MyGpsApp.Droid.csproj" (SignAndroidPackage target(s)):
    

    It's also not producing any errors:

             0 Error(s)
    

    As such, it doesn't help in diagnosing your install issues. :-(

  • NaboNabo SEMember ✭✭

    I'n on a mac with Xamarin studio. Can I use adb or Xamarin to get the install log?

  • NaboNabo SEMember ✭✭

    @JonathanPryor‌ Sorry about the duplicate post but saw that I missed to adress you and I'm not sure if you would get the reply otherwise.

    I'm on a mac with Xamarin studio. Can I use adb or Xamarin to get the install log?

  • JonathanPryorJonathanPryor USXamarin Team Xamurai

    @MatsNs‌: The Device Deployment Logs may provide sufficient information.

  • NaboNabo SEMember ✭✭

    @JonathanPryor‌ Attached is the Device Deployment log

  • JonathanPryorJonathanPryor USXamarin Team Xamurai

    @MatsNs‌: It certainly looks like it should be working:

    This means that adb is being launched:

    [2014-04-24 21:20:43.6] INFO: Starting Android device monitor
    

    Installation of the shared runtime:

    [2014-04-24 21:20:55.0] DEBUG: RunShellCommand: HT245W114864 am broadcast -a mono.android.intent.action.PACKAGE_VERSIONS -e "packages" "Mono.Android.DebugRuntime,Mono.Android.Platform.ApiLevel_10,MyGpsApp.Droid" Mono.Android.DebugRuntime/com.xamarin.mono.android.PackageVersions
    [2014-04-24 21:20:55.8] DEBUG: RunShellCommand: HT245W114864 pm uninstall "Mono.Android.DebugRuntime"
    [2014-04-24 21:21:09.5] DEBUG: RunShellCommand: HT245W114864 pm install "/data/local/tmp/Mono.Android.DebugRuntime-armeabi-v7a.apk"
    [2014-04-24 21:21:12.8] DEBUG: RunShellCommand: HT245W114864 rm "/data/local/tmp/Mono.Android.DebugRuntime-armeabi-v7a.apk"
    

    Oddly Mono.Android.Platform.ApiLevel_10 isn't installed; I guess the version numbers matched and it was already present. (This can be verified with adb shell pm list packages | grep Mono.Android.Platform.ApiLevel_10).

    Find the path of your MyGpsApp.Droid directory and the .__override__ directory:

    [2014-04-24 21:21:13.0] DEBUG: RunShellCommand: HT245W114864 "pm" "path" "MyGpsApp.Droid"
    [2014-04-24 21:21:14.2] DEBUG: Stat: FileInfo for /data/data/MyGpsApp.Droid/files/.__override__: drwxrwxrwx
    

    The Stat: line means that it exists, so copy the assemblies:

    [2014-04-24 21:21:14.2] DEBUG: NotifyPhase: Uploading files
    [2014-04-24 21:21:14.2] DEBUG: NotifySync: SkipCopyFile /Users/mats/Projects/Xamarin/MyGpsApp/MyGpsApp.Droid/bin/Debug/MyGpsApp.Droid.dll /data/data/MyGpsApp.Droid/files/.__override__/MyGpsApp.Droid.dll 67584
    ...
    [2014-04-24 21:21:14.2] DEBUG: NotifyPhase: Upload completed
    

    Then the app is launched:

    [2014-04-24 21:21:14.6] DEBUG: RunShellCommand: HT245W114864 am start -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -n MyGpsApp.Droid/MyGpsApp.droid.MainActivity
    

    ...but the app never launches (ps never finds a matching process), which means deployment was successful...but the app failed to launch for reasons not evident in that log.

    Can you please provide the adb logcat output generated when attempting to run the app?

  • NaboNabo SEMember ✭✭

    @JonathanPryor‌ Thanks for taking your time with this!

    "adb shell pm list packages | grep Mono.Android.Platform.ApiLevel_" returns the following packages:
    package:Mono.Android.Platform.ApiLevel_10
    package:Mono.Android.Platform.ApiLevel_17
    package:Mono.Android.Platform.ApiLevel_19
    package:Mono.Android.Platform.ApiLevel_8

    Just to make sure that I have explained my problem correctly. The app deploys to the device (HTC One X) fine and starts the app. Using the app also works fine until the code hits a breakpoint when the session stops (hitting the breakpoint works fine in the emulator). I can barely just see that the "yellow cursor debugger bar" in Xamarin Studio touched the breakpoint and some kind of error was displayed in the info bubble but it just flashes then it's gone and the app is killed.

    The adb logcat output is attached. Wasn't sure what you meant by "with attempting to run the app" but it's filtered to the app's PID. Did you also want for Mono?

  • JonathanPryorJonathanPryor USXamarin Team Xamurai

    The app deploys to the device (HTC One X) fine and starts the app. Using the app also works fine

    We were on different pages. :-)

    On the Samsung Galaxy S4 and KNOX devices, fast deployment doesn't work at all. The app can't be properly installed, and it errors when starting.

    In your case, the app is installing properly, and does run, so this is nothing like KNOX devices.

    Your problem sounds like a debugger problem. I unfortunately don't have any ideas there.

    Thoughts, @jstedfast?

  • NaboNabo SEMember ✭✭

    @jstedfast‌ Do you have any idéas on what I can try to solve the problem or get more info? As it stands I have an indie lic but can't develop on my phone...

    Ps. Same problem at this thread: http://forums.xamarin.com/discussion/comment/50251

  • JeffreyStedfastJeffreyStedfast USXamarin Team Xamurai

    I have no clue. I suspect this more likely to be a runtime issue than an IDE-side debugger issue.

  • TimothyParezTimothyParez HKMember
    edited April 2014

    I'm having very similar issues on a Cubieboard which has a firmware without restrictions.

    When I build in "debug" mode, the app will run for a while then mono will simply exit,
    without any indication why.

    When I build in "release" mode the app will start and stop instantly.

    If I then run the app by simply starting it on the device it runs for days without interruption (which is the idea in our case)

    Using the latest versions from the Alpha channels. (Unable to use the stable channel because of other issues) The latest versions which I installed this morning seem to make things even worse... it takes less long for mono to exit.

    And I'm using Visual Studio 2013 on Windows 8.1 (just noticed the OP is using OSX)

  • NaboNabo SEMember ✭✭

    @jstedfast‌ With no disrespect intended, basically I'm left with invest in a new phone?

  • JeffreyStedfastJeffreyStedfast USXamarin Team Xamurai

    I'm just saying I'm the wrong person to ask. I work on the debugger, not the runtime and this bug doesn't even involve the debugger (the app crashes, but the debugger is in the IDE which means that the debugger has nothing to do with it.)

  • NaboNabo SEMember ✭✭

    @jstedfast‌ No, I think you misunderstand. It only crashes when trying to debug/stop at a breakpoint. If I remove the breakpoint then the app works fine. Also it's in any app, from my target app, sample project to even the startup "app" you get then creating a new project from scratch. So my problem is not with an app but that I can't debug, which makes it kinda hard to develop.

  • JeffreyStedfastJeffreyStedfast USXamarin Team Xamurai

    What crashes? The app? or Xamarin Studio?

  • NaboNabo SEMember ✭✭

    @jstedfast Well the app stops and some exception is thrown (unable to see or catch it as the session I closed immediately) but I'd rather say that it's the bug session that crashes. Xamarin Studio does not crash but if I remove the breakpoint the app also works fine.
    And again it doesn't matter which app I try or where the breakpoint is set. As soon as the debugger tries to halt at the breakpoint the debug session is terminated. I'll see if I can make a video of it because I'm not sure that I'm explaining it correctly.
    Is there a way to get more info about what is going on?

  • JeffreyStedfastJeffreyStedfast USXamarin Team Xamurai

    @VargaZoltan‌ is the best person to ask what sort of logging information he needs to figure out the problem.

    I only deal with the IDE-side of things.

  • NaboNabo SEMember ✭✭

    @VargaZoltan‌ Third person to ask is the charm? ;)

  • ZoltanVargaZoltanVarga USXamarin Team Xamurai

    This looks similar to the issue where debugging would crash on some older samsung devices due to a kernel problem, but that was a lot time ago, and shouldn't affect newer devices.

    Unfortunately, adroid doesn't provide very good logging facilities to diagnose app crashes, so its hard to debug these problems if we can't reproduce them.

  • NaboNabo SEMember ✭✭
    edited May 2014

    @VargaZoltan‌ So again, I'm stuck with buy a new phone if I want to debug on the device?

  • akevanakevan CAMember ✭✭
    edited May 2014

    @JonathanPryor Thanks for explaining the real problem, the KNOX / Samsung thing. Is there any way the IDE (@jstedfast) could check the phone type (or try and write to that directory) and tell the user that debugging is not supported on the device? Rather than just not work with no error. Samsungs aren't the rarest of phones out there :) I imagine more people will come across this.

    @MatsNs I hear your frustration. I just hit another mystery crash yesterday that sent me for a loop. I've found quite a few quirks in my 5 months working with Xamarin, but the benefits are largely outweighing the difficulties.

    Maybe you can try some of the following to try and at least get some more info on the problem (sorry I'm sure you've already tried some of these, just going through the list of what I've tried in the past)

    • try targeting a lower SDK version
    • take a look at the log file (Help->Open Log Directory)
    • play around with the debug settings, try different debug options, debugger, etc.
    • try an out-of-the-box Xamarin sample project. Can you set break points there?
    • check your watch variables... I find if I use a complex or certain type (linq) of expression in a watch variable while debugging, my app will just shutdown with no message
    • try another phone (borrow one) just to see if it works ??
  • AlexeyGukezhevAlexeyGukezhev ITMember

    Same problem: on samsung device after updating Xamarin Studio.
    To solve the issue go to optiond and disable fast deploy + enable single deployment package
    cheesss

  • BenPattinsonBenPattinson USMember ✭✭

    Intermittently the same problem here on a Samsung S6 - much of the time it works fine, then it will get into a cycle where it refuses to get past the splash screen of the App 4 or 5 times in a row. Switching apps on the phone seems to help, then it starts working perfectly after a few attempts.
    Very irritating, but it sounds like KNOX should prevent it working at all, so maybe I should be thankful!

    Is this KNOX issue still supposed to be a problem with the S6 and latest Xamarin via visual studio 2013?

  • AlejandroSeguraAlejandroSegura USMember ✭✭

    My Galaxy Edge S6 would suddenly crash immediately on app start after making a minor change. I rebooted my machine which did not help. I rebooted my phone and then things were back to normal. Hope that helps somebody.

  • FernandoEstevesFernandoEsteves USMember

    I had the same problem and found out is how to compile, try to make a apk release form of 3.6mb jumped to 13.4mb with libraries and so worked.

  • stoberovstoberov BGMember

    I had a similar issue - finally fixed it by going to Properties / Android Options / Advanced tab and checking "armeabi", "armeabi-v7a" and "x86" as supported architectures.

  • BoguslawBlonskiBoguslawBlonski PLMember ✭✭✭

    Well it's happening on Android_Accelerated_x86 as well, and it is weird worked fine no changes ware made in that could affect armabi, and it stoped working

  • SnehalJadhav.7507SnehalJadhav.7507 USMember ✭✭

    I'm facing the same problem and i'm new to this stuff. App works fine with release mode. But Crashes on Debug mode.

Sign In or Register to comment.