5.1.1

Preview in itself is working for me but every time I try to print something it crashes with EXC_BAD_ACCESSProcess: Preview [1044]Path: /Applications/Preview.app/Contents/MacOS/PreviewIdentifier: com.apple.PreviewVersion: 8.1 (876)Build Info: Preview-876000000000000~3Code Type: X86-64 (Native)Parent Process: ??? [1]Responsible: Preview [1044]User ID: 501Date/Time: 2015-08-25 11:20:16.305 +0200OS Version: Mac OS X 10.11 (15A263e)Report Version: 11Anonymous UUID: 9B0A50CC-D131-E97A-D9FC-BEDA4B343C95Time Awake Since Boot: 12000 secondsCrashed Thread: 0 Dispatch queue: com.apple.main-threadException Type: EXC_BAD_ACCESS (SIGSEGV)Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000018Exception Note: EXC_CORPSE_NOTIFYVM Regions Near 0x18:--> __TEXT 00000001052a5000-0000000105468000 [ 1804K] r-x/rwx SM=COW /Applications/Preview.app/Contents/MacOS/PreviewApplication Specific Information:objc_msgSend() selector name: shouldPrintPerforming @selector(doPrint:) from sender NSButton 0x7fe68d716ee0Global Trace Buffer

It might be my WindowServer crashing. There are a lot of these and the timing seems to be close.Process: WindowServer [7583]Path: /System/Library/Frameworks/CoreGraphics.framework/Versions/A/Resources/WindowServerIdentifier: WindowServerVersion: 1Code Type: X86-64 (Native)Parent Process: launchd [1]Responsible: WindowServer [7583]User ID: 0Date/Time: 2015-08-27 19:25:04.843 -0400OS Version: Mac OS X 10.11 (15A263e)Report Version: 11Anonymous UUID: A178737F-1D40-4A04-2AFD-5BC330EB41E0Time Awake Since Boot: 35000 secondsCrashed Thread: 0 Dispatch queue: com.apple.main-threadException Type: EXC_GUARDException Codes: 0x200000010004e68b, 0x00007fabbc15a760Thread 0 Crashed:: Dispatch queue: com.apple.main-thread0 libsystem_kernel.dylib 0x00007fff8d07dbfa _kernelrpc_mach_port_destroy_trap + 101 libsystem_kernel.dylib 0x00007fff8d081c0b mach_port_destroy + 172 com.apple.CoreGraphics 0x00007fff8aab97f1 process_connection_event_ping_port_death + 36953 com.apple.CoreGraphics 0x00007fff8aab668d WSTerminateMatchingConnect

If the past is any indication, you can continue to use slightly older Xcode versions when a new version is released. Note that the minimum at this moment is Xcode 5.1.1 (logical SDK requirements still apply).

Cool thanks KMT, what do you mean by Logical SDK Requirements still apply? And what are you going by to say Xcode 5.1.1 is the minimum?

As an example, Xcode 6.4 can't support iOS 9.x, so logically, that means you'd need to accept a lower iOS when using it to build for the store. There were several different SDKs used from Xcode 5.1.1 up to now, so the version of Xcode you use will mandate which SDK and which iOS version(s) you can expect to support.As for Xcode 5.1.1, it's common knowledge that when submitting an app to the store, you can expect to see a dialog alerting to which version Xcode is currently allowed as minimum. At this time, that dialog warns the dev to use Xcode 5.1.1 or higher.

In the past, Apple has allowed older Xcode versions to be used for submittal - as an example, Xcode 5.1.1 was very recently still being noted as the minimum version allowed.

I'm having the same problem. I'm building against the OS X 10.8 SDK (copied from the Xcode 5.1.1 bundle). My deployment target is also 10.8.The root of the problem seems to be that clang is automatically linking in the static library /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/arc/libarclite_macosx.a. As the linker error notes, this library references the symbol objc_readClassPair. However, that function wasn't added to libobjc until OS X 10.10. Hence, when linking against an earlier version, the symbol can't be found, and linking fails.I can get my project to link successfully by building against the 10.11 SDK. However, the resulting binary is still going to reference a function that isn't present on pre-10.10 systems. If _ARCLite__load is invoked on such a system, objc_readClassPair will be NULL, so presumably the app is going to crash. For that reason, this seems like a bug.

I'm building against the OS X 10.8 SDK (copied from the Xcode 5.1.1 bundle).Huh? You copied the SDK from one version of Xcode and are using it in another? That’s not supported. The SDKs included in a given version of Xcode are the only SDKs supported by that SDK.Why are you doing this?Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Edit: Nevermind, just found the answer: Apps built against earlier SDKs will behave as they always have.Hi AucoI don't think this is true though? My app's deployment target is set to 5.1.1, but my app fails on my iOS 9 device.