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.

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 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.

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.

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

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

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.

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.

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.

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?

Things keep changing during the beta. It's very frustrating since Apple doesn't document anywhere what the correct approach is (or will be by the end of the beta). And there's still no word on how to support alternate app icons with Icon Composer icons. I've noticed that what I posted here last became obsolete as of beta 3. iOS 18 has been showing a version of the glass icon since then. It makes much more sense for iOS 18 and lower to keep using the old Assets app icons and for iOS 26+ to use the new glass icons. I don't like the fact that Apple assumes everyone will want the new fancy iOS 26 icon to appear on devices with older versions of iOS. I'm fine with that being an option, but let developers choose how they want their apps to appear and which icons to use.

Just to keep people updated, this issue still exists using a macOS 26 beta 4 guest with Xcode 26 beta 4 on a macOS 15.5 host. I'm wondering if updating the host to macOS 15.6 will help resolve this. I'm not yet in a position to try with macOS 15.6 RC but if anyone does, please update.

This is not the place to report bugs to Apple. Use the Feedback Assistance app to submit a bug report (and attached sample app).

@DTS Engineer I've filed the following reports related to various tinting issues since beta 1. None have been resolved yet as of beta 4: FB17989300 FB17996063 FB18061370 FB18745302 I do hope these get resolved. Thanks.

iOS 26 has a lot of issues like this where it breaks how tinting works. Please file a bug report using the Feedback Assistant app. Apple needs to know that this needs to be fixed.