xcode9

Is there a way to tell XCode fold methods/functions by default when opening a file? Not sure if this is an OS change, or an Xcode change, but on Lion with Xcode 4 , some of these commands cited by Griffo are performed with the Option modifier (the ⌥ key), not control. I've made some changes to reflect this: Fold ⌥⌘← option+command+left Unfold ⌥⌘→ option+command+right Unfold All ⌥U option+U Fold Methods/Functions ⌥⌘↑ option+command+up Unfold Methods/Functions ⌥⌘↓ option+command+down Sorry to necro a thread, but I thought this was worthwhile to revise. If you want to fold / unfold specific

How do I get Xcode to build an OS X app in release mode? I can only seem to find instructions for earlier versions and none of the screenshots match. I didn't see anything when I put "release" into the help menu's search. skyline75489 In Xcode 6 - 10: Choose Product -> Scheme -> Edit Scheme . Change the Build Configuration under the Info tab. Shortcut: hold Alt ⌥ and click the run button ▶ . The easiest way with a project that has the default set up for schemes is just to do Product -> Build For -> Profiling. When you want to generate a release build, choose Product -> Archive. That is a

While running a project into the simulator, it crashes after booting: Crash: 'NSInternalInconsistencyException', reason: 'Device <redacted>, Booted) is available but has no defaultDisplay' I already cleaned the project files and changed the iOS image but it crashes anyway. Any clue? ricardopereira Close all simulators and just run sudo killall -9 com.apple.CoreSimulator.CoreSimulatorService to restart the service. All simulators will launch as usual. 来源： https://stackoverflow.com/questions/51708445/ios-simulator-crashes-after-boot-with-available-but-has-no-defaultdisplay

Failed to load OMO warning (potential crash): Project with xcode 9 following warning is observed in the console during debug/release builds (iOS 11 GM/beta & iOS 10): CoreData: annotation: Failed to load optimized model at path "/Users/xyz.abc/Library/Developer/CoreSimulator/Devices/A-GUID/data/Containers/Bundle/Application/B-GUID/app-name.app/Frameworks/framework-name/mystorename.momd/mystorename 6.omo" Any custom framework (e.g. GoogleMaps, etc) that uses CD also results in this warning and potential crashes. Update: Using Xcode Version 9.1 beta (9B46) doesn't result in this warning. Note:

This morning, Xcode 9.0 (9A235) shows a new/strange Auto Complete box that is not at all what it used to be. How do I get the full auto-complete box so that autocomplete looks like how it usually does? Try: Go to Xcode > Preferences > Text Editing Under Code completion - Uncheck 'Suggest completions while typing' Quit out of Xcode and then relaunch Xcode. Go to Xcode > Preferences > Text Editing again Quit out of Xcode and then relaunch Xcode. Now go to Code completion and check 'Suggest completions while typing'. Try typing library function or enum and enjoy! Deleting the DERIVED DATA folder

After installing Xcode 9 beta, Xcode 8 gives me an error when compiling a project: Cannot find cdtool at '/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/Library/Xcode/Agents/cdtool': Cannot find a simulator runtime for platform <DVTPlatform:0x7fd67af0a930:'com.apple.platform.iphonesimulator':<DVTFilePath:0x7fd67af0a7c0:'/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform'>> . I suspect Xcode 9 modified some shared state with Xcode 8 (set a path, overwrote a file, etc.). But I've tried deleting and both Xcodes to no avail. The

I started adapting my app for iPhone X and found an issue in Interface Builder. The safe area layout guides are supposed to be backwards compatible, according to official Apple videos. I found that it works just fine in storyboards. But in my XIB files, the safe area layout guides are not respected in iOS 10. They work fine for the new OS version, but the iOS 10 devices seem to simply assume the safe area distance as zero (ignoring the status bar size). Am I missing any required configuration? Is it an Xcode bug, and if so, any known workarounds? Here is a screenshot of the issue in a test

TL;DR: Custom fonts couldn't be used programmatically before using them in a Storyboard/xib. Note: I've checked out this , tried the answers and they didn't work. I've also made sure that they're in target membership. I've noticed a strange bug while changing segment control title a custom font: segmentedControl.titleTextAttributes = NSDictionary(objects: [UIFont.init(name: "Comfortaa-Regular", size: UIFont.systemFontSize)!, UIColor.white], forKeys: [NSAttributedStringKey.font as NSCopying, NSAttributedStringKey.foregroundColor as NSCopying]) as? [AnyHashable : Any] It couldn't find the font,