Interface Builder

RSS for tag

Build interfaces for applications without writing code using Interface Builder, an editor within Xcode.

Interface Builder Documentation

Posts under Interface Builder tag

171 results found
Sort by:
Post marked as solved
276 Views

XCode13

After updating to Xcode13 on my iMac and MacBookAir, I have the same problem on both devices? Xcode13 takes all the resources of my computer, long waiting times and crashes!? "Command CompileSwiftSources failed with a nonzero exit code" Unfortunately I do not know what to do? Any ideas or suggestions? Thanks for any help!!!
Asked Last updated
.
Post marked as solved
107 Views

Nib file not showing up in Xcode 13.0 interface builder

I am running a MacPro7,1 with Big Sur 11.6 and Xcode 13.0. When I open the main nib file for my application, the editor is completely blank -- nothing shows up. The app builds and runs as expected, so it is not like the nib has vanished. The nib has been visible recently, but I am not aware of anything unusual that I might have done to it to cause damage. The behavior repeats after a project clean, and also after closing Xcode and reopening it. Does anyone have any ideas of what might be going on, and how to fix the problem?
Asked
by Knightley.
Last updated
.
Post not yet marked as solved
59 Views

Does anyone have a replacement class for NSDrawer?

It looks like I will eventually have to reverse-engineer and replace NSDrawer for one of my MacOs apps. There has been talk here and there about doing that, and I wondered if anyone had done so and would be willing to share or give hints. For the record: (1) My use of NSDrawer is appropriate under the original human interface guidelines for it, which were "[u]se drawers only for controls that need to be accessed fairly frequently but that don't need to be visible all the time." (2) NSSplitView is not appropriate because (a) my app is text-based, and it is very disconcerting to have the text re-flowed when the extra view opens and closes, and (b) I need more than one drawer (for different sets of controls, useful in different circumstances). (3) Various other kind of view don't work because of one or more of (a) they block content in the main view, (b) they do not automatically appear at the same position relative to the main view, or (c) they do not follow the main view when the user moves  or resizes it. (Note that requirements (b) and (c) follow from Fitt's law.) My app is a program-development environment for the Scheme programming language, called "Wraith Scheme".
Asked
by Knightley.
Last updated
.
Post not yet marked as solved
345 Views

Failed to attach to IBAgent-iOS

