Craig Hockenberry:
Then, when you look at the sample code, it’s all SwiftUI. At least the sample compiles and runs because it uses a completely different syntax than what was shown at WWDC.
[…]
Eventually I stumbled upon TipUIPopoverViewController which inherits from UIViewController. That should work! […] But it didn’t: the close button on the popover didn’t work.
[…]
Until you realize that any changes you make are stored in a SQLite database, debugging is very confusing. It’s also easy for your own state to get out-of-sync with the Tip state: there is not a single source of truth.
[…]
Unfortunately, that sample code doesn’t scale well. If you have a view with multiple tips, you’re going to be littering your code with tip instances, observation tasks, and popover controllers. It’s a mess and a clear sign that the TipKit developers didn’t think much about UIKit.
Fatbobman:
In the previous article, we introduced the basic usage of TipKit. In this article, we will discuss some advanced topics related to TipKit, such as how to fully customize Tip views (not using TipView and popoverTip), how to use TipKit with UIKit, and how TipKit can share data across different applications, as well as how to reuse Tip declaration code. Additionally, we will attempt to address some common questions and concerns about TipKit.
Previously:
iOS iOS 26 Open Source Programming Swift Programming Language SwiftUI Tips.app
Joe Rossignol:
Apple’s former hardware engineering chief John Ternus officially became CEO of the company today, with the change now reflected on Apple’s leadership page.
[…]
Tim Cook is now executive chairman of Apple’s board of directors, after a 15-year run as CEO.
Apple:
John joined Apple’s product design team in 2001 and became a vice president of Hardware Engineering in 2013. He joined the executive team in 2021 as senior vice president of Hardware Engineering. Throughout his tenure at Apple, John has overseen hardware engineering work on a variety of groundbreaking products and was instrumental in the introduction of multiple new product lines, including iPad and AirPods, as well as many generations of products across iPhone, Mac, and Apple Watch.
John has led much of the company’s focus in areas like reliability and durability, introducing new techniques that have made Apple products remarkably resilient. He has also driven much of Apple’s innovation in materials and hardware design that have reduced the carbon footprint of its products, including the creation of a new recycled aluminum compound that has been introduced across multiple product lines, the use of 3D-printed titanium in Apple Watch Ultra, and advancements in reparability that have increased the life spans of several Apple products.
Prior to Apple, John worked as a mechanical engineer at Virtual Research Systems. He holds a bachelor’s degree in Mechanical Engineering from the University of Pennsylvania.
Myke Hurley (9To5Mac):
This feels like Apple really trying to remind us of a previous product-focused CEO.
[…]
I would not have predicted this [reliability and durability] angle being so prominent, so I can only assume it’s something that’s important to Ternus.
[…]
One of the key tenets of the Cook era was Apple making a series of environmental pledges. I am very happy to see this called out as something Ternus is interested in.
There’s no mention of software.
Juli Clover:
Ternus sent his first memo as CEO to employees this morning, praising Cook and sharing his excitement for Apple’s future.
Benjamin Mayo:
The 5 GB free iCloud tier lasted Tim Cook’s entire career as CEO, how will Ternus stack up?
Previously:
Apple Apple Watch Ultra Business Environment iCloud iOS John Ternus Mac Tim Cook
John Sundell:
New in Swift 6.4 […] is a warning which is emitted when a nested closure performs a weak capture while the parent closure implicitly captures that object as a strong reference.
At first glance, that new diagnostic could be a bit puzzling, since it might seem unnecessary to have to specify such a weak capture twice (or, alternatively, move it to the parent closure’s capture list), but it turns out that it’s an incredibly useful new warning that can help us avoid a quite common kind of memory management bug.
[…]
Finally, in situations where capturing self strongly doesn’t actually lead to a retain cycle, we can silence the new warning for nested weak captures by explicitly adding self to the outer closure’s capture list, such as when creating a Task within the following example[…]
Previously:
Automatic Reference Counting (ARC) Language Design Memory Management Programming Swift Programming Language
Matthias Gansrigler-Hrad:
I don’t appreciate being forced by Xcode 27 to drop support for macOS 10.13-11.0. It’s my decision which OSes I want to support, not Apple’s. Yes, I can keep Xcode 26 around until submissions require Xcode 27, but what then?
Originally, Xcode 27 was documented as supporting Big Sur on Intel Macs, but now the earliest is Monterey.
I’m frustrated, too, but it’s more honest than the recent releases that claimed to support deployment on older macOS versions when Apple clearly hadn’t tested that it actually worked. I filed bugs, and Apple kept responding that they’d fixed it, when they hadn’t.
Using old versions of Xcode isn’t a great solution because they aren’t supported on Golden Gate. Swift also makes it more difficult to call newer APIs when using an older SDK. You can’t just copy/paste a method prototype or constant value and conditionally use it when running on a newer OS.
Ighor July:
I eventually found a hidden workaround that changes the errors back into warnings. That is good news, but it does not make the concern disappear. The setting is undocumented, absent from the normal Xcode interface, and currently being tested only in a beta toolchain. The larger question is what Apple intends to enforce when Xcode 27 is final and, later, when App Store submission requirements move to its SDKs.
[…]
Apple’s current Xcode system requirements list Xcode 26 with deployment targets beginning at iOS 15 and macOS 11. Yet developers have been able to enter older targets manually. In an Apple Developer Forums discussion about Xcode 26, an Apple product manager explained that the published deployment target range is aligned with simulator support and on-device debugging. The accepted answer confirms that an iOS 13 target can still build even though it falls below the range in Apple’s table.
My own tests went further. Xcode 26.5 compiled a project targeting iOS 9.0. It warned that the target was older than the supported range, but the build succeeded. On macOS, I have compiled current apps with deployment targets as old as macOS 10.9. Xcode warned me, but it still produced working applications.
[…]
For iOS and iPadOS, staying on Xcode 26 is not a lasting option. Apple has repeatedly made a current Xcode and SDK mandatory for new App Store submissions. […] If any one of those conditions fails, iOS and iPadOS developers will have no normal App Store path for publishing new updates that still support versions older than 15.
Previously:
App Store iOS iOS 14 iOS 9 Mac Mac App Store Mac OS X 10.9 Mavericks macOS 11.0 Big Sur macOS 12 Monterey macOS 27 Golden Gate Objective-C Swift Programming Language Xcode
