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.

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.