This is developer's website. You are at a wrong place to ask questions about your wife's phone.

Where does 'testDouble' come from? And what's testDouble's type?

When you have a submit-ready IAP, a new section will appear right below the Build section and above the Game Center checkbox. If you don't click on 'Select In-App Purchases or Subscriptions' to include your IAP, that will be it. The cruise ship has already sailed out. If that's the case, you have to start over and submit a software update to go with a new IAP product identifier.

State the EULA URL for your app in the description of your app. Indicate what a subscription plan enables the user to do upon purchase. Indicate what benefits are. Indicate what happens to the app after a subscription plan expires. Indicate how they can request a refund. Indicate how they can check out when their subscription plan expires. Indicate how they can cancel their auto-renewal subscription.

If you develop software in SwiftUI, you should know better. Every time you initiate an Xcode project, a new folder with a ton of data is created inside the DerivedData folder. If you duplicate an existing Xcode project, a duplicate after the Xcode project name will be created in the DrivedData folder. I occasionally go to the DerivedData folder and delete the folders that I no longer keep track of although my Mac mini gives me 512 GB of space.

What exactly is the thing that you refer to as Copyright? Are you talking about the Copyright reference of the software title at App Store Connect as shown below? If so, wouldn't it just be the matter of the new guy submitting a new software update so that he or she could edit it?

If your app has no special features beyond your website, it might get rejected in line with 4.2 Minimum Functionality.

The first screenshot you have pasted says Apple Developer Program License Agreement has been updated. And the last screen suggests that you have a link to the said agreement. So if you click on the link and then scroll down to the bottom, what do you see? By the way, you are showing your name and your company name at the top-right corner of two screenshots. You shouldn't. There are bad people here and there. You never know who intends to impersonate you and your company.

returned from songs from the user library How!? Unless you explain how, I'm afraid the song variable that you refer to means nothing to the rest of the world. If you access this URL ( https://itunes.apple.com/search?term=classical+music&entity=song ), in the meantime, with URLSession, it will return two objects: resultCount and results. And you can easily return a dataset in the form of a JSON object. The results returns an array of dictionaries including a property named 'releaseDate.' Additionally, provided that you got your dataset with MPMediaQuery.songs, I would search for the 'MPMediaItem' class. Other than that, you probably want to explain how you get your data.

They are known to use an iPad to test the iOS app you submit regardless of the intended platform. I would ask them to send me a screen-capture video. But I don't know if they comply. I don't remember if they have ever sent me a screen-capture video. It's true that they sometimes go terribly wrong. Back in July, they claimed that nothing had happened in making an in-app purchase. It has turned out he or she failed to scroll down further and tapped an image, not a button. The same reviewer also claimed that a user would not be able to request customer support at our web site when in fact it was just the matter of scrolling down further, again, to find a comment box. I would send them a screenshot after circling the button they are supposed to tap to make sure he or she is not off the track. It's true that I sometimes make a mistake and deserve to get my software submissions rejected. But reviewers collectively make more mistakes than I do. I say they are wrong 2/3 of the times.

Since the minimum of deployment version that Xcode 26 supports is iOS 15.0, according to Gemini, I suppose, it should recognize your phone. And you are not able to run the iPhone 7 Simulator?

Depending on your minimum deployment version, isn't it just the matter of a elimination game with UIDevice.current.name? import SwiftUI struct ContentView: View { var body: some View { VStack { ... } .onAppear(perform: { let device = UIDevice.current print("1 \(device.name)") // iPhone 16 Pro print("2 \(device.systemName)") // iOS print("3 \(device.model)") // iPhone print("4 \(NSUserName())") // mobile print("5 \(device.description)") // <UIDevice: 0x28048dd70> //print("6 \(device.model)") // iPhone }) .padding() } }

The brother app went through the review process two days ago. The new app in question went through the review process successfully an hour ago. So why the toolbar item images from Assets.xcassets were miniaturized into 4-by-by tiny images possibly under iOS 26? I have no clue. As a possible remedy, I have created 3 scale versions for each toolbarItem image at the exact sizes (84 px, 56 px, 28 px) as opposed to just one image having the app resize it. I was pretty much prepared to abandon this new app. I'm kind of surprised that it has gone through the review process without a hitch

If you use an M1 MacBook Air with 8 GB of memory, you may not be able to open multiple Xcode projects. I had one 2 and a half years ago at work. It often hung up. Also, depending on how much you write code, Xcode projects can quickly fill up your SSD. My M2 Mac mini has 512 GB space with an external HD taken from an old iMac machine. Each week, I create a few dozen Xcode projects in SwiftUI and lose several GB to them. So I end up deleting old data folders in DrivedData. As you probably, you cannot increase memory or swap SDDs with machines with Apple-made chips.

I have reluctantly upgraded my iPhone 14 to iOS 26 to run the new app that has been rejected. I don't see the 4-by-4 toolbar item image glitch. Meanwhile, I've sent a software update of the brother app with each image having three separate scale versions (@1x, @2x, @3x). So the image of each toolbar button is no longer resized as follows. Button { } label: { Image("ToolbarImage1") } Hopefully, I'll find out if a reviewer reports the same 4-by-4 toolbar item image glitch in a few days.