Buttons with text labels are not merged with buttons with images. This is documented somewhere or mentioned in one of the WWDC 2025 videos (I forget which one). Here's a big question for you - how did you get the Back button tinted? As of iOS 26.0 beta 4, there is no way to tint a standard back button. Did you add your own button to look and work like a back button?

Show how you actually add the button and set its position. I just ran a test using constraints against the safeAreaLayoutGuide.topAnchor and the view is positioned as expected below the status bar. This is for an iPhone SE 3rd gen iOS 26 simulator. If you are relying on manually setting a view's frame based on safeAreaInsets then you must keep in mind that the insets can change. Override viewSafeAreaInsetsDidChange in your view controller and update frames as needed. But using constraints is so much simpler.

I missed another one I filed against beta 3: FB18744580 All five of these are all different issues related to tinting/coloring bugs. All five of these affect my production app under iOS 26. None of these issues appear in iOS 18 (or earlier). All of these bug reports include a trivial sample app and instructions demonstrating the bugs.

Have a look at the excludedActivityTypes property of UIActivityViewController. That lets you specify which activities you do not want to appear. The hard part is determining the activity type for the different activities. Some are listed in the documentation for UIActivity.ActivityType. Many others are not. One trick I've used is to make use of the completionWithItemsHandler. Then look at the activityType value provided to the handler when an activity is selected.

There are two issues: The use of .weekOfMonth. This is not a "number of weeks". If the result had 21 days, this doesn't give 3, for example. Drop your use of .weekOfMonth since it is not a useful component for what you are trying to do. The "strange" output is the result of your use of the DateComponentsFormatter. The formatter assumes a 28-day month. Just print the raw components. If you change the line: let result = formatter.string(from: components)! to: let result = "\(components)" then you will get correct output (once you remove the use of .weekOfMonth. 57: year: 0 month: 1 day: 26 58: year: 0 month: 1 day: 27 59: year: 0 month: 1 day: 28 60: year: 0 month: 1 day: 29 61: year: 0 month: 2 day: 0 62: year: 0 month: 2 day: 1 63: year: 0 month: 2 day: 2

I take back what I said about .weekOfMonth. Once you ditch DateComponentsFormatter, you get the correct result, even with .weekOfMonth. 57: year: 0 month: 1 day: 5 weekOfMonth: 3 58: year: 0 month: 1 day: 6 weekOfMonth: 3 59: year: 0 month: 1 day: 0 weekOfMonth: 4 60: year: 0 month: 1 day: 1 weekOfMonth: 4 61: year: 0 month: 2 day: 0 weekOfMonth: 0 62: year: 0 month: 2 day: 1 weekOfMonth: 0 63: year: 0 month: 2 day: 2 weekOfMonth: 0

What issue are you having with the change? The deprecation warning that you quoted in your question tells you what the replacement is. In short, add the encoding parameter.

You make no mention of where you are looking in Xcode for the option. First, you need to add the StoreKit configuration file to your project properly. Use Xcode -> File -> New -> File from template... Then on the template screen, scroll down to the "Other" section and select StoreKit Configuration File. Once that file is setup, you make use of it by going to Xcode -> Product -> Scheme -> Edit Scheme. Then select the "Run/Debug" tab on the left. Then select the Options tab on the right. There you will see the StoreKit Configuration option where you can select the configuration file you created as described above.

You had this: content = try String(contentsOfFile: filepath) You need this now: content = try String(contentsOfFile: filepath, encoding: .utf8) As I said, all you need to do is add the additiional encoding parameter.

You can easily submit an update to your app using Xcode 16. Just keep your app's deployment target set to iOS 17 (or 16 or 15 or even 12). The requirement is for the base SDK, not the deployment target. Anyone can create an update or even a new app that still supports anywhere from iOS 12 and later while using Xcode 16.

This has been an issue since iOS 26 beta 1. I filed a bug report then. Please do the same using the Feedback Assistant app. There are actually quite a few issues related to tinting bar button items in iOS 26. I've filed 4 separate bug reports so far (just for different tinting issues). Apple just doesn't seem to care about fixing basic UIKit bugs in iOS 26. It's frustrating. And every beta update introduces new issues related to colors. (sorry for the rant).

Maybe they are not using UIActivityViewController. It's not that hard to recreate the same user interface (I've done it myself, mostly). Then you have full control over what appears.

I updated my host to 15.6. I then crested a new macOS 26 guest. Installed Xcode 26 beta 4. Created a new test project. Added the iCloud capability and then I ran into the same issue - unable to add the device (the guest Mac) via automatic provisioning. Bummer.

This is not the place to report bugs. Use the Feedback Assistant app to report issues to Apple. Be sure you include a clear explanation of the issue and a simple test app that demonstrates the problem.

Another beta release and another round of disappointment. Not a single tint/color related issue was fixed in the beta 5. Two months of beta testing and Apple seems to want all of us to deliver purely black and white user interfaces. That or they are abandoning UIKit. I have a dozen open iOS 26 UIKit bugs. Many since beta 1. All include trivial sample apps that demonstrate the issue. And I’m talking about flat out broken behavior, not just things I wish were different. So frustrating.