My Xcode can't compile *.xib and this is the error: 2021-06-30 13:34:42.355 ibtoold[5240:180074] [MT] DVTAssertions: Warning in /Library/Caches/com.apple.xbs/Sources/IDEInterfaceBuilder/IDEInterfaceBuilder-19115.3/InterfaceBuilderKit/Utilities/IBAbstractInterfaceBuilderPlatformToolManager.m:495 Details: Failed to attach to IBAgent-iOS with error: Error Domain=com.apple.InterfaceBuilder Code=-1 "Encountered an error communicating with IBAgent-iOS." UserInfo={NSLocalizedFailureReason=IBAgent-iOS (5309) failed to launch and exited with status 11, NSUnderlyingError=0x7fa995b726f0 {Error Domain=com.apple.InterfaceBuilder Code=-1 "Failed to launch IBAgent-iOS via CoreSimulator spawn" UserInfo={NSLocalizedDescription=Failed to launch IBAgent-iOS via CoreSimulator spawn, NSUnderlyingError=0x7fa995b63350 {Error Domain=com.apple.InterfaceBuilder Code=-1 "Failed to handshake with platform tool" UserInfo={NSLocalizedFailureReason=Failed to open connection over FIFOs with platform tool, NSLocalizedDescription=Failed to handshake with platform tool, NSUnderlyingError=0x7fa995b5e810 {Error Domain=com.apple.InterfaceBuilder Code=-1 "" UserInfo=0x7fa995b5e840 (not displayed)}}}}}, NSLocalizedRecoverySuggestion=Please check Console.app for crash reports for "IBAgent-iOS" for further information., NSLocalizedDescription=Encountered an error communicating with IBAgent-iOS.} Object:   Method:  +_THREADSAFE_launchNewToolWithLaunchContext:executionContext:toolProxyClass:proxyDelegate:failureContext:requestingMethod:error:forReason: Thread:  <NSThread: 0x7fa9e5421b60>{number = 1, name = main} Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide. 2021-06-30 13:34:42.355 ibtoold[5240:180074] [MT] IBPlatformTool: *** Failed to launch tool with description <IBCocoaTouchPlatformToolDescription: 0x7fa995b59330> System content for IBCocoaTouchFramework-EightAndLater <IBScaleFactorDeviceTypeDescription: 0x7fa995b58980> scaleFactor=2x, renderMode.identifier=(null): Encountered an error communicating with IBAgent-iOS. (Failure reason: IBAgent-iOS (5309) failed to launch and exited with status 11): Failed to launch IBAgent-iOS via CoreSimulator spawn: Failed to handshake with platform tool (Failure reason: Failed to open connection over FIFOs with platform tool): : Failed to open FIFOs for handshaking with platform tool (Failure reason: IBAgent-iOS exited before we could handshake) /* com.apple.ibtool.errors */ /Users/white/Downloads/IAPConnect_2.16.7-POC_tmn/IAPWallet/LaunchScreen.storyboard: error: Encountered an error communicating with IBAgent-iOS.   Failure Reason: IBAgent-iOS (5309) failed to launch and exited with status 11   Recovery Suggestion: Please check Console.app for crash reports for "IBAgent-iOS" for further information.   Underlying Errors:     Description: Failed to launch IBAgent-iOS via CoreSimulator spawn     Underlying Errors:       Description: Failed to handshake with platform tool       Failure Reason: Failed to open connection over FIFOs with platform tool       Underlying Errors:         Description:          Recovery Suggestion: Try restarting your computer         Underlying Errors:           Description: Failed to open FIFOs for handshaking with platform tool           Failure Reason: IBAgent-iOS exited before we could handshake macOS: 12.0 Beta (21A5268h) Xcode: 13.0 beta (13A5155e) This happened when I upgraded my macOS and Xcode to beta versions. Now they are beta2 and this error is still there. In Console.app there are many IBAgent-iOS crashes, like below: Incident Identifier: B054FA93-708C-467C-8FFC-BCE93325E057 CrashReporter Key: 0E556268-9A0A-80A5-ED93-2D187F2B194A Hardware Model: MacBookPro17,1 Process: IBAgent-iOS [5309] Path: /Users/USER/Desktop/Xcode-beta.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/Library/Xcode/Overlays/IBAgent-iOS Identifier: com.apple.dt.Xcode Version: 13.0 (19161.15) Code Type: X86-64 (Native) Role: Unspecified Parent Process: ibtoold [5240] Coalition: com.apple.dt.Xcode [2293] Responsible Process: [4617] Date/Time: 2021-06-30 13:34:42.3555 +0800 Launch Time: 2021-06-30 13:34:42.3476 +0800 OS Version: macOS 12.0 (21A5268h) Release Type: User Report Version: 104 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000000 Exception Codes: 0x0000000000000001, 0x0000000000000000 VM Region Info: 0 is not in any region. Bytes before following region: 4299710464 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL UNUSED SPACE AT START ---> mapped file 100486000-10048a000 [ 16K] r-x/r-x SM=COW ...t_id=a2f74781 Exception Note: EXC_CORPSE_NOTIFY Termination Reason: SIGNAL 11 Segmentation fault: 11 Terminating Process: exc handler [5309] Triggered by Thread: 0 Application Specific Information: Thread 0 Crashed: 0 ??? 0x7ff7ffecc118 ??? 1 0x1004b5954 ??? 2 dyld 0x2004c2a32 dyld4::prepareSim(dyld4::RuntimeState&, char const*) + 890 3 dyld 0x2004c16b5 dyld4::prepare(dyld4::APIs&, dyld3::MachOAnalyzer const*) + 244 4 dyld 0x2004c14b4 start + 388 5 dyld 0x2004bc000 ??? Thread 1:: com.apple.rosetta.exceptionserver 0 ??? 0x7ff7ffeb9984 ??? 1 ??? 0x7ff7ffed1320 ??? Thread 0 crashed with X86 Thread State (64-bit): rax: 0x0000000000000000 rbx: 0x000000010850daf8 rcx: 0x0000000000000000 rdx: 0x0000000000000001 rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x0000000000000000 rsp: 0x0000000108bbd000 r8: 0x2cbd1c0c97070014 r9: 0x0000000000000000 r10: 0x0000000108bbd000 r11: 0x00000001089c6010 r12: 0x0000000000000000 r13: 0x00000001089c6060 r14: 0x0000000200530080 r15: 0x0000000000000000 rip: rfl: 0x0000000000000283 tmp0: 0x00000001004a4d98 tmp1: 0x00000001004a4090 tmp2: 0x00000002004dba13 Binary Images: 0x0 - 0xffffffffffffffff ??? () <00000000-0000-0000-0000-000000000000> ??? 0x2004bc000 - 0x200523fff dyld () <1051784a-31a4-3307-b922-6e65e511ff69> /usr/lib/dyld EOF
Asked
by White_CN.
Last updated
.
Post not yet marked as solved
152 Views

