Trial and error. I managed to get through this by random restarts of the device, deleting and reinstalling the app to the device etc. Still get blank pages in the purchase screen though, but I'm past that.

Word salad. Either this is spam as you haven't actually asked any sort of question, or you need to re-word your question so we might be able to help you. Also, note that these forums are full of primarily random developers from around the world who write apps for APple's platforms - not actual Apple employees, so you might want to direct your question (?) elsewhere.

These are the Developer Forums, where developers of apps for Apple's platforms ask each other for hints and tips on coding. Your question is more of a product support one, so I'd suggest you ask it over at the Apple Support Forums. Thanks.

I use this for making something happen only once. Put it into an Extensions.swift file or something like that: extension View { func onFirstAppear(perform: @escaping () -> Void) -> some View { modifier(OnFirstAppear(perform: perform)) } } private struct OnFirstAppear: ViewModifier { let perform: () -> Void @State private var firstTime = true func body(content: Content) -> some View { content.onAppear { if firstTime { firstTime = false perform() } } } } And you use it like you would use .onAppear, i.e.: .onFirstAppear { // Do something once }

The warnings you see are caused by Apple's code, not yours. It relates to displaying a keyboard, so you can ignore those. Just tried this here and it works fine. iPhone 16 Pro Max 18.2 Simulator. What happens if you click in the text field in your app in the Simulator, and press Cmd+K to toggle the software keyboard? Does it let you type into the field? Can you remove/comment out the .overlay that contains the clear button with image xmark.circle.fill. Maybe the tap onto the field is being intercepted by the Spacer() and that image? I don't know, I'm just trying to see what might cause your issue.

Speak to your team's Account Holder, and try not to put their name on these public forums... You also haven't mentioned which page causes the error.

These are the Developer Forums, where developers of apps for Apple's platforms ask each other for hints and tips on coding. Your question is more of a product support one, so I'd suggest you ask it over at the Apple Support Forums. Thanks.

If you have a suggestion then you should raise it at: https://feedbackassistant.apple.com/ But I would say that your assumption that everyone uses the same 20-30 emojis is absolutely incorrect. How would Apple decide which emojis to put in there? Would you be happy with the rainbow flag being in there and you not able to remove it? (Some people don't like LGBTQ+ people, and I expect they'd rail against Apple for forcing it on them...) You simply cannot assume such a thing. How it works right now is personal to each user; why not just leave it as it is?

Welcome to the Developer Forums, but I must say that your issue is not something you should post in these forums. These are the Developer Forums, where developers of apps for Apple's platforms ask each other for hints and tips on coding. Since you've already contacted Chase and they say it's a known issue that they're working to fix, just wait for Chase to fix it! Posting in here - to random developers around the world - won't get you any closer to having your app working again. We don't work for Chase, and we don't work for Apple. I'm sorry you've got an issue with an app on your iPhone. but Apple cannot help you, and neither can us random developers. Chase know what the issue is, and they're going to fix it. Just be patient (and please don't use these forums for such posts in future). Thanks.

No. I really wish people wouldn't use these forums to ask this exact question every few weeks. It's so tiring. Marking your post as spam.

You're in the wrong place. These are the Developer Forums, where developers of apps for Apple's platforms ask each other for hints and tips on coding. We are not employees of Apple. Your question is more of a product support one, so I'd suggest you ask it over at the Apple Support Forums. Thanks.

Ask the App Review team.

This looks like an amateur AI wrote it. Marking it as spam.

What's your problem? Why do I have to go to a comment on Stack Overflow to see what the issue is? Post the specific issue here and we may be able to help you. If you're just firing off duplicates in the hope someone will see it and help you... nah.

How about not using .ignoresSafeArea and seeing what happens? You're telling SwiftUI to ignore the safe areas, i.e. the bit where the Dynamic Island is, and manually setting a distance away from that part. Don't use magic numbers; they will change and your app will look rubbish. Adhere to the safe areas and you should be fine.