Howdy, I have a UITableView which is embedded deeply (i.e. nested in other views) within another UIScrollView for reasons. It seems that in order to get this outer UIScrollView to scroll properly, I have to constrain the height of this UITableView ahead of time. My problem is that I can't figure out how to calculate this height quickly with dynamically sized cells (thus contentSize and related methods won't work). The best method I have been able to come up with is to scroll to each cell individually and fetch their height ahead of time sometime during/after layout, which is less than ideal... I imagine I could also adjust the height as cells are being loaded, but that doesn't sound like good user experience (scroll view keeps growing, wouldn't it be choppy?). On quick investigation, it seems that a regular (i.e. non-embedded) UITableView is able to get an accurate height of dynamically sized cells ahead of time (as seen by the scroll bar). I'm curious if this means that there is something I am missing? I'm sure there is a lot left for me to learn. I will appreciate any help. Thanks, smkuehnhold

got warnings as below every time I perform segue: [Assert] UINavigationBar decoded as unlocked for UINavigationController, or navigationBar delegate set up incorrectly. Inconsistent configuration may cause problems. navigationController=<UINavigationController: 0x10bf01280>, navigationBar=<UINavigationBar: 0x10bab7c80; frame = (0 0; 0 50); opaque = NO; autoresize = W; layer = <CALayer: 0x118e83f80>> delegate=0x10bf01280 Seems it does not direct crash my App directly since I always got this warning after a new iOS (forgot which version). But I got a crash as the attached report, not sure any relation with this warning, or due to another cause, thank you for your help. 2023-01-12, 05-24.crash

2022-11-10, 17-40.crash