trying to code in C using Xcode

I am trying to write a code that recreates Pong. I am trying to use the graphic features in C, but all of the headers are different from Windows/PC features. I need to know what is needed to do graphics in C using Xcode.
Asked Last updated
.
Post marked as solved
60 Views

Multiple Xcode versions on My Mac

Hi guys. I'm currently in the need of installing a lower Xcode version on my Mac. I've been doing some research and I know this is possible but I've still got some doubts about both the process and the possible outcomes. Currently I have Xcode 13 from the App Store and I need to install Xcode 12.5. I'm also currently on an M1 Mac with macOS Big Sur v11.6 My first doubt is, would installing a lower version of Xcode take up just as much space on my hard dive as the current version I already have installed? And if so, can I install the lower version on an external hard drive? Second, can having multiple Xcode versions installed cause unexpected behavior? How can I make this process in a safe and optimized way? Any guidance that you could provide me would be well appreciated
Asked
by JSXFer.
Last updated
.
Post not yet marked as solved
2.2k Views

Thread 1: signal SIGABRT

Hello,I'm having an issue with my single view app. The build is succeeded but the excution fails. Here is the main code -- ViewController.swift --:// // ViewController.swift // Décodeur // // Created by Boustani on 9/23/19. // Copyright © 2019 Stif. All rights reserved. // import UIKit class ViewController: UIViewController { @IBOutlet weak var champMessageCodé: UITextField! @IBOutlet weak var libelléMessageDécodé: UILabel! override func viewDidLoad() { super.viewDidLoad() mettreÀJourMessageDécodé() champMessageCodé.becomeFirstResponder() } @IBAction func champTexteAChangé(_ sender: Any) { mettreÀJourMessageDécodé() } private static func décoder(message messageCodé: String) -&amp;gt; String { return String(messageCodé.reversed()) } func mettreÀJourMessageDécodé() { let texteEntré = champMessageCodé.text ?? "" let messageDécodé = ViewController.décoder(message:texteEntré) libelléMessageDécodé.text = messageDécodé } }And here is my stacktrace:2019-09-29 22:05:36.999631+0100 Décodeur[32109:3024886] Unknown class _TtC9Décodeur14ViewController in Interface Builder file.2019-09-29 22:05:37.214381+0100 Décodeur[32109:3024886] *** Terminating app due to uncaught exception 'NSUnknownKeyException', reason: '[&amp;lt;UIViewController 0x7ff368f07be0&amp;gt; setValue:forUndefinedKey:]: this class is not key value coding-compliant for the key champMessageCodé.'*** First throw call stack:( 0 CoreFoundation 0x00000001093bf8db __exceptionPreprocess + 331 1 libobjc.A.dylib 0x00000001079d6ac5 objc_exception_throw + 48 2 CoreFoundation 0x00000001093bf449 -[NSException raise] + 9 3 Foundation 0x000000010744b3a6 -[NSObject(NSKeyValueCoding) setValue:forKey:] + 289 4 UIKitCore 0x000000010bb11f8e -[UIViewController setValue:forKey:] + 87 5 UIKitCore 0x000000010bd9fcd9 -[UIRuntimeOutletConnection connect] + 109 6 CoreFoundation 0x00000001093abf21 -[NSArray makeObjectsPerformSelector:] + 305 7 UIKitCore 0x000000010bd9ca1f -[UINib instantiateWithOwner:options:] + 1810 8 UIKitCore 0x000000010bb1906b -[UIViewController _loadViewFromNibNamed:bundle:] + 382 9 UIKitCore 0x000000010bb199f5 -[UIViewController loadView] + 177 10 UIKitCore 0x000000010bb19d04 -[UIViewController loadViewIfRequired] + 172 11 UIKitCore 0x000000010bb1a524 -[UIViewController view] + 27 12 UIKitCore 0x000000010c15322b -[UIWindow addRootViewControllerViewIfPossible] + 122 13 UIKitCore 0x000000010c15391f -[UIWindow _setHidden:forced:] + 289 14 UIKitCore 0x000000010c16657e -[UIWindow makeKeyAndVisible] + 42 15 UIKitCore 0x000000010c11633c -[UIApplication _callInitializationDelegatesForMainScene:transitionContext:] + 4555 16 UIKitCore 0x000000010c11b4e6 -[UIApplication _runWithMainScene:transitionContext:completion:] + 1617 17 UIKitCore 0x000000010b95fa4e __111-[__UICanvasLifecycleMonitor_Compatability _scheduleFirstCommitForScene:transition:firstActivation:completion:]_block_invoke + 904 18 UIKitCore 0x000000010b968346 +[_UICanvas _enqueuePostSettingUpdateTransactionBlock:] + 153 19 UIKitCore 0x000000010b95f664 -[__UICanvasLifecycleMonitor_Compatability _scheduleFirstCommitForScene:transition:firstActivation:completion:] + 236 20 UIKitCore 0x000000010b95ffc0 -[__UICanvasLifecycleMonitor_Compatability activateEventsOnly:withContext:completion:] + 1091 21 UIKitCore 0x000000010b95e332 __82-[_UIApplicationCanvas _transitionLifecycleStateWithTransitionContext:completion:]_block_invoke + 782 22 UIKitCore 0x000000010b95dfe9 -[_UIApplicationCanvas _transitionLifecycleStateWithTransitionContext:completion:] + 433 23 UIKitCore 0x000000010b962d2e __125-[_UICanvasLifecycleSettingsDiffAction performActionsForCanvas:withUpdatedScene:settingsDiff:fromSettings:transitionContext:]_block_invoke + 576 24 UIKitCore 0x000000010b963988 _performActionsWithDelayForTransitionContext + 100 25 UIKitCore 0x000000010b962a95 -[_UICanvasLifecycleSettingsDiffAction performActionsForCanvas:withUpdatedScene:settingsDiff:fromSettings:transitionContext:] + 223 26 UIKitCore 0x000000010b967a48 -[_UICanvas scene:didUpdateWithDiff:transitionContext:completion:] + 392 27 UIKitCore 0x000000010c119dc8 -[UIApplication workspace:didCreateScene:withTransitionContext:completion:] + 514 28 UIKitCore 0x000000010bcd102f -[UIApplicationSceneClientAgent scene:didInitializeWithEvent:completion:] + 361 29 FrontBoardServices 0x00000001145fcd25 -[FBSSceneImpl _didCreateWithTransitionContext:completion:] + 448 30 FrontBoardServices 0x0000000114606ad6 __56-[FBSWorkspace client:handleCreateScene:withCompletion:]_block_invoke_2 + 283 31 FrontBoardServices 0x0000000114606300 __40-[FBSWorkspace _performDelegateCallOut:]_block_invoke + 53 32 libdispatch.dylib 0x000000010a757db5 _dispatch_client_callout + 8 33 libdispatch.dylib 0x000000010a75b2ba _dispatch_block_invoke_direct + 300 34 FrontBoardServices 0x00000001146380da __FBSSERIALQUEUE_IS_CALLING_OUT_TO_A_BLOCK__ + 30 35 FrontBoardServices 0x0000000114637d92 -[FBSSerialQueue _performNext] + 451 36 FrontBoardServices 0x0000000114638327 -[FBSSerialQueue _performNextFromRunLoopSource] + 42 37 CoreFoundation 0x0000000109326db1 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17 38 CoreFoundation 0x0000000109326633 __CFRunLoopDoSources0 + 243 39 CoreFoundation 0x0000000109320cef __CFRunLoopRun + 1231 40 CoreFoundation 0x00000001093204d2 CFRunLoopRunSpecific + 626 41 GraphicsServices 0x00000001115582fe GSEventRunModal + 65 42 UIKitCore 0x000000010c11cfc2 UIApplicationMain + 140 43 DeÃÅcodeur 0x00000001070f58eb main + 75 44 libdyld.dylib 0x000000010a7cc541 start + 1 45 ??? 0x0000000000000001 0x0 + 1)libc++abi.dylib: terminating with uncaught exception of type NSException(lldb)
Asked
by Stif.
Last updated
.
Post marked as solved
8.7k Views

