Starting with iOS 18, there is a change in how the transition from an underlying view to a UIDocumentInteractionController’s preview view is animated. The transition now scales down the size of the content within the controller’s view, using the center point of the root view as the base of the transformation. This results in a smaller, compressed view centered within the root view, revealing the root view’s background, which is typically white. Even if this background color is adjusted to match elements like the navigation bar, the transformed view has non-rounded corners. I have not tested this behavior when presenting a UIDocumentInteractionController from a SwiftUI view. My question to the UIKit framework developers: Is this new behavior of UIDocumentInteractionController an intentional feature, a feature with bugs, or just a bug?

I have integrated contentUnavailableConfiguration within my view controller, which has a navigation bar, a segmented bar below the navigation bar, and a table view. The contentUnavailableConfiguration sets the new view to cover everything except the navigation bar and tab bar. I have tried to use ViewDebugger to understand the auto layout used by the contentUnavailableConfiguration, but its view is not displayed in the debugger's view hierarchy navigator. I would like to only cover the table view and keep the segmented bar, which is below the navigation bar and above the table view, visible to the user. Is it possible to do this with contentUnavailableConfiguration?

I have two Swift macro packages that have the same name for the macros inside them. When using one of them in code, I get an error. Is there a way to specify which one I want to use?

In Xcode 15.0.0 I have created a package using a template Swift Macro. I have named it 'MyMacroApple'. The template comes with #stringify macro so I have created an new app and named it 'MyMacroApp' then copy pasted the code from 'MyMacroApple' main.swift file import MyMacroApple let a = 17 let b = 25 let (result, code) = #stringify(a + b) then I have added Local package dependency to the app project and selected package product 'MyMacroApple' of Library kind to my 'pocMyApp' target. When I run the project I get the error: "No such module 'MyMacroApple'"

Storyboard segues which use @IBSegueAction will crash app if destination scene has other object with custom class on the same level as view controller. It looks like a Storyboard bug

How Apple is assuring that apps compiled against older baseSDK like for example iOS 9 are working under iOS14 without change in behavior and look? Does Apple include multiple versions of UIKit, Foundation and other core frameworks in each iOS release?

Usually I write a subclass of NSObject which implements UITableViewControllerDataSource and start to write number which leads to an autocomplete with suggestions from mentioned protocol but in Xcode12 the autocomplete returns empty list. STR: move a cursor to body of class CountriesTableDataSource start to write "numb" which should lead to an autocomplete list of methods from UITableViewDataSource class CountriesTableDataSource: NSObject, UITableViewDataSource {     let data = Locale.isoRegionCodes.map {		 Locale.current.localizedString(forRegionCode: $0) } }