Forum Xamarin.iOS

Error when launching my App on Iphone 6 9.3.2 and Xamarin 6.0

Hello,

I have got an issue with the last release of xamarin.

I'm running my app on a iphone 6 with IOS 9.3.2, my app won't start on debug mode but start on release mode.
I try with another device (iphone and older Iphone) it's working.

Some details, only ARMV7 and minimum target IOS 9.

Launched application '*****' on '******' with pid 622
dyld: Library not loaded: @executable_path/libxamarin-debug.dylib
Referenced from: /var/containers/Bundle/Application/8F7B416B-116A-4EEB-AFFF-714FF248C44A/*****.app/******
Reason: no suitable image found. Did find:
/var/containers/Bundle/Application/8F7B416B-116A-4EEB-AFFF-714FF248C44A/*******.app/libxamarin-debug.dylib: mmap() error 22 at address=0x006B1000, size=0x00021CD0 segment=__LINKEDIT in Segment::map() mapping /var/containers/Bundle/Application/8F7B416B-116A-4EEB-AFFF-714FF248C44A/*******.app/libxamarin-debug.dylib
/private/var/containers/Bundle/Application/8F7B416B-116A-4EEB-AFFF-714FF248C44A/*******.app/libxamarin-debug.dylib: mmap() error 22 at address=0x00711000, size=0x00021CD0 segment=__LINKEDIT in Segment::map() mapping /private/var/containers/Bundle/Application/8F7B416B-116A-4EEB-AFFF-714FF248C44A/******.app/libxamarin-debug.dylib
Application '********' terminated.

Thanks

Posts

  • FrancoisDabonotFrancoisDabonot USMember ✭✭
    edited June 2016

    I have some informations
    This issue is only when I compiled my app on ARMV7 and not with ARM64 with an iphone 6.

    It can be reproduce with a new project for Xamarin IOS with Supported architectures ARMV7.

  • DaveHuntDaveHunt USMember ✭✭✭✭✭

    Anything you submit to the App store has to have ARM64 enabled anyway. I don't know what it has to do with release vs debug, but you've got to enable it eventually, so you may as well do it now.

  • FrancoisDabonotFrancoisDabonot USMember ✭✭

    Thanks for the reply.

    My apps is not for the store, only inhouse.
    I have some limitation from native library which not supporting arm64.

    So this is clearly an issue from the debug library of Xamarin.

    My apps worked with the previous release not with the current one.

    So, I will rollback my Xamarin version.

    Thanks

  • sarahdsarahd USMember

    I get the same error. The ios app won't run in debug mode on any of my devices.

    Francois - on your other devices, what version of ios are they running? Have you found a fix?

    Xamarin Studio MAC Version 6.0 (build 5174)
    iPhone 6 & iPhone 6 plus - running 9.3.2
    (Xamarin Studio & Packages are all up to date)

    Dyld Error Message:
    Dyld Message: Library not loaded: @executable_path/libxamarin-debug.dylib
    Referenced from: /var/containers/Bundle/Application/F92B2E33-F3AE-4AC5-83E6-7F3649123F3D/MyAppiOS.app/MyAppiOS
    Reason: no suitable image found. Did find:
    /var/containers/Bundle/Application/F92B2E33-F3AE-4AC5-83E6-7F3649123F3D/MyAppiOS.app/libxamarin-debug.dylib: mmap() error 22 at address=0x00A59000, size=0x00021CD0 segment=__LINKEDIT in Segment::map() mapping /var/containers/Bundle/Application/F92B2E33-F3AE-4AC5-83E6-7F3649123F3D/MyAppiOS.app/libxamarin-debug.dylib
    /private/var/containers/Bundle/Application/F92B2E33-F3AE-4AC5-83E6-7F3649123F3D/MyAppiOS.app/libxamarin-debug.dylib: mmap() error 22 at address=0x00AB9000, size=0x00021CD0 segment=__LINKEDIT in Segment::map() mapping /private/var/containers/Bundle/Application/F92B2E33-F3AE-4AC5-83E6-7F3649123F3D/MyAppiOS.app/libxamarin-debug.dylib
    Dyld Version: 390.7

    Binary Images:
    0xac000 - 0x39ffff MyAppiOS armv7 <72affff9f392384fafae4bbccc335c36> /var/containers/Bundle/Application/F92B2E33-F3AE-4AC5-83E6-7F3649123F3D/MyAppiOS.app/MyAppiOS
    0x79c000 - 0x923fff libmonosgen-2.0.dylib armv7s <86b4c11485533926a35f07a704eedf20> /var/containers/Bundle/Application/F92B2E33-F3AE-4AC5-83E6-7F3649123F3D/MyAppiOS.app/libmonosgen-2.0.dylib
    0x1fe00000 - 0x1fe27fff dyld armv7s /usr/lib/dyld

  • sarahdsarahd USMember

    I get the same error. The ios app won't run in debug mode on any of my devices.

    Francois - on your other devices, what version of ios are they running? Have you found a fix?

    Xamarin Studio MAC Version 6.0 (build 5174)
    iPhone 6 & iPhone 6 plus - running 9.3.2
    (Xamarin Studio & Packages are all up to date)

    Dyld Error Message:
    Dyld Message: Library not loaded: @executable_path/libxamarin-debug.dylib
    Referenced from: /var/containers/Bundle/Application/F92B2E33-F3AE-4AC5-83E6-7F3649123F3D/MyAppiOS.app/MyAppiOS
    Reason: no suitable image found. Did find:
    /var/containers/Bundle/Application/F92B2E33-F3AE-4AC5-83E6-7F3649123F3D/MyAppiOS.app/libxamarin-debug.dylib: mmap() error 22 at address=0x00A59000, size=0x00021CD0 segment=__LINKEDIT in Segment::map() mapping /var/containers/Bundle/Application/F92B2E33-F3AE-4AC5-83E6-7F3649123F3D/MyAppiOS.app/libxamarin-debug.dylib
    /private/var/containers/Bundle/Application/F92B2E33-F3AE-4AC5-83E6-7F3649123F3D/MyAppiOS.app/libxamarin-debug.dylib: mmap() error 22 at address=0x00AB9000, size=0x00021CD0 segment=__LINKEDIT in Segment::map() mapping /private/var/containers/Bundle/Application/F92B2E33-F3AE-4AC5-83E6-7F3649123F3D/MyAppiOS.app/libxamarin-debug.dylib
    Dyld Version: 390.7

    Binary Images:
    0xac000 - 0x39ffff MyAppiOS armv7 <72affff9f392384fafae4bbccc335c36> /var/containers/Bundle/Application/F92B2E33-F3AE-4AC5-83E6-7F3649123F3D/MyAppiOS.app/MyAppiOS
    0x79c000 - 0x923fff libmonosgen-2.0.dylib armv7s <86b4c11485533926a35f07a704eedf20> /var/containers/Bundle/Application/F92B2E33-F3AE-4AC5-83E6-7F3649123F3D/MyAppiOS.app/libmonosgen-2.0.dylib
    0x1fe00000 - 0x1fe27fff dyld armv7s /usr/lib/dyld

  • MnetKrishnaMnetKrishna USMember

    Hey Guys,

    I'm getting the same result, Visual Studio and Mac both updated to latest versions of Xamarin - app starts, displays splash screen, then boom.

    Any work arounds?

    I just came across this scenario, thought I'd put some feelers out before I spend hours trying to track it down.

  • FrancoisDabonotFrancoisDabonot USMember ✭✭

    I also try with an Iphone SE, same libxamarin-debug.dylib error. But with older device (iphone 4G/5G and iphone 4S) it's working.

    I seems the issue happens on ios device which support ARM64 (Iphone 5s/6Plus/6sPlus/Iphone SE).

    The problem can be easily reproduce with a new projet which support only armv7 and launch on a iphone 6 or SE.

    But for now, I'm back to the previous release...

  • MnetKrishnaMnetKrishna USMember

    Interesting... I've reverted to the previous version of Xamarin. Did you need to downgrade the nuget packages also?

  • FrancoisDabonotFrancoisDabonot USMember ✭✭
    edited June 2016

    I got some trouble when I rollback, Some updated references wasn't compatible with the previous version of xamarin (Mono Version, I guess). I just rollback my workspace with my svn repository and fix my problem of references.

  • sarahdsarahd USMember

    Changing the build settings to ARMv7 + ARM64 worked for me.

  • Nickrogers.3615Nickrogers.3615 USMember

    This was fixed for me by unchecking "Enable Device Specific Builds" for debugging on iOS 7Plus physical device

    The AdHoc build would run fine, but the Debug builds would crash at the loading screen until I unchecked this in Build options. Now it takes a much longer time to build. Productivity is dropping...

  • Felix.xFelix.x USMember ✭✭

    uncheck the incremental build will also help.

  • IsaackIsaack USMember ✭✭

    For me a Rebuild All did it, I didn't need to change any other settings.

  • IsaackIsaack USMember ✭✭

    For me a Rebuild All did it, I didn't need to change any other settings.

  • WindyhenWindyhen USMember ✭✭

    @Felix.x said:
    uncheck the incremental build will also help.

    tis work for me Xamarin 3.0.0.561731. Thanks

  • nimbusternimbuster Member

    Did anyone figure out why unchecking 'Enable incremental builds' resolves this? Happening to me in Xamarin 5.0.0.2012.

    Long story short, I've tried everything -- creating new certificates, deleting caches, reinstalling Visual Studio and Xcode, etc. -- but only this works. However, forcing me to wait 15 minutes per build is not a solution.

Sign In or Register to comment.