"Can't find keyplane that supports type 8 for keyboard"?

When I first began trying to build my app, I set the device to iPhone 11. I ran the app several times in the simulator and it worked just fine. But after two days, I began to get an error (listed below) and finally my textfield wouldn't allow me to type in text at all.At first I set the keyboard for the textfield to Decimal Pad and it worked fine the first four or fives times that I ran it; but soon, I began to get the below error and finally I couldn't enter any text into the field anymore (even using my own keyboard):Can't find keyplane that supports type 8 for keyboard iPhone-PortraitChoco-DecimalPad; using 25727_PortraitChoco_iPhone-Simple-Pad_DefaultI changed the keyboard to Number Pad and now I'm getting the below error:Can't find keyplane that supports type 4 for keyboard iPhone-PortraitChoco-NumberPad; using 25686_PortraitChoco_iPhone-Simple-Pad_DefaultCould someone please let me know why this is happening? I'm in Xcode 11.2.1 if that's of any help. Please help. Thank you.
Asked
by kiwimango.
Last updated
.
Post not yet marked as solved
55 Views

Tinder app creation

Hi guys, I'm trying to build an app that functions similarly to tinder and i'm asking for some tips on that creation. I just need some brainstorm ideas of how to best create a dating swipe type app like tinder? Does anyone have any ideas on how tinder was created? How many view controllers, which is the best view controller to use/create? anything would be helpful!
Asked
by Wenh08.
Last updated
.
Post not yet marked as solved
1k Views

