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.

If there is something that I have never done before is that I have the TCA software package (ComposableArchitecture). I seldom use Swift packages. This time, I'm just trying to submit a new software title to test this 3rd-party framework.

init?(string: String) returns an optional value. guard let url = URL(string: "https://...") else { return } let request = URLRequest(url: url) URLSession.shared.dataTask(with: request) or guard let url = URL(string: "https://...") else { return } do { let (data, _) = try await URLSession.shared.data(from: url) } catch { }

That's because you have selected 'System' as opposed to 'login' on the sidebar?

What happens if you apply the corner radius to your button guy?

I would look for a local phone number to call up. It was a very long time ago, but I once trined to correct some information in the Tax section. They never made changes despite my repeated requests.

I kind of remember that I had several applications running an FFMPEG command-line app submitted to Mac App Store some 14 years ago. In the meantime, you are not specific about your development platform, making ambiguous statements like "MacOs" and "AppStore." So which is it? Is it an iOS app or macOS application? Anyway, if you are not sure if your macOS submission does not abide by Mac App Store review guidelines, you can have your users download the command-line tool and install it on their own. I would search for 'DVD rip' at Mac App Store.

Thank you, App Review and Apple Appeals Board. The app in question has been approved. I'm taken by a surprise because there was a bitter time when Appeals Board used to take the side of the reviewer without questions and because I was ready to abandon this software submission. I don't know if the reviewer has changed his or her mind this time or if the Appeals Board has made their decision for me.