5.1.1

You should be able to test from Xcode but you need a separate build config that doesn't include the arm64 architecture. iOS 5.1.1 devices don't know what to do with a 64 bit slice. The App Store performs some magic on the binary to make the 64 bit slice invisible to the device, but Xcode doesn't know how to do that. So you have to build a version without the 64 bit slice for testing directly from Xcode (or for ad hoc distribution for that matter).

I am having the same problem - but not with C++ code. I am getting crashes most of the time when I stop at a break point (especially when I am near or in Swift code), and 100% of the time when I launch the visual debugger.I've been testing out other projects to try and reproduce the issue - but I can only confirm it only happens in our project (You can can check out master if you want to see: https://github.com/wikimedia/wikipedia-ios)I can also confirm that one of my teammates has the exact same issue… but another one does not. So it appears to be some combination of Project setup and Environment - but I haven't been able to track anything down concrete.Unfortunately setting CLANG_ENABLE_MODULE_DEBUGGING = NO is not fixing the crash for me. (I set it to NO on the project and all dependenies in the workspace). Any other thoughts for a workaround?Stack trace:Process: Xcode [55210] Path: /Applications/Xcode.app/Contents/MacOS/Xcode Identifier: com.apple.dt.Xcode Version: 7.0.1 (8228) Build Info: IDEFrameworks-8

Xcode 5.1.1 is still allowed now, so if that's any indication, v6.x should have a while to go.

Hi Ben,I have exactly the same problem. Precisely, xcode crashes when two conditions in whichever order are met.1. An <animateWithTextures> action in a .sks file is selected in the editor.2. The attributes inspector for this particular action is active.Here is crash report.Process: Xcode [18315]Path: /Applications/Xcode-beta.app/Contents/MacOS/XcodeIdentifier: com.apple.dt.XcodeVersion: 7.1 (9061)Build Info: IDEFrameworks-9061000000000000~7Code Type: X86-64 (Native)Parent Process: ??? [1]Responsible: Xcode [18315]User ID: 299565391Date/Time: 2015-09-28 18:03:30.670 +0800OS Version: Mac OS X 10.11.1 (15B17c)Report Version: 11Anonymous UUID: 91C5D987-2FFE-B992-3001-B6B884730489Time Awake Since Boot: 2700 secondsSystem Integrity Protection: enabledCrashed Thread: 0 Dispatch queue: com.apple.main-threadException Type: EXC_CRASH (SIGABRT)Exception Codes: 0x0000000000000000, 0x0000000000000000Exception Note: EXC_CORPSE_NOTIFYApplication Specific Information:ProductBuildVersion: 7B60UNCAUGHT EXCEPTION (NSInval

Apple has allowed older Xcode to be used for submittals in the past - I believe Xcode 5.1.1 is still ok right now, so you should have no problem with 6.x

Hi ishahak2If I include the standard architectures (both 32 and 64 bits), I'm getting an error saying that apps with 64-bits can't set their target to iOS 5.1. (see below)iOS 5.1 did not properly handle fat binaries with a 64-bit slice. iOS 5.1.1 was released to address this issue and it is the lowest iOS version you can deploy back to when distributing via the App Store. Set your deployment target to iOS 5.1.1. You can then continue to build a fat binary, with 64-bit and 32-bit slices.

After doing that (I also use Sparkle), now Xcode 7 crashes when I try to export a Developer ID Signed application from the OrganizerProcess: Xcode [11920]Path: /Applications/Xcode.app/Contents/MacOS/XcodeIdentifier: com.apple.dt.XcodeVersion: 7.0 (8223)Build Info: IDEFrameworks-8223000000000000~15Code Type: X86-64 (Native)Parent Process: ??? [1]Responsible: Xcode [11920]User ID: 501Date/Time: 2015-09-18 07:52:42.112 -0400OS Version: Mac OS X 10.11 (15A282b)Report Version: 11Anonymous UUID: 98FBD7C6-A1F5-E174-F66F-39ECB5EA836CSleep/Wake UUID: 3A17E47B-4DDE-480D-BB55-042228B926E1Time Awake Since Boot: 400000 secondsTime Since Wake: 500 secondsSystem Integrity Protection: enabledCrashed Thread: 0 Dispatch queue: com.apple.main-threadException Type: EXC_CRASH (SIGABRT)Exception Codes: 0x0000000000000000, 0x0000000000000000Exception Note: EXC_CORPSE_NOTIFYApplication Specific Information:ProductBuildVersion: 7A218UNCAUGHT EXCEPTION (NSInvalidArgumentException): -[NSTaggedPointerString count]: unrecognized selector

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.

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

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.

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.