Xcode 13 beta has issues during build storyboards

Hello everyone! I has tried build an exists iOS app on Xcode 13 beta 4. The building process finished with issues of building storyboards. Even more, Xcode is crashed when I open this storyboard. The error: /* com.apple.ibtool.errors */ /path-to-storyboard/main.storyboard: error: Compilation Failed.     Underlying Errors:         Description: Encountered an error communicating with IBAgent-iOS.         Failure Reason: IBAgent-iOS (51126) failed to launch and exited with status 5         Recovery Suggestion: Please check Console.app for crash reports for "IBAgent-iOS" for further information.         Underlying Errors:             Description: Failed to launch IBAgent-iOS via CoreSimulator spawn             Underlying Errors:                 Description: Failed to handshake with platform tool                 Failure Reason: Failed to keep platform tool alive                 Underlying Errors:                     Description: Failed to keep launch platform tool and keep alive                     Recovery Suggestion: Try restarting your computer                     Underlying Errors:                         Description: Failed to communicate with helper tool                         Failure Reason: The tool closed the connection I see following issue in console.app: Application Specific Information: dyld4 config: DYLD_ROOT_PATH=/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot DYLD_LIBRARY_PATH= DYLD_FRAMEWORK_PATH=/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/Library/Xcode/Overlays:/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/Library/PrivateFrameworks BUG IN LIBDISPATCH: Failed to create fd to simulator memory pressure file
Asked
by axazeano.
Last updated
.
Post marked as solved
3.4k Views

