I think what they say is that you are advised to use TabView (in SwiftUI) if you are going to switch the entire content of the view. The Phone app seems to use a segmented control. (But who knows!?) Yet, it's used to filter the list content. Whatever it is isn't changing the entire content of the view.

Mr. Gemini who works for Google, Inc. says the following about 'iOS 26 image shrunken to 4 x 4.' Reports of images being "shrunken to 4x4" in iOS 26 refer to a visual glitch that some users experienced, which was caused by new features like CarPlay's Smart Display Zoom. This was not an intended feature of the new software, and Apple quickly addressed the issue. Here's an explanation of what happened: A new OS feature caused a visual glitch. With the release of iOS 26 in September 2025, some users reported that photos would be displayed as extremely small, 4x4 pixel images. The bug was tied to CarPlay. This issue appeared when using CarPlay and was related to a new setting called "Smart Display Zoom". Disabling this feature could resolve the problem for some users. Apple fixed it in a software update. The visual bug was never widespread and was resolved by Apple in the early 26.0.1 update, which was released just a few days after the initial public launch. The problem was a bug, not a feature. Unlike the "Liquid Glass" design or new Apple Intelligence features, the 4x4 image display was not an intended part of the iOS 26 experience.

in the last package we submitted for review, it was confirmed... That's never going to help, unfortunately. One reviewer accepts something, and another rejects it. That's because their guidelines can change. Also, it's possible that the first reviewer has simply made a mistake accepting your app. If you take it to the appeals board, I guarantee that they will reject your claim with a simple, flat rubber stamp without giving you a reason. And that will be the end of your app. You have to convince the reviewer somehow. But I wouldn't waste my time and would rather move on with my life. Just for your information, I've been in this business for 14.5 years.

As long as you give a new name like Example 2 as opposed to Example as the initial one with a new bundle ID, you can submit a new version. But you have to remove the old one. Some reviewers don't mind your leaving the old at the store. Most do mind and will reject your new submission. I have gone so far to Version 6 in this manner.

I'm sorry for the bad advice. I got mixed up. You get the said permission error for .fileImporter, not .fileExporter.

I'm trying to write to a file How!? By way of fileExporter(isPresented:document:contentType:defaultFilename:onCompletion:) ? If you use fileExporter and gets a permission error, that's most likely because you are not using the security-scoped bookmark.

Finally, ... They've made me wait for 1 hour and 35+ minutes.

You can customize the title text color and the background color of the navigation bar like the following for a workaround. import SwiftUI struct ContentView: View { @Environment(\.colorScheme) var colorScheme var body: some View { NavigationStack { VStack { Image(systemName: "globe") .imageScale(.large) .foregroundStyle(.tint) } /* .navigationBarItems( trailing: Text("Trailing").foregroundStyle(.yellow) ) */ .navigationBarTitleDisplayMode(.inline) .toolbar { ToolbarItem(placement: .principal) { Text("GGGGGGG GGGGGGG") .font(.title) .bold() .foregroundColor(colorScheme == .light ? .white : .black) } } .toolbarBackground(colorScheme == .light ? .black: .white, for: .navigationBar) .toolbarBackground(.visible, for: .navigationBar) } } }

You can customize the title text color and the background color of the navigation bar like the following for a workaround. import SwiftUI struct ContentView: View { @Environment(\.colorScheme) var colorScheme var body: some View { NavigationStack { VStack { Image(systemName: "globe") .imageScale(.large) .foregroundStyle(.tint) } /* .navigationBarItems( trailing: Text("Trailing").foregroundStyle(.yellow) ) */ .navigationBarTitleDisplayMode(.inline) .toolbar { ToolbarItem(placement: .principal) { Text("GGGGGGG") .font(.title) .bold() .foregroundColor(colorScheme == .light ? .white : .black) } } .toolbarBackground(colorScheme == .light ? .black: .white, for: .navigationBar) .toolbarBackground(.visible, for: .navigationBar) } } }

I think Error Code 1004 suggests that you have entered your domain incorrectly somewhere. What is your associated domain, and what's the domain that you give to ASAuthorizationPlatformPublicKeyCredentialProvider(relyingPartyIdentifier: )? And what's the domain stated in your apple-app-site-association file? The domain has to be consistent in all these places.

Apple, Inc. has their own reviewers go over their OS releases since they introduced MacOS Lion to the public in the summer of 2011. I suppose they have a long list of apps to catch up with since they released iOS 26 and macOS 25 on top Xcode 26 last Monday. So it may take a little while they reach your app.

Oops... I've found the cause of the transfer issue. I've reported that my application's bundle identifier as something like com.example.HelloReady3. And my Xcode project has it as something like com.example.HelloReady-3. I'm sorry for blaming you, Apple, Inc. In fact, it was all my fault.

I've created a package with Xcode 26 and used its Organizer to send it to iTunes Connect. The same issue stands. This is totally disappointing. I don't know why Organizer now requests me to enter the application name and SKU when the application itself is already registered at iTunes Connect site.

I slept on this issue overnight and thought it has something to do with the deployment of Xcode 26. It happens that it was released yesterday, I'm going to install Xcode 26 to see what happens.

I would delete existing subscription plans and create new ones with different reference names and product IDs. There was a time when existing IAP products went unusable after the reviewer rejected the app body itself. I guess that was a decade ago.