Hi, I wrote a simple auto layout constraint below and used a force change orientation method to present a full-screen landscape view controller. imageView.topAnchor.constraint(equalTo: safeAreaLayoutGuide.topAnchor, constant: 16) After the landscape view controller is dismissed, the safe area guide seems broken, the top safe area insets change to zero, and call layoutIfNeeded() won't fix this issue. The only way to fix this is back to Home Screen and reopen the app. This problem occurred on the iPhone SE simulator, newer devices with a notch don't have this issue. Does anybody know how to fix this? func forceOrientation(orientation: UIInterfaceOrientation) {     let value = orientation.rawValue     if #available(iOSApplicationExtension 16.0, iOS 16.0, *) {         let windowScene = UIApplication.shared.connectedScenes.first as? UIWindowScene         var interfaceOrientations: UIInterfaceOrientationMask = []         switch orientation {         case .portrait:             interfaceOrientations = .portrait         case .landscapeLeft:             interfaceOrientations = .landscapeLeft         case .landscapeRight:             interfaceOrientations = .landscapeRight         case .portraitUpsideDown:             interfaceOrientations = .portraitUpsideDown         case .unknown:             interfaceOrientations = .portrait         @unknown default:             interfaceOrientations = .portrait         }         windowScene?.requestGeometryUpdate(.iOS(interfaceOrientations: interfaceOrientations))     } else {         UIDevice.current.setValue(value, forKey: "orientation")         UINavigationController.attemptRotationToDeviceOrientation()     } }

I am running this on MacOS, Xcode version 11.6. In order to run this code you must add com.apple.security.network.client with the value true to your entitlements file. I want to enable the Inspector for WKWebView. I have created an NSViewRepresentable to encapsulate the WKWebView. Here is the simplified code: struct WKWebViewRepresentable: NSViewRepresentable { &#9;&#9;var urlToDisplay: URL? &#9;&#9;var enableDeveloperTools: Bool = false &#9;&#9;func loadData(wkWebView: WKWebView) { &#9;&#9;&#9;&#9;if let url = urlToDisplay { &#9;&#9;&#9;&#9;&#9;&#9;wkWebView.load(URLRequest(url: url)) &#9;&#9;&#9;&#9;} &#9;&#9;} &#9;&#9;func makeNSView(context: Context) -> WKWebView { &#9;&#9;&#9;&#9;let wkWebView = WKWebView() &#9;&#9;&#9;&#9;wkWebView.configuration.preferences.setValue(enableDeveloperTools, forKey: "developerExtrasEnabled") &#9;&#9;&#9;&#9;loadData(wkWebView: wkWebView) &#9;&#9;&#9;&#9;return wkWebView &#9;&#9;} &#9;&#9;func updateNSView(_ wkWebView: WKWebView, context: Context) { &#9;&#9;&#9;&#9;loadData(wkWebView: wkWebView) &#9;&#9;} &#9;&#9;func makeCoordinator() -> Coordinator { &#9;&#9;&#9;&#9;return Coordinator(self) &#9;&#9;} } extension WKWebViewRepresentable { &#9;&#9;class Coordinator: NSObject { &#9;&#9;&#9;&#9;init(_ parent: WKWebViewRepresentable) { &#9;&#9;&#9;&#9;&#9;&#9;super.init() &#9;&#9;&#9;&#9;} &#9;&#9;} } and with this code in place I can create the following ContentView: struct ContentView: View { &#9;&#9;static let demoURL = "https://" + "www.apple.com/apple-music/" &#9;&#9;var body: some View { &#9;&#9;&#9;&#9;HStack { &#9;&#9;&#9;&#9;&#9;&#9;WKWebViewRepresentable(urlToDisplay: URL(string: ContentView.demoURL), enableDeveloperTools: true) &#9;&#9;&#9;&#9;&#9;&#9;WKWebViewRepresentable(urlToDisplay: URL(string: ContentView.demoURL), enableDeveloperTools: false) &#9;&#9;&#9;&#9;} &#9;&#9;} } The good news is that the above code actually works. If you right click on the left hand side, you can select Inspect Element which will start the Inspector. The idea is that I would do discovery on the left hand side and do show the processed result on the right hand side. That part is obviously not in the code. For testing purposes the right hand side simply shows the same content as the left hand side. I would like to see that the user is being able to split the real-estate between the two views, hence I replace the HStack with HSplitView, no other change. When you run this code, the WkWebView's come up as before but one you select Inspect Element the place where the Inspector should show is blank (black or white depending on dark mode), it starts flashing etc. By dragging inside that rectangle, it becomes clear that the code is actually running just not properly rendering. This stackoverflow - https://stackoverflow.com/questions/60727065/wkwebview-web-inspector-in-macos-app-fails-to-render-and-flickers-flashes article, mentions the same problem and it suggests that autolayout should be disabled. Does anyone know a trick to circumvent this layout problem for SwiftUI?

So I have a stack view and the profile image needs to go next to the the username and stay there. How do I do that in this arranged stack view without conflicts because I have tried to anchor it to the top. Like this but no results: But I am actually getting: Here is the code for the stack view:     override init(style: UITableViewCell.CellStyle, reuseIdentifier: String?) {         super.init(style: style, reuseIdentifier: reuseIdentifier)         contentView.addSubview(profileImageView)         contentView.addSubview(profileNameLabel)         contentView.addSubview(userHandel)                                    profileImageView.setContentHuggingPriority(.defaultHigh, for: .horizontal)                                                               let innerPostStackView = UIStackView(arrangedSubviews: [profileNameLabel, userHandel, postTextLabel])         innerPostStackView.axis = .vertical                       let postStackView = UIStackView(arrangedSubviews: [profileImageView, innerPostStackView])         postStackView.translatesAutoresizingMaskIntoConstraints =  false         postStackView.alignment =  .center         postStackView.spacing = 10         contentView.addSubview(postStackView)                           NSLayoutConstraint.activate([                          postStackView.leadingAnchor.constraint(equalTo: contentView.leadingAnchor, constant: 10),             postStackView.trailingAnchor.constraint(equalTo: contentView.trailingAnchor, constant: -15),             postStackView.topAnchor.constraint(equalTo: contentView.topAnchor, constant: 10),             postTextLabel.bottomAnchor.constraint(equalTo: contentView.bottomAnchor, constant: -15)                                         ]) Hope someone can help.

i have the next problem, i have a scroll view that contains an stack view in the center of my app, but in the botton of the view i have some checkbox, sometimes the user got 1, sometimes the user got 3. how i can move the scroll view to the top when the 3 checkbox are enable. to explain this in a graphic way and in a more common problem. Imagine that the checkbox are the keyboard, they go up (because it take more space when 3 checkbox are enabled) and i need to move the content of my app and maintain the content always in the visible rect of the scroll view. I cant use a simple view since the icons inside my scroll view had to have always the same size. all my constraints are made in a xib file. i dont want the full solution just ideas of what i can do or how i can face this problem. this is what i want , left image are devices like pro max series and right image the smaller ones, like SE 1st gent. Thanks

Hello I set a few constraints on a UIView in the storyboard. The height constraint is set to 300 and has a size class variation set on 350 (see screenshot). In my code, I modify the constraint and set its constant to 100. When I call that code, I see the view changing correctly its height to 100. But If I go to homescreen ( app in background) and come back to the app, the height of the view is set back to the old value (300). This problem only appears when the constraint has a size variation. When I remove the variation on the height, the behaviour is ok, the height stays at 100 when I go to homeview and switch back to the app. Is that a bug of AutoLayout ? Is there a workaround ? (tested with iOS16, on iPhone Xr and iPhone 14 Pro, xcode 14) class ViewController: UIViewController {     @IBOutlet weak var heightConstraint: NSLayoutConstraint!     override func viewDidLoad() {         super.viewDidLoad()     }     @IBAction func buttonPushed(_ sender: Any) {         heightConstraint.constant = 100; // works ok until app goes background     } }

Hello everyone. I just discovered one issue with List in iOS16. The sample Playground code is provided below. Steps to reproduce: Run the code. Scroll down the list to the bottom so first rows become hidden. Scroll up to first row. Tap on first row. Result: row is marked as selected but its size stays unchanged. Once you scroll the list up and down this row will resize itself. Expected result: row resize immediately after tap on it. Note that if you don't perform steps 2 and 3 (maybe cells are not being reused) it works as expected. Also on iOS 14, 15 it works as expected import PlaygroundSupport struct Item: Identifiable, Equatable {     let id: String     let name: String } struct App: View {          @State var items: [Item] =   [Item(id: "0", name: "Apples"),                                   Item(id: "1", name: "Oranges"),                                   Item(id: "2", name: "Bananas"),                                   Item(id: "3", name: "Pears"),                                   Item(id: "4", name: "Mangos"),                                   Item(id: "5", name: "Grapefruit"),                                   Item(id: "6", name: "Peaches"),                                   Item(id: "7", name: "Qiwies"),                                   Item(id: "8", name: "Strawberries"),                                   Item(id: "9", name: "Lemons"),                                   Item(id: "10", name: "Limes"),                                   Item(id: "11", name: "Pineapples")]     @State var selections: [Item] = []         var body: some View {         List(items) { item in             MultipleSelectionRow(title: item.name, isSelected: selections.contains(item)) {                 if selections.contains(item) {                     selections.removeAll(where: { $0 == item })                 }                 else {                     selections.append(item)                 }             }         }     } } struct MultipleSelectionRow: View {     var title: String     var isSelected: Bool     var action: () -> Void          var body: some View {         HStack {             Text(title)             if isSelected {                 Spacer()                 Image(systemName: "checkmark")             }         }         .frame(height: isSelected ? 120 : 60)         .onTapGesture {             action()         }     } } PlaygroundPage.current.setLiveView(App().previewDevice("iPhone 13"))

first, I am using a translator. Please understand. want to add buttons using Auto Layout on a large image. Auto layout applied but button position incorrectly //let screenHeight = UIScreen.main.bounds.size.height Currently, the height was obtained through the above method and automatic layout was applied to each. However, too many situations had to be considered when trying to apply the iPad. Isn't there a better way?

Hi, I have an NSOutlineView, and each cell within that has an NSCollectionView (a horizontal one), setup using autolayout with the 'height' of the collectionView driving the height of the OutlineView cell. Each item in the collectionView can have a dynamic width, and I use a 'dummy' collectionView to size each item from it's contents, then getting the height of the collectionView and using a 'height constraint' to make each collectionView get the height it needs (and hence the cell have a dynamic height. It works fine for the most part, but I get this warning multiple times in the console: "The behavior of the UICollectionViewFlowLayout is not defined because: the item width must be less than the width of the UICollectionView minus the section insets left and right values, minus the content insets left and right values. The relevant UICollectionViewFlowLayout instance is <NSCollectionViewFlowLayout: 0x10e3b7f80>, and it is attached to <MacTagsCustomCollectionView: 0x10e3b7840>. Make a symbolic breakpoint at UICollectionViewFlowLayoutBreakForInvalidSizes to catch this in the debugger." I've tried Googling this, but I can't find a good explanation for this issue. Also, I'm not sure why it references 'UICollectionViewFlowLayout' when it's an AppKit app and uses NSCollectionView. Also, setting the 'UICollectionViewFlowLayoutBreakForInvalidSizes' symbolic breakpoint doesn't help since it never gets triggered. Here is some code from my outlineView's viewForTableColumn, where I get the height of the collectionView and hence the height of the cell: result = [outlineView makeViewWithIdentifier:@"DataWithTags" owner:self]; if (result.tagListCollectionView.delegate == nil) { result.tagListCollectionView.delegate = self; result.tagListCollectionView.dataSource = self; result.tagsCollectionViewScrollView.automaticallyAdjustsContentInsets = NO; result.tagListCollectionView NSNib *cellNib = [[NSNib alloc] initWithNibNamed:@"MacTagsForPersonItem" bundle:nil]; [result.tagListCollectionView registerNib: cellNib forItemWithIdentifier:@"PersonTagsCollectionViewItemID"]; if (self.tagsSizingItem == nil) { NSArray *topLevelObjects; [cellNib instantiateWithOwner:self.tagsSizingItem topLevelObjects: &topLevelObjects]; for (id topLevelObject in topLevelObjects) { if ([topLevelObject isKindOfClass:[MacPersonTagsCollectionViewItem class]]) { self.tagsSizingItem = topLevelObject; break; } } } result.tagListCollectionView.backgroundColors = @[[NSColor clearColor]]; result.tagListCollectionView.enclosingScrollView.backgroundColor = [NSColor clearColor]; result.tagsCollectionViewScrollView.verticalScroller.hidden = YES; } result.tagListCollectionView.tagsPerson = person; [result.tagListCollectionView reloadData]; result.frame = outlineView.bounds; [result layoutSubtreeIfNeeded]; [result.tagListCollectionView layoutSubtreeIfNeeded]; if (person.tagsCacheHeight == 0) { &#9; person.tagsCacheHeight = result.tagListCollectionView.collectionViewLayout.collectionViewContentSize.height; } result.collectionViewHeightConstraint.constant = person.tagsCacheHeight; Anyone with any idea on how to overcome this? I feel that it's responsible for some layout issues that I'm having in the view.

I have a collection view with vertical flow layout. On bigger iPhones there is empty space after the 5 items in the row. Height and width and fixed at 30. There is empty space horizontally after the 5th item in the row. If i turn height and width constraint to be 'greater that of equal to' then i see just 3 items in the row and the remaining 2 appear in the row below. I find constraints very challenging and want guidance with setting them right so that the items resize on all screens to have exactly 5 items in a row from edge to edge of the collection view.

I've upgraded to Xcode 14 and iOS 16, and now the app has a layout glitch when moving to new screens. You can see in the gif below the text and buttons move in the first few milliseconds when moving to a new screen. Any idea how to fix this? https://media.giphy.com/media/lhGlbU4YXlx1RGlaW0/giphy.gif

Hi, I think the size classes for iPhone 14 and iPhone 14 Pro are wrong in the Apple documentation. I don't think they have "regular height" in landscape orientation. https://developer.apple.com/design/human-interface-guidelines/foundations/layout/

Hello guys! I'm having this weird issue with a basic compositional layout (full screen cell with horizotal swiping), on a collection view: whenever I rotate the device, it's showing the wrong cell. I think this is a problem of the content offset, because it's always jumping to the previous image (2nd to 1st, 3rd to 2nd, etc.), and this is even before the rotation started (I tried setting the cell manually in viewWillTransition, but it also jumps). And when i come back to portrait, it returns to the "original" image. Here is a gif with the slow animation: https://gifyu.com/image/S3M3d. Note that on the video the cell is changing from 2nd to 1st, but if I'm on the 3rd cell, it changes to the 2nd one. So it seems it's always to the previous one. This is the layout definition: let itemSize = NSCollectionLayoutSize( widthDimension: .fractionalWidth(1), heightDimension: .fractionalHeight(1) ) let layoutItem = NSCollectionLayoutItem(layoutSize: itemSize) layoutItem.contentInsets = .zero layoutItem.edgeSpacing = NSCollectionLayoutEdgeSpacing(leading: .none , top: .none, trailing: .none, bottom: .none) let groupSize = NSCollectionLayoutSize(widthDimension: .fractionalWidth(1), heightDimension: .fractionalHeight(1)) let layoutGroup = NSCollectionLayoutGroup.vertical(layoutSize: groupSize, subitems: [layoutItem]) layoutGroup.interItemSpacing = .fixed(0) let layoutSection = NSCollectionLayoutSection(group: layoutGroup) layoutSection.interGroupSpacing = 0 layoutSection.orthogonalScrollingBehavior = .groupPaging let collectionViewLayout = UICollectionViewCompositionalLayout(section: layoutSection) let collectionView = UICollectionView(frame: .zero, collectionViewLayout: collectionViewLayout) collectionView.translatesAutoresizingMaskIntoConstraints = false collectionView.backgroundColor = .clear collectionView.bounces = false collectionView.isPagingEnabled = true collectionView.showsHorizontalScrollIndicator = false collectionView.delegate = self collectionView.dataSource = self collectionView.register(CustomCell.self, forCellWithReuseIdentifier: "...") I've tried everything (removed every spacing, inset, and all that I could find), but I can't make it work. Any ideas? It's been driving me crazy. Thanks in advance.

Hi everyone, our team was transferred a project that is using a "UICollectionViewCompositionalLayout" for displaying a large amount of data. On iOS 14 and below, we seemed to be having no problems. Now on iOS 15 however, we keep getting this debugger message: APPNAME[47924:507017] [UICollectionViewRecursion] cv == 0x7ff2af9d0200 Disabling recursion trigger logging We are also collecting crashes in our crash tool, solely from iOS 15 devices, saying: NSInternalInconsistencyException: UICollectionView (<UICollectionView 0x1122a6400>) is stuck in its update/layout loop. This can happen for many reasons, including self-sizing views whose preferred attributes are not returning a consistent size. To debug this issue, check the Console app for logs in the "UICollectionViewRecursion" category. We've found that setting all .estimated() sizes we're using in the section provider to .absolute() gets rid of the message, but of course the views aren't sized correctly then. We are using views that size themselves based on the content they display, using UIStackViews. We need them to be dynamic in height. Has something changed moving from iOS 14 to 15 about how the compositional layout has to be configured? Is there something we can do to further debug this issue? I've found some questions about this asked on StackOverflow, but none of them were answered either.

CoreAuto layout crash issue I absolutely do not have any idea, what can occure this problem and how can i reproduce. It crashes randomly. I use Crashlytics v3.14 in my project. Does anybody face with the same problem? Crashlytics : iOS Crash : CoreAutoLayout _col_rawAddForEngineVar Crash Item : _col_rawAddForEngineVar Issue Details : Crashed: com.apple.main-thread 0 CoreAutoLayout 0xbb20 _col_rawAddForEngineVar + 180 1 CoreAutoLayout 0x5990 _engineVar_addForVariableIfNeeded + 464 2 CoreAutoLayout 0x152f0 -[NSISLinearExpression setCoefficient:forVariable:] + 56 3 CoreAutoLayout 0xc9e8 -[NSLayoutConstraint _lowerIntoExpression:reportingConstantIsRounded:] + 188 4 CoreAutoLayout 0xef4c -[NSLayoutConstraint _addToEngine:mutuallyExclusiveConstraints:] + 140 5 UIKitCore 0x1df1ec __57-[UIView(AdditionalLayoutSupport) _switchToLayoutEngine:]_block_invoke_2 + 372 6 CoreAutoLayout 0x85c4 -[NSISEngine withBehaviors:performModifications:] + 88 7 UIKitCore 0x1ccf70 __57-[UIView(AdditionalLayoutSupport) _switchToLayoutEngine:]_block_invoke + 560 8 UIKitCore 0x3ba200 -[UIView(AdditionalLayoutSupport) _switchToLayoutEngine:] + 216 9 UIKitCore 0x1df134 __57-[UIView(AdditionalLayoutSupport) _switchToLayoutEngine:]_block_invoke_2 + 188 10 CoreAutoLayout 0x85c4 -[NSISEngine withBehaviors:performModifications:] + 88 11 UIKitCore 0x1ccf70 __57-[UIView(AdditionalLayoutSupport) _switchToLayoutEngine:]_block_invoke + 560 12 UIKitCore 0x3ba200 -[UIView(AdditionalLayoutSupport) _switchToLayoutEngine:] + 216 13 UIKitCore 0x1df134 __57-[UIView(AdditionalLayoutSupport) _switchToLayoutEngine:]_block_invoke_2 + 188 14 CoreAutoLayout 0x85c4 -[NSISEngine withBehaviors:performModifications:] + 88 15 UIKitCore 0x1ccf70 __57-[UIView(AdditionalLayoutSupport) _switchToLayoutEngine:]_block_invoke + 560 16 UIKitCore 0x3ba200 -[UIView(AdditionalLayoutSupport) _switchToLayoutEngine:] + 216 17 UIKitCore 0x4845c0 -[UIView(AdditionalLayoutSupport) _initializeHostedLayoutEngine] + 212 18 UIKitCore 0x1ecdd8 -[UIView _layoutEngine_windowDidChange] + 124 19 UIKitCore 0x2b6de0 -[UIView(Internal) _didMoveFromWindow:toWindow:] + 280 20 UIKitCore 0x2b706c -[UIView(Internal) _didMoveFromWindow:toWindow:] + 932 21 UIKitCore 0x1dd82c __45-[UIView(Hierarchy) _postMovedFromSuperview:]_block_invoke + 140 22 CoreAutoLayout 0x85c4 -[NSISEngine withBehaviors:performModifications:] + 88 23 UIKitCore 0x26d060 -[UIView(Hierarchy) _postMovedFromSuperview:] + 840 24 UIKitCore 0x189b90 -[UIView(Internal) _addSubview:positioned:relativeTo:] + 2152 25 UIKitCore 0x3b0638 -[UITableView _addSubview:positioned:relativeTo:] + 108 26 UIKitCore 0x178554 -[UIScrollView _addContentSubview:atBack:] + 380 27 UIKitCore 0x19e01c -[UITableView _addContentSubview:atBack:] + 252 28 UIKitCore 0x19a754 __53-[UITableView _configureCellForDisplay:forIndexPath:]_block_invoke + 1772 29 UIKitCore 0x1729a8 +[UIView(Animation) performWithoutAnimation:] + 104 30 UIKitCore 0x419dbc -[UITableView _configureCellForDisplay:forIndexPath:] + 272 31 UIKitCore 0x286ac4 -[UITableView _createPreparedCellForGlobalRow:withIndexPath:willDisplay:] + 1788 32 UIKitCore 0x484030 -[UITableView _updateVisibleCellsForRanges:createIfNecessary:] + 732 33 UIKitCore 0x2abbbc -[UITableView _updateVisibleCellsNow:] + 1432 34 UIKitCore 0x17bed8 -[UITableView layoutSubviews] + 456 35 UIKitCore 0x18c17c -[UIView(CALayerDelegate) layoutSublayersOfLayer:] + 2592 36 QuartzCore 0x407fc CA::Layer::layout_if_needed(CA::Transaction*) + 532 37 QuartzCore 0x32c60 CA::Layer::layout_and_display_if_needed(CA::Transaction*) + 136 38 QuartzCore 0x475b4 CA::Context::commit_transaction(CA::Transaction*, double, double*) + 452 39 QuartzCore 0x504a8 CA::Transaction::commit() + 704 40 QuartzCore 0x323a0 CA::Transaction::flush_as_runloop_observer(bool) + 88 41 CoreFoundation 0x410c4 CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION + 36 42 CoreFoundation 0x10080 __CFRunLoopDoObservers + 592 43 CoreFoundation 0xb13c __CFRunLoopRun + 1052 44 CoreFoundation 0x1ebc8 CFRunLoopRunSpecific + 600 45 GraphicsServices 0x1374 GSEventRunModal + 164 46 UIKitCore 0x514b58 -[UIApplication _run] + 1100 47 UIKitCore 0x296090 UIApplicationMain + 364 48 TCP App 0xbad894 main + 39 (AppDelegate.swift:39) 49 ??? 0x10674dda4 (Missing)

Hi, In an iOS app, I have a Storyboard View Controller with a UILabel on it where I set the font style to Body/Heading/whatever with dynamic fonts. This all works fine. However, is there a way in the VC code to extract that font style? I've looked at the associated font and font descriptor for the UILabel but don't see an obvious attribute for it. Any idea how to see it? I would prefer not to hardcode it and extract it from the UILabel instead. I need it as I will be modifying portions of the text (bold, etc.). Regards, Patrick

Howdy! I have a view which is constrained to a height of 0.5 and is reused in several places. When several are rendered near each other however, it becomes clear that their heights are subtly different (but enough to annoy me!). It doesn't appear as if any constraints are breaking. For additional information, I am trying to roughly replecate the appearance of the UITableView seperator in some of my views. Hints on how UIKit manages to ensure that a UITableView's seperators all appear to be the same height will also be appreciated. Thanks, smkuehnhold

In the Xcode 13 beta, where's the Vary For Traits button?