Can I use the Apple San Francisco Font?

Hi,I would like to know if I can use the Apple San Francisco Font for my entire application text:SF Pro ScreenSF Pro TextAnd be able to market the application with this Font.Thanks in advance!
Asked
by maria i..
Last updated
.
Post marked as solved
124 Views

Standard value for Auto Layout constraints

Hello! I am new to iOS development and was walking through UIKit iOS App Dev Tutorial on this website. My problems start every time when I need to set leading horizontal spacing to "Standard" by removing value or selecting it in the dropdown menu. When I try to do that, the value in the field resets to previously set value and "Use Standard value" is greyed out. This is so frustrating! Even when I download complete project and try to set value myself, it still does not work! Is it an Xcode bug? My version is 13.0 (13A233)
Asked Last updated
.
Post not yet marked as solved
124 Views

"Unexpectedly found nil while unwrapping an Optional value" with UIColor

Xcode 13.0 is driving me crazy at the moment... I've got a couple of color sets (default sRGB with "Any Appearance" & "Dark") that are used in various UIViewControllers. Two of them I also use in a custom button class: class SpecialBorderButton:UIButton { override func traitCollectionDidChange(_ previousTraitCollection: UITraitCollection?) { if #available(iOS 13.0, *) { super.traitCollectionDidChange(previousTraitCollection) if (traitCollection.hasDifferentColorAppearance(comparedTo: previousTraitCollection)) { layer.borderColor = UIColor(named: "ButtonBorderColor")!.cgColor } } } } What the code does: When the theme is changed while the app is running, usually the border of a button wouldn't change until you reload the ViewController. traitCollectionDidChange is called when the theme changes and this way the border color is set properly too. The issue navigator has been throwing the same error for 3 different UIViewControllers since I installed Xcode 13: Failed to render and update auto layout status for ViewController (.....): The agent crashed The crash report in Library/Logs/DiagnosticReports says: CoreSimulator 776.3 - Device: iPhone SE (1st generation) (...simulator code...) - Runtime: iOS 15.0 (19A339) - DeviceType: iPhone SE (1st generation) myApp/SpecialButton.swift:26: Fatal error: Unexpectedly found nil while unwrapping an Optional value First of all, I don't even use the SE 1G/iOS 15 simulator but always the SE2/iOS13 one, also, I checked one of the buttons that use that class and pressed "Debug" next to "Designables Crashed" in the Attribute Inspector and it blames the same line: layer.borderColor = UIColor(named: "ButtonBorderColor")!.cgColor ... with the same error: Thread 1: Fatal error: Unexpectedly found nil while unwrapping an Optional value The reason why I'm writing this question: The color exists! I checked the spelling multiple times and also copied the name but the errors are still there. I deleted derived data, cleaned the build folder and restarted Xcode and the mac multiple times but the error never fully vanish for all 3 ViewControllers. There aren't any wonky connections to that button either (as far as I've seen). I use UIColor(named:....) with different colors in multiple other classes too (but without the custom class) and they're fine there, it's just this class that's affected, for whatever reason. How do I fix this?
Asked
by Sim2019.
Last updated
.