You can run an iPhone app on an iPad. Are you able to deploy the app to an iPad Simulator via Xcode? If so, what does the app look like on the iPad? Are there any glaring issues? This is what the App Review Team are likely seeing. Give it a go and see if you actually to fix anything.

Do you have any profiles installed that would prevent installing a newer version? Have a look in the Settings app > General > Device Management. If not, use Disk Utility to repair your startup disc. Then try Software Update again. If that still doesn't help, try reinstalling macOS from the Options menu: Backup your Mac (just in case). Shut it down. Boot it up by holding down the power button. Don't release the button until you see the boot menu. Click on the Options item, and choose to reinstall macOS. This will reinstall macOS over the top of the existing install. It won't affect your user data, but I suggest you backup your Mac just in case. Once reinstalled, try Software Update again.

Two usernames, both ending with "_0", asking about ASO, posting multiple threads, and answering their own questions with a question. Spam.

There are 272 lines of code in the file you linked to. Is all that code necessary just to keep the sidebar open?! Seems like something Apple should implement in SwiftUI. Would you consider raising a Feedback request? (If they implement it, it would save everyone having to write so much code, including you 😉)

If you have a contract with the developer, you should check what it says. Do you have the source code, or access to it? If the contract doesn't allow you access to the source code then you will have to develop the app from scratch, and you won't be able to use the same name. If the contract allows you access to the source code, you need to get that source code. If you get the source code, you need to contact Apple Developer Support (that "Support" link at the top of the page) showing them the contract, and they should be able to transfer the app to you. There are lots of things to check and Developer Support will ask you to prove a few things, so be prepared. Ask what they require upfront.

Two things: These are the Developer Forums, where developers of third-party apps for Apple's platforms ask each other for hints and tips on coding. You're talking to random third-party developers from around the world, not Apple's developers; If you have a suggestion, you should raise it at: https://www.apple.com/feedback/ but please note that your post doesn't really explain the issue, so please clearly state what's wrong with the three dots button. There is no option in that menu to directly delete a tab group; it's more than one tap away - so whatever you're doing it's not as a direct result of that menu.

@Freocast Isn't there an "Auto-renew" toggle on this page (you must be signed in): https://developer.apple.com/account#MembershipDetailsCard

I wonder if this is because on iPadOS users can now resize apps, so forcing them to a certain orientation is redundant now? If you want to lock in an orientation, you could maybe set the scene's minimumSize so users can't resize it smaller than a specific size that just happens to be a landscape window, such as 800 x 600? i.e.: class SceneDelegate: UIResponder, UIWindowSceneDelegate { func scene(_ scene: UIScene, willConnectTo session: UISceneSession, options connectionOptions: UIScene.ConnectionOptions) { guard let windowScene: UIWindowScene = scene as? UIWindowScene else { return } windowScene.sizeRestrictions?.minimumSize = CGSizeMake(800, 600) ... So, implement that, and tick all the orientation check boxes in the deployment info. Note, you should probably try and make sure your chosen window size makes your app look good on a smaller iPad (iPad mini) in portrait orientation. If necessary, compress or hide parts of the UI when the window is too small.

No idea what you mean by "it freezes the Camera feed", and you don't exactly say how those cameraStatus and isAuthorized variables are used. I assume the initial value of isAuthorized is false ? You don't show that in the code. Do you need two variables? It seems: whenever isAuthorized is true, cameraStatus is .authorised; and vice versa, when isAuthorized is false, cameraStatus is notAuthorised. Except in the last case: @unknown default: where isAuthorized is true but cameraStatus is notAuthorised. Could this be your issue? Could you use just one variable to cut down on the complexity?

I agree with @Etresoft, but I would also point out that these forums aren't the place for your post. These are the Developer Forums, where developers of apps for Apple's platforms ask each other for hints and tips on coding. You are talking to other third-party developers here. While some Apple employees do visit these forums, they are likely to agree with @Etresoft in this instance, and, if they don't agree, they would probably point out that your issue is more suited to the Apple Support Forums. (And yes, I'm aware of your other post regarding being unable to post in the other forums, but that does not negate the fact that this is not the place for your post.)

If you have a suggestion, you should raise it at: https://feedbackassistant.apple.com/ When doing so, I recommend you list the specific APIs you want, and the justification for them. A suggestion that Apple just implement some of the missing APIs won't get very far.

No evidence provided here, but what do you think a bunch of random third-party developers can do to help you? WE ARE NOT APPLE. WE CANNOT DO ANYTHING TO YOUR DEVICE. Take your suspicions to your local law enforcement and have them deal with it. These forums are not the right place for this.

Why not just have a way to allow the user to buy the IAP without having to play for 5 minutes? If there's some sort of menu screen just add a way of buying the IAP from there. Some users might play your game for two minutes ten times and never see the screen that appears after five minutes, but they might like it enough to buy it. One of my apps lets you add three "things" in the free version, and unlimited "things" once you've bought the IAP, but you don't have to add exactly three "things" before the buy button appears; it's always there.

Whilst it's a consumer feature and not something us third-party devs should be concerned with, I'd say it should be raised as a bug in the usual way so it gets looked at and fixed. Posting it in the Apple Support Communities won't do anything. No one can there can recommend a fix other than not enabling large text... @yrcrt You can raise a bug at: https://feedbackassistant.apple.com/ then post the FB number here.

@GGdev26 My suggestion? If so, please accept it as the answer so that others know there's a solution to this problem. Thanks!