xcode 7 beta 2 unable to launch iOS 9 simulators

It happens both in beta 1 and beta 2.

After installing xcode 7 beta, I see no simulators at all.


When navigation to Xcode -> open developer tool -> Simluator

I get the following error "Simulator cannot be opened because of a problem.":


(reinstalling xcode beta didn't work. xcode 6.4 works fine)


Process:               Simulator [1541]
Path:                  /Applications/Xcode-beta.app/Contents/Developer/Applications/Simulator.app/Contents/MacOS/Simulator
Identifier:            com.apple.iphonesimulator
Version:               ???
Build Info:            Indigo-605000000000000~23
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           Simulator [1541]
User ID:               502


Date/Time:             2015-07-01 12:16:11.842 +0300
OS Version:            Mac OS X 10.10.4 (14E46)
Report Version:        11
Anonymous UUID:        F963D212-569A-07E6-358A-853EBB0129B1




Time Awake Since Boot: 3400 seconds


Crashed Thread:        0


Exception Type:        EXC_BREAKPOINT (SIGTRAP)
Exception Codes:       0x0000000000000002, 0x0000000000000000


Application Specific Information:
dyld: launch, loading dependent libraries


Dyld Error Message:
  Library not loaded: /usr/lib/libwep
  Referenced from: /Applications/Xcode-beta.app/Contents/Developer/Applications/Simulator.app/Contents/MacOS/Simulator
  Reason: no suitable image found.  Did find:
  /usr/lib/libwep: mmap() error 1 at address=0x1061E7000, size=0x00003000 segment=__TEXT in Segment::map() mapping /usr/lib/libwep
  /usr/lib/libwep: mmap() error 1 at address=0x1061EE000, size=0x00003000 segment=__TEXT in Segment::map() mapping /usr/lib/libwep


Binary Images:
    0x7fff64cda000 -     0x7fff64d10837  dyld (353.2.1) <72A99D0F-0B56-3938-ABC5-67A0F33757C4> /usr/lib/dyld
    0x7fff81ccc000 -     0x7fff81f8dffb  com.apple.WebKit (10600 - 10600.7.12) <A6515140-ADED-30E6-B010-E5C3EEC51732> /System/Library/Frameworks/WebKit.framework/Versions/A/WebKit
    0x7fff83c40000 -     0x7fff83c43fff  com.apple.xpc.ServiceManagement (1.0 - 1) <D94F7F86-4015-3453-92FD-ADC04F215C04> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement
    0x7fff8600c000 -     0x7fff8602cff7  com.apple.MultitouchSupport.framework (264.6 - 264.6) <B4BDB2C0-5D4E-30F4-8EB0-CC16C91DF418> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport
    0x7fff885fc000 -     0x7fff88994ff7  com.apple.CoreFoundation (6.9 - 1153.18) <5C0892B8-9691-341F-9279-CA3A74D59AA0> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x7fff88c4f000 -     0x7fff88cc1fff  com.apple.framework.IOKit (2.0.2 - 1050.20.2) <09C0518C-90DF-3FC3-96D6-34D35F72C8EF> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
    0x7fff898bf000 -     0x7fff898bffff  com.apple.Carbon (154 - 157) <9BF51672-1684-3FDE-A561-FC59A2864EF8> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
    0x7fff8ae73000 -     0x7fff8ae74ff3  libSystem.B.dylib (1213) <AD223AEB-237D-35A3-825E-EECF95916838> /usr/lib/libSystem.B.dylib
    0x7fff8af1c000 -     0x7fff8b758fef  com.apple.CoreGraphics (1.600.0 - 788.2) <31A7F05E-9C68-3642-A8F0-3863777955AE> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
    0x7fff8bf66000 -     0x7fff8c116ff3  com.apple.QuartzCore (1.10 - 361.19) <F815B60E-75E3-3263-BE93-27A49882CF58> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
    0x7fff8d075000 -     0x7fff8dbf6ff7  com.apple.AppKit (6.9 - 1348.17) <E485D56D-3E72-34B7-99BB-BFDEE2D07BF5> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
    0x7fff8dbf7000 -     0x7fff8df28fff  com.apple.Foundation (6.9 - 1153.20) <F0FF3A5D-C5B7-34A1-9319-DE1EF928E58E> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
    0x7fff8f40d000 -     0x7fff8f60746f  libobjc.A.dylib (647) <759E155D-BC42-3D4E-869B-6F57D477177C> /usr/lib/libobjc.A.dylib
    0x7fff8f7b4000 -     0x7fff8f7c2ff7  com.apple.opengl (11.1.2 - 11.1.2) <5F355713-4637-33CD-9CBA-4B4CA43FB0FE> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL


Model: Macmini7,1, BootROM MM71.0220.B03, 2 processors, Intel Core i5, 2.6 GHz, 16 GB, SMC 2.24f32
Graphics: Intel Iris, Intel Iris, Built-In
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x02FE, 0x4544464232333241314D412D47442D460000
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x02FE, 0x4544464232333241314D412D47442D460000
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x13B), Broadcom BCM43xx 1.0 (7.15.166.24.3)
Bluetooth: Version 4.3.5f8 15969, 3 services, 27 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Serial ATA Device: APPLE HDD HTS541010A9E662, 1 TB
USB Device: iPhone
USB Device: IR Receiver
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: Plantronics C310-M
USB Device: Keyboard Hub
USB Device: Apple Keyboard
Thunderbolt Bus: Mac mini, Apple Inc., 26.1
Up vote post of staselVaronis Down vote post of staselVaronis
5.1k views
Posted by
staselVaronis
Reply
Add a Comment

