Show us your code. It might be something you're doing.

That sounds like a massive problem. Have you raised a Feedback report? If not, please do so at https://feedbackassistant.apple.com/ then post the FB number here. The exact model numbers might be important, so be sure to add specific details.

Have you raised a Feedback report? If not, please do so at https://feedbackassistant.apple.com/ then post the FB number here. Then, if the phone isn't working, yes, you should downgrade. If the downgrade is successful - and you can use the iPhone as normal - you could try to upgrade again, but if it does the same I'd say hold off until a later beta comes out. But, it's important that you raise the bug.

There is no need to make a new post just to change the title of an existing post. You have an hour to edit a post. If you're outside of that one-hour window, and the edits you want to make are really that important, just reply to your original post. Duplicate posts clutter the forums.

Well, you aren't going to be creating a driving licence or passport in your app, so there's no need to delete that data. You're just providing users with a way to view already existing data via an app. What you need to provide is a way to delete data that your app creates. If users can create an account on a government website (outside of your app) and login to your app with those same credentials, or they can create an account in the app and login to the government website with those same credentials, then there should be no requirement to delete the login details or user account. If, however, the app creates a brand new account used solely for the app, then this is what must be available for deletion. What you also might have to offer is the deletion of any data pertaining to the use of the app, e.g. logs or app customisations saved as a file on government servers. An example might be a preferences file that's created in the app and uploaded to the server.

I think you're in the wrong place for this. These are the Developer Forums, where developers of apps for Apple's platforms ask each other for hints and tips on coding, not on 'AI'.

Have you tried holding down the power button and waiting until it loads the startup options? There are various options in there, restore from Time Machine, Disk Utility (erase etc.), and Reinstall macOS.

It's basically: if a then b else c which is three parts.

Probably, it's beta software. Have you raised a Feedback report? If not, please do so at https://feedbackassistant.apple.com/ then post the FB number here. When you raise the bug, be sure to explain what ringtone you have selected, and any other relevant info such as whether you've assigned a particular ringtone to the person calling you, or whether it's just a general ringtone for all calls. Are you in a focus mode like Mindfulness or Personal, perhaps?

Yeah, if it's not a solid colour it would need the scaling, but hopefully it makes sense to you now? The ordering of the modifiers is important.

You should probably raise this as a bug in the usual way. It won't really get progressed if it's 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 can link to them.

You should probably raise this as a bug in the usual way. It won't really get progressed if it's 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 can link to them.

It's your app, how are we supposed to know? We're just developers like you. The App Review Team will have taken the credentials you gave them, and tried to login. When the login failed, they stopped reviewing it and informed you of the issue. That'll be the extent of their information on how to reproduce the issue. Do you have any logging on your server so you know why the login failed? Have you tried to debug it, and follow through the code to see what happens when you attempt to login with those credentials? Whilst stepping through the code you might notice something that could be causing the issue. Why is the password field blank? Does it get wiped the moment the user presses the Login button? Did the App Review Team attempt to login without a password? Did you give them a password? So many questions...

When you do this: Image(.background) .resizable() .scaledToFill() .ignoresSafeArea() You're telling SwiftUI that the image can be resized, and you want to scale it to fill its parent, so SwiftUI scales the image. However, at this point, SwiftUI doesn't know that the image can ignore the safe areas, so the parent view at that point isn't ignoring safe areas. That's why you get the white bit at the bottom. I took your image and added a red border and yellow squares in the corners so I could see where the image was stretched/resized and positioned. With the code above, you get this: So you can see it was resized to fit inside the parent view, and doesn't ignore the safe areas. For your needs, just remove the .scaledToFill() modifier, you don't need it: Image(.background) .resizable() .ignoresSafeArea() This yields: If your ultimate need is to get that last image with just the white bit at the bottom, the fix again is to remove the scaling: Image(.background) .resizable() .ignoresSafeArea(edges: .top)

I can't help you specifically with this, sorry. I know it's a pain to migrate from ObjC to Swift/SwiftUI - I've been there - but there are two options: Migrate from ObjC one file at a time; Rewrite the app from scratch. I completely rewrote one of my ObjC apps within a couple of weeks in my spare time, and it has far less code in it. Things like filter, map and compactMap reduced my code so much. You could do this as a separate project while trying to update the original app. So, make the necessary updates to the original and also start writing the new version from scratch. You'll probably enjoy it. And if you need any help at all, just ask.