On what View did you apply the constraints ? Could you: a screenshot explaining what you get and what you'd expect a screenshot of the Size Inspector in which constraints are defined

@develop1226 I once experienced a similar problem when I defined shouldChangeCharactersIn(), which discarded return keystroke. Could it be your problem ? If so, you should add this early in shouldChangeCharactersIn() if let char = string.cString(using: String.Encoding.utf8) { let isReturn = strcmp(char, "\\r") if (isReturn == -82) { backSpace = true } }

What is your question to the developers community, at the end of (way too long, could not read it to the end) message ? If your question is for Apple, note that the forum is not an official channel to them.

Welcome to the forum. It is UIKit app (not SwiftUI ?) Is it on device or simulator ? You can add this func in your viewController: func textFieldShouldReturn(_ textField: UITextField) -> Bool { self.view.endEditing(true) return false } Tell if it works, then don't forget to close the thread by marking the correct answer. Otherwise, could you show the complete attributes inspector for the TextField ? As well as its connections Inspector panel.

Welcome to the forum. Which OS version do you use ? Did you test with iPadOS 18.4.1 ?

Welcome to the forum.   Is there any way to directly contact/speak with the reviewer who evaluates our app for approval? AFAIK, it is not possible to discuss directly with a reviewer.   How can we have a conversation beyond the copy pasted template responses being provided? Did you appeal the rejection ?   Any other suggestions for our next steps? Have you an idea of what, in your app other its metadata may lead the reviewer to think you are collecting funds ? When you update the submission, explain your point of view, clearly, synthetically and politely in the notes to reviewer ?

You'll just have to take care with storage. It's OK if you manage it properly.

What exactly do you want to mimic. Your question is not precise enough to get proper answer. In SwiftUI, that would be a List, with a VStack for each item (Surname, First Name, Company), and 2 Text in each VStack, with the proper font attributes…

In Apple Library, you have Swift programming Language. For most up to date reference (Swift 6.1): https://docs.swift.org/swift-book/documentation/the-swift-programming-language/aboutthelanguagereference/

I tested your code (Xcode 16.3) and it works without issue. Which Xcode version do you use ? As you posted a screenshot only (you should paste the real code, as is), it is not possible to say if you have a non printing character somewhere. Show hidden characters to check (Menu: Editor -> Invisibles) Please show real and complete code if you need more help. Error may be elsewhere in your file as well.

Yes, there are many workarounds, as soon as it is understood that the cause is that clipping just clips the image, but not the view, which then overlays the button and intercept taps. The problem is not the VStack by itself. But VStack makes Button on Image sit close together, hence the problem. If VStack spacing is increased, no problem. You can also disable user interaction by adding this modifier to the image: .allowsHitTesting(false) Don't forget to close the thread on the correct answer.

I tested (in simulator) and did not notice , any delay. I compared with the same button outside the scroll view, no difference.   most users won't see it I think. So, what's the point ? What animation do you mean ? What do you see ? What did you expect ?

OK, I see you are a seasoned developer… So, best is probably to make code robust by testing the validity of row. Could be a side effect of some values not yet updated when you use them, and it may be hard to find.

Where is this checkbox ?

Bienvenue sur le forum. Est ce que votre app utilise 'un service de connexion tiers,' tel que Facebook Login, Google Sign-In, Sign in with Twitter, Sign In with LinkedIn, Login with Amazon, ou WeChat Login Si non, il faut le signaler au reviewer, que vous n'êtes pas dans ce cas. Si oui, vous pouvez soit utiliser la connexion avec Apple login, à la place de celle utilisée, soit montrer que vous respectez les exigences 2 et 3. Attention, la traduction que vous avez des guidelines est imprecise. Les exigences sont: le service de connexion limite la collecte de données au nom et à l'adresse électronique de l'utilisateur ; le service de connexion permet aux utilisateurs de ne pas divulguer leur adresse électronique lors de la création de leur compte ; et le service de connexion ne collecte pas les interactions avec votre application à des fins publicitaires sans le consentement de l'utilisateur. Et enfin, mettez à jour les copies d'écran si besoin.