Hi,I cannot connect a first generation iPad running iOS 5.1.1 to XCode 7 Beta. XCode 7 Beta requires a device running with at least iOS 6.0 or later.Has support for devices running less than iOS 6.0 been dropped? Or is it just because it's a Beta.Thanks, David
Search results for
5.1.1
400 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Well, considering Xcode 5.1.1 is still allowed, it seems that 7.x will not be mandated for some time. Beyond 2016 I'd guess.Why do you ask?
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Tags:
UPDATED FOR Xcode 7In Xcode 7.0, I have not been able to install or uninstall apps with simctl.And there is a typo in the simctl help:$ xcrun simctl help ... get_app_container Print the path of the **intsalled** app's container ...Reproduce$ export DEVICE=F24BE4F9-36C5-4842-84A4-1EA2614B8A3E $ export APP=/path/to/CalSmoke-cal.app $ xcrun simctl boot $DEVICE $ xcrun simctl install $DEVICE $PATHExpectedTo see the app installed on the target simulator.FoundThe command hangs indefinitely. Xcode 7 GM$ xcrun simctl install $DEVICE $PATH An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=2): Failed to install the requested application An application bundle was not found at the provided path. Provide a valid path to the desired application bundle.The APP does exist at path.The Simulator log shows that `backboard` is not loaded; that log message repeats indefinitely.$ tail -f ~/Library/Logs/CoreSimulator/F24BE4F9-36C5-4842-84A4-1EA2614B8A3E stern CoreSimulatorBridge[8316]: Requesting inst
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
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:
Topic:
Developer Tools & Services
SubTopic:
General
Tags:
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:
I'm seeing the same issue. I'm building with a target of 5.1.1, and there are no references to iOS 5.1 anywhere in the project. Yet I get this warning on every .o file being linked. I have not found a solution yet.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
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
That message depends on if there is a legacy version of the app you're trying to download that supports a lower iOS than your 5.1.1, as an example. Apparently that dev had never put up that app with less than 5.1.1 support, so the store reponsed with the message to download at newer iOS.
Topic:
Developer Tools & Services
SubTopic:
Developer Forums
Tags:
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).
Topic:
Developer Tools & Services
SubTopic:
Developer Forums
Tags:
My app supports back to iOS 5.1.1 so I use UIActionSheet and UIAlertView. These seem to translate to the new UIAlertController pretty well. However, the color of the buttons in these views are set using window.tintColor. This is a problem in my app since I use black toolbars with white text, but do NOT want white text on light grey. You'd think that iOS would be smart enough to not render text in unreadable colors.Anyway, the only work around in iOS 8 is to set the appearnace of text views. Here's what I do in the app delegate... [[UIView appearanceWhenContainedIn:[UIAlertController class], nil] setTintColor:[UIColor colorWithRed:0 green:(float)196/255 blue:(float)181/255 alpha:1]]; [[UILabel appearanceWhenContainedIn:[UIAlertController class], nil] setTextColor:[UIColor colorWithRed:0 green:(float)196/255 blue:(float)181/255 alpha:1]];However, this does NOTHING in iOS 9 beta. I've issued a bug report since there appears to be no way to change the color of this text from window.tintColor.Does anyone
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
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Xcode 5.1.1 is still allowed now, so if that's any indication, v6.x should have a while to go.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
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
Topic:
Graphics & Games
SubTopic:
SpriteKit
Tags:
So on the WWDC 2015 video on What's New in HomeKit they have this homekit@apple.com email address to send questions to. So I did and it came bake as undeliverable. ----- The following addresses had permanent fatal errors -----<homekit@apple.com> (reason: 550 5.1.1 Recipient address rejected: User unknown)Is there an Evangelist for HomeKit or anything. Because no one seems to answer here in the forums.ThanksMark