Replies

What is /usr/lib/libwep?

In Xcode 7, we enabled library validation for CoreSimulatorService. If the system detects foreign code being injected into the process, the process will be killed. In this case, "something" is causing /usr/lib/libwep to be injected into the process, and the system is terminating it.

Posted by
jeremyhu
Up vote reply of jeremyhu Down vote reply of jeremyhu
Add a Comment

Jeremy,

libwep is used by Websense - an application in use in numerous corporate organisations world wide.


I have tried to get Xcode 7 to work for over a day in a corporate environment and cannot. I have websense installed.


Enabling this feature is likely to prevent a large number of developers from being able to work - unless there is a planned work around which doesn't require uninstalling websense...


Your thoughts please.

Posted by
adpward
Up vote reply of adpward Down vote reply of adpward
Add a Comment

Jeremy,


As adpward said, /usr/lib/libwep is a file managed by WebSense endpoint which is part of our organization policy. This prevents us from using the new simulators. We are currenly in contact with WenSense support about this issue. But uninstalling WebSense is currently not an option.


Is there a workaround you can offer until the issue is being resolved on either sides?


Thanks

Posted by
staselVaronis
Up vote reply of staselVaronis Down vote reply of staselVaronis
Add a Comment

Unfortunately, there's no workaround that I can provide to you. I don't have access to WebSense in order to inspect what it's doing to the system to inject its code. If you could provide more information about how WebSense operates, I could possibly help figure out a workaround for you.


Other software uses DYLD_INSERT_LIBRARIES in order to inject 3rd party code which interposes system libraries. In cases like that, you could work around it by unsetting DYLD_INSERT_LIBRARIES for certain processes. However, the crash log indicates that this isn't the method that WebSense is using to inject its code. The log indicates that the main executable has a dependency on /usr/lib/libwep (which it doesn't), so I wonder if some kext is involved with this.


You're seeing this issue now because certain parts of Xcode are running with tightened security measures called library validation. The system will only allow processes with LV enabled to use libraries that are provided by the OS or which have the same team identifier as the main executable's code signature.


Any executable which requires library validation will fail to run on systems with WebSense. This problem is not unique to Xcode, Simulator, Instruments, and IB. It's just that Xcode 7 is one of the first adopters of library validation.


I suggest that you reach out to WebSense to report the problem and request an update that won't inject their library into LV-enabled processes.

Posted by
jeremyhu
Up vote reply of jeremyhu Down vote reply of jeremyhu
Add a Comment

Is there any updated on this? I am also using websense and installed xCode 7 today and can't get it to work (no simulators and storyboard not loading).

Posted by
naveed.iqbal
Up vote reply of naveed.iqbal Down vote reply of naveed.iqbal
Add a Comment