Search results for

5.1.1

411 results found

Post

Replies

Boosts

Views

Activity

Reply to Error Migrating to Configurator 2
Same here tooCrashReport:Process: com.apple.configurator.xpc.MigrationService [24702] Path: /Applications/Apple Configurator 2.app/Contents/Frameworks/ConfigurationUtilityKit.framework/Versions/A/XPCServices/com.apple.configurator.xpc.MigrationService.xpc/Contents/MacOS/com.apple.configurator.xpc.MigrationService Identifier: com.apple.configurator.xpc.MigrationService Version: 1.0 (193) Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: Apple Configurator 2 [24639] User ID: 501 Date/Time: 2015-10-19 11:26:47.536 +0800 OS Version: Mac OS X 10.11.1 (15B38b) Report Version: 11 Anonymous UUID: D910531A-363D-B277-77C0-641FBCE7E824 Sleep/Wake UUID: 8300C88C-F5C1-4BB1-AE89-35B09206751C Time Awake Since Boot: 99000 seconds Time Since Wake: 10000 seconds System Integrity Protection: enabled Crashed Thread: 4 Dispatch queue: NSOperationQueue 0x7fbdf3306270 :: NSOperation 0x7fbdf3310540 (QOS: LEGACY) Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note:
Oct ’15
SensibleTableView and tvOS?
Has anyone had any success using SensibleTableView with tvOS? I'm kind of new to STV myself, so I'm not sure how hard it will be for them to port to tvOS for official support, but I figured there's a good chance an STV dev might be in this forum...If tvOS isn't supported, should I specifically avoid using STV 5.1.1 with XCode 7.1 beta 3, and stick with the official XCode for my non-tvOS development?
0
0
165
Oct ’15
Reply to Cannot run kext built on 10.11
According to Apple one must build kernel extensions against the SDK for the lowest OS version they are to support. See WWDC 2013 session 707 What's New in Kext Development. In your case this would be the 10.8 SDK. You were just lucky that the kext built with Xcode 5.1.1 and the 10.9 SDK worked on 10.8. The trick with setting the deployment target to a version lower than the SDK only works for userspace code. This makes things difficult for kernel developers that need to support older OS version since we are forced to use old Xcode versions, on old OS's, on old hardware, for developement.
Topic: App & System Services SubTopic: Core OS Tags:
Oct ’15
Cannot run kext built on 10.11
When I build a kext that uses IOLockSleepDeadline and IOLockWakeup with Xcode 7 with the MacOSX10.11.sdk, the resulting kext will not load on OS X 10.8 (even though I am specifying MACOSX_DEPLOYMENT_TARGET=10.8 and -mmacosx-version-min=10.8).Trying to load the resulting kext on 10.8 yeilds:(kernel) kxld[com.mykext]: The following symbols are unresolved for this kext: (kernel) kxld[com.mykext]: _IOLockSleepDeadline_darwin14 (kernel) kxld[com.mykext]: _IOLockWakeup_darwin14 (kernel) Can't load kext com.mykext - link failed.It looks like by the very act of compiling against the 10.11 headers (particularly IOLocks.h), the _darwin14 part is being appended.However, building using Xcode 5.1.1 with MacOSX10.9.sdk, the resulting kext loads on both 10.8 and 10.11 without modifications.In the 10.11 IOLocks.h, there are three definitions:int IOLockSleep( IOLock * lock, void *event, UInt32 interType) __DARWIN14_ALIAS(IOLockSleep); int IOLockSleepDeadline( IOLock * lock, void *event, AbsoluteTime deadline, UInt32
2
0
1.1k
Oct ’15
Xcode Crashes when Opening Storyboard
I have a Swift project that I've been developing on since Xcode 6 which contains about 8 storyboards in total. For some reason, Xcode 7 will consistently crash immediately when trying to open only one of these storyboards. I have tried downloading the latest Xcode 7.1 beta 3 but I get the exact same crash. I have already tried the following steps to no avail:Deleted ~/Library/Developer/Xcode/DerivedData folderPerformed Product Clean from Xcode and rebuilt projectRemoved xcuserdata files from .xcworkspace fileCompletely uninstalled Xcode 7.0.1 and reinstalledInstalled Xcode 7.1 beta 3I have googled around and searched for people having similar crashes, but nothing has worked yet. If anyone has faced this same problem, you're help would be greatly appreciated as I have been fighting this bug for several days now! The crash dump is pasted below:Process: Xcode [8137] Path: /Applications/Xcode.app/Contents/MacOS/Xcode Identifier: com.apple.dt.Xcode Version: 7.0.1 (8228) Build Info: IDEFrameworks-8228000000000000~5
4
0
2.4k
Oct ’15
"object file was built for newer iOS version"
After upgrading to Xcode 7.0, one of our projects is giving a boatload of linker warnings like this:ld: warning: object file (...) was built for newer iOS version (5.1.1) than being linked (5.1)The thing is, the deployment target of the project is 5.1.1, not 5.1. I can't find a 5.1 anywhere in the project (and I have searched all the files that exist in the project.) I have absolutely no idea where that 5.1 is coming from.Even if it were coming from one of the third-party precompiled libraries, why should that matter? I'm not trying to build for 5.1. I'm trying to build for 5.1.1. Why would Xcode try to link for 5.1, when the deployment target of the project is 5.1.1?When I look at the linker command, printed in the issues window, I can't see a 5.1 anywhere there either. (The only thing I see is export IPHONEOS_DEPLOYMENT_TARGET=5.1.1.)This started happening only after the upgrade to Xcode 7.0. Nothing else has changed in the project.What is causing this, and how d
2
0
9.6k
Oct ’15
Xcode Proj crashed and will not open
I was in the middle of discarding all changes I had made in a branch when Xcode crashed and now this project will not open. Is there anything I can do short of migrating all the source code to a new project? It was a fairly large app. Below is my error log:Process: Xcode [774]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 [774]User ID: 501Date/Time: 2015-10-06 17:33:02.412 -0400OS Version: Mac OS X 10.11 (15A284)Report Version: 11Time Awake Since Boot: 660 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): data parameter is nilUserInfo: (null)Hints: NoneBacktrace: 0 0x00007f
0
0
433
Oct ’15
Xcode Proj crashed and will not open
I was in the middle of discarding all changes I had made in a branch when Xcode crashed and now this project will not open. Is there anything I can do short of migrating all the source code to a new project? It was a fairly large app. Below is my error log:Process: Xcode [774]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 [774]User ID: 501Date/Time: 2015-10-06 17:33:02.412 -0400OS Version: Mac OS X 10.11 (15A284)Report Version: 11Time Awake Since Boot: 660 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): data parameter is nilUserInfo: (null)Hints: NoneBacktrace: 0 0x00007f
0
0
229
Oct ’15
Reply to Xcode cannot install or launch applications supporting the 64-bit architecture on devices running iOS versions prior to 6.0
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).
Oct ’15
Xcode cannot install or launch applications supporting the 64-bit architecture on devices running iOS versions prior to 6.0
According to apple developer site info,'deployment target' must be set to at least 5.1.1 In order to support 64 bit in iOS apps, :https://developer.apple.com/library/ios/documentation/General/Conceptual/CocoaTouch64BitGuide/ConvertingYourAppto64-Bit/ConvertingYourAppto64-Bit.htmlAs I understand it - it means that a device with iOS 5.1.1 (32 bit) should be supported (but OS below 5.1.1 is not supported). However, when the app is installed using xCode (6.4) on iPhone4(iOS 5.1.1) I get the following error: Xcode cannot install or launch applications supporting the 64-bit architecture on devices running iOS versions prior to 6.0. This configuration is supported for distribution through the iOS App Store, but cannot be used during development with Xcode. To continue, edit the Run scheme action and select a build configuration that does not include the 64-bit architecture.The error says that this this version (5.1.1) supported on appstore but not on xcode. Does it mean
3
0
3.3k
Oct ’15
Reply to Xcode 7 crash at breakpoint
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
Oct ’15