It's only free if you bring your own API keys, so you're still paying someone somewhere for something. I'm quite happy with the autocomplete built into Xcode. It's pretty good at what it does. I have real reservations about using LLMs (it's not AI) to write code for me, because I need to read what it's provided and confirm that's what I need my app to do. It's much easier to understand code when you write it yourself because you know what you want it to do. I'm not overly convinced by the demos on the site. I have no doubt it might be useful at some point but right now I just cannot trust an LLM to write the right code for me. (And I'm not going to be used as the source material to improve someone else's software by having to correct it when it gets something wrong.)

The solution, as reiterated by @Yoorque, is to use Color.green and not just .green in foregroundStlye().

I figured it out. Using :has-text(/myText/i) seems to work. But... I still think Apple need to do far better in their documentation. One example is not good enough, especially when Apple devs are writing frameworks that cover many scenarios - why not mention some of those in the docs?

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.