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 { }

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.

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.

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

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.

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.

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.

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) } } }

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) } } }

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

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.

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

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.

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.