What @darkpaw said is important. Do not change TextField behaviour. But you can do something if you really need. Subclass TextField (call it ControlledTextField for instance). add an activation button on the side TextField is editable only when activated So, that will be some kind of double tap, or trigger and fire. Hope that helps.

So you'll have to first change the name of the old app. Once changed and visible in Appstore (that's the only delay I know), check for the old name. You should not find it and thus be able to create the new app with this name. You should explain this very clearly to reviewer in the notes to reviewer. Another point,: I don't know if there is a risk some one reuse the old nam before you…So go fast. Anyway, you'd better double check with Developers support. If you get a precise answer, please report here.

Welcome to the forum. But your question is not precise at all, no one can answer. You would better contact Apple Support and explain.

That is a frustrating issue with SwiftUI, how poor and misleading the error reporting may be. That is one of the reason I'm not very fond of SwiftUI… My understanding (but I may be wrong) is that when the error occurs at top level of the view, it is correctly matched. But when inside s structure (List, ForEach or whatever), compiler just fails on this part ; and at higher level (body), get noticed that a subview was not created. And it guesses it is because it is too complex. When I get such error, I work by dichotomy: comment out a significant part (about half) of the body code if still fails, then error is in the other part ; so I comment out half of this other part if is works, then I uncomment half of the commented and test again… That's the best I've found.

Welcome to the forum. What are you speaking about ? What is the issue ? What is going on for 30 hours ? I hope you realise your post is just incomprehensible.

Bonjour et bienvenue sur le forum. No, don't submit again. Your app will remain in rejected status during the investigation. Don't worry, it will clear as soon as the inspection is completed (or you'll get a message). It could take several days for this investigation.

Navigating in the storyboard for Watch is always tricky. But, YES, you can. Open the library to find gestures You drag a tapGesture on the object you want to double tap. It will appear in the hierarchy. You set its attributes with Attribute Inspector You connect the gesture to an IBAction in its controller to connect to the destination : @IBAction func tapOnImage(_ sender: Any) { presentController(withName: "Detail", context: self) } Hope that helps. If so, don't forget to close the thread by marking the answer as correct.

Welcome to the forum. M3 Chip 8 Core GPU That's quite enough. In fact M2 would also be OK, if you want to save $100 for other options. Or look for second hand machine (but may be hard to find with enough storage and memory) 256 GB storage is not enough. Not enough. That's the most critical. System will use close to 100 (even more in some cases) ; Xcode uses a lot of storage. So 512 is a strict minimum, and 1TB is a safer choice for +$460 (personally I never go now below 2 TB). 16 GB Unified Memory Take care, that cannot be expanded. If you intend to keep your Mac for several years (more than 5 or 7 is a safe bet), you should consider 24 GB (extra $230) Mind also of screen size if you do not plan to buy an external monitor. Xcode requires a lot of screen space to develop efficiently (and comfortably). So 15" is better

It seems to be normal. I've searched for "Cameroon taxes on import of digital goods": Cameroon exports of goods and services as percentage of GDP is 19.41% and imports of goods and services as percentage of GDP is 20.50%. 20.5% over 99 = 119.29 That's not extra money that goes into Apple's pocket but the state's one.

Welcome to the forum.   Any idea why they do so? Because they apply the guidelines. The fact that other app which you consider similar, has been accepted is never an argument for the review team. You don't know if they have done anything special to comply. Or may be, they just passed by luck but will be rejected in a future update. Anyway, you have to focus on your own app and modify it to comply or explain why you think you comply. PS in fact our app ui also closely resembles all 4 of them Take care not to be rejected as spam as well.

Thanks for the explanation. But so, what is the best solution for a Button ? Having to overlay in a Rectangle is really a convoluted workaround.

You only show the button, not the swipe code. That does not give any information to understand what happens. Please provide complete code so that we can reproduce.

Welcome to the forum. When you post code, please use the code formatter tool: import SwiftUI struct ContentView: View { var body: some View { VStack(spacing: 20) { Text("SwiftUI Button") .font(.largeTitle) Text("Enabled & Disabled") .font(.title) .foregroundColor(.gray) /* Disabled */ Button("Enabled") {} .buttonStyle(.borderedProminent) .tint(.blue) .controlSize(.large) Button("Disabled") {} .buttonStyle(.borderedProminent) .tint(.blue) .controlSize(.large) .disabled(true) } } } struct ContentView_Previews: PreviewProvider { static var previews: some View { ContentView() } } I tested on iOS simulator, it works

Welcome to the forum. Your question is really too vague. First question: do you want to use AppKit (Cocoa) or SwiftUI ? For SwiftUI, there are many tutorials (including from Apple). For Cocoa, you have to search for: swift developing macapp "cocoa" Here is a very simple one : https://www.youtube.com/watch?v=8zFzldVgG4k Or search for sample code : swift developing macapp "cocoa" sample code Many here: https://github.com/kicsipixel/Cocoa-Samples To search the libraries, the best is to use Xcode documentation directly,

Welcome to the forum. Your code compiles and runs fine (just had to change RoundedCorners by RoundedRectangle and initialise the 3 vars). I also removed the extra closing curly brackets at the end. So where does the error occur ? Probably in a part of code you did not show.