Yeah, or some bot accounts asking about ASO. Perhaps complaints about review length or developer account issues should be syphoned off into a separate section? Maybe Apple could add a section above in the new post screen that says if they have an issue with their account to "click here" and go to some other place where actual Apple staff will have to respond? As a developer I don't really care about review length or someone else being unable to find a button in their Developer Account settings. I've helped people and never gotten a response from them, so I tend not to bother helping now. I've used these forums a lot in the past, and I enjoy them, but they have definitely recently gone downhill. Right now they're "just good enough". Apple should step in and make them better.

It looks like the Review team are logging in but aren't able to do much. What happens when you login with those credentials? You're in your prod environment, right? And if you want to go through using the app what do you have to do? You have to perform an actual transaction... in a prod environment... where actual money is used. The Review team are not going to do that. Do you have a test environment? If so, you should change the app so that when this particular test account logs in, it connects to the test environment instead of your prod environment so that the review team can go through the app properly. If you don't have a test environment, you should probably spin one up for the duration that the Review team need to use it.

Accept your own answer. That'll show others there's a solution to this, so they'll be more likely to view this thread and see it 😉

Don't you have to have created a new app in App Store Connect for Xcode to upload it? Otherwise, Xcode doesn't know where the app should go. Not sure how you achieve this, but before making any more attempts at uploading to App Store Connect, install your old app on the Simulator, then run the new app and install it to the Simulator. If you get two different apps, then you know that you haven't done it properly. Delete the new app from the Simulator, make some changes in Xcode and install to the Simulator again. Repeat until it actually just installs over the top of the original app.

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