This thread from nine years ago has been resurrected to say you've got the same issue on the most recent beta of macOS 26? Honestly. Read the release notes. It's a known issue.

No. All apps are expected to function correctly on every device, because customers can choose which device to run their apps on. A user can download an iPhone app and have it run in compatibility mode on an iPad, so you have to ensure that it functions correctly on all devices. By stating that your app looks "significantly better on iPhones than iPads" you are admitting that you haven't written it to function properly when it's run on an iPad. Apps like that tend to get rejected, so spend some time to fix the issues.

Isn't this a known issue in the release notes? HFS external media might fail to mount automatically. (168672160) Workaround: For macOS only, use CLI tool diskutil mount to attach the relevant disk device.

You should put screenshots of your Watch app in the Watch section, yes. And the guys at AppScreens are correct - these must be screenshots of the actual app running, not a mock-up. Your iPhone screenshots can include mock-up Watch screenshots, say if you have an iPhone next to a Watch in one mocked screenshot, but not separately. Respect the required resolutions.

You should probably raise these as bugs in the usual way. They won't really get progressed if they're only posted in these Developer Forums. You need to raise each issue you find separately at https://feedbackassistant.apple.com/ You can post the FB numbers here if you want, so that others (especially Apple employees) can link to them.

Don't hijack a thread, especially one that's almost a year old and not really related to your own app's issue. If your game is being rejected for being spam, raise a NEW post with information about YOUR app, and perhaps people can help you.

@aosiman Don't hijack a thread, especially a really old one like this. If you have an issue, raise a new post and provide some code so we can help you.

Sorry, I don't really understand your question. To run your code I have to use a simple @State variable in place of your userProfileAccountInfoviewModel which wasn't provided, and probably isn't necessary to provide), and I don't know what Color.baseBackgroundSecondary is, so if these are required to reproduce your issue you'll have to provide them. I can show the DatePicker when I click to the right of the displayed date (because you're using the .colorMultiply(.clear) hack). If I change the line .background(Color.clear) to use a blue colour instead, I can see that the DatePicker is clickable in that blue rectangle: Why would you want to set the opacity to 0.011? That's just over 1% opacity and is practically transparent. This is what it looks like with that blue colour at 0.011: Can you explain a little more clearly what you want to achieve?

@ptgr In App Store Connect, go to your app's page. In the top right where you had previously pressed buttons like "Save" and "Add for Review", there should now be a blue button with something like "Release this Version" (I'm not entirely sure of the actual text). Press that, and the new version will be released.

These are the Developer Forums, where developers of apps for Apple's platforms ask each other for hints and tips on coding. We aren't employed by Apple. You're in the wrong place. Your question is more of a product support one, which should be asked over at the Apple Support Forums. I just did a quick search and this came up: https://support.apple.com/en-us/108918

Don't use comments if you want a reply. No one gets notified that a comment has been left. You only get notifications when a reply is left. Anyway, this has been answered by an Apple employee, and it's basically exactly what I told you earlier: https://developer.apple.com/forums/thread/727753?answerId=873144022#873144022

You shouldn't get errors for such a simple bit of code. The way you've phrased it suggests you are getting errors? The worst way to handle such errors would be to close your app. You should handle the failures gracefully. You should find out what the error actually is, and see why it's happening. You'd probably be able to stop them occurring in the first place. If it's an error you cannot work around then you should probably tell the user that you couldn't save the data, and leave it on the screen so they can try again. Make it as seamless as possible for the user. No one likes a technical error message in an app.

Are you trying this on a physical device or the Simulator? You have to test IAPs on a physical device; they don't work in the Simulator.

[quote='872985022, nightow1, /thread/813147?answerId=872985022#872985022, /profile/nightow1'] You have a choice, right? [/quote] No, you literally don't. Every iPhone app is expected to work on an iPad. It doesn't have to be written as an iPad app, i.e. it doesn't have to take up the full screen and have all the same navigation stacks, tabs and layout as an iPad app does, but the app must function on an iPad. App Store Connect shows it is an iPhone app, yes, but that just means it is listed in the App Store for iPhones. If someone downloads it on their iPhone it will also become available on their iPad, too, so it must work on their iPad as well. As I said, run it on an iPad and see if the app works properly. If it doesn't, then you have to fix it. The App Review Team are literally telling you that they are rejecting it because it doesn't function properly on an iPad. Your app must work on an iPad, so make it work on an iPad. Just run it on an iPad and see what needs fixing. It might be a really simple thing to fix.

Note that users expect apps they download to function on all the devices where they are available. Since your app may be downloaded onto iPad devices, it is important that it also function as expected for iPad users As they have stated, you can download an iPhone app and run it on an iPad. What does your app look like when run on an iPad Simulator? If there are any issues, you should fix them. It seems that you've just assumed everything is fine because you've turned off some switches, but haven't actually tested that it works properly.