As explained here, https://stackoverflow.com/questions/58081108/unexpected-character-in-prerequisites you may have a colon (:) in a name of a file or directory. Or leading spaces. In any case, a name is invalid for Xcode. You should find and remove. Hope that helps.

Old post for sure. Could you post a complete code, so that we can try to reproduce and find solution ?

So my explanation was wrong. It is now again last 24 hours.

Welcome to the forum. Which type of app is it ? I understand it is an update, not a first release ? You could contact support and ask.

Do I need to go through a testing process Yes, of course. And remind your app will not pass review if reviewer finds a bug. But precise answer may depend on what you mean. You need to test extensively: that means testing all the functions of your app in various conditions: for instance, if user has to enter a value, test with different values including "incorrect" values. Test also the performance if that is important for your app. If you write a user manual, that's a good way to be sure you test in a user perspective, not only a developer one. But you are not required to go through a specific test method or process. It is up to you to select the best, possibly some tool to organise test. You may have a look here: https://useyourloaf.com/blog/xcode-test-plans/ https://www.avanderlee.com/swift-testing/introducing-expressive-apis/

Hey, I did not notice, but that's the case. It is clearly intentional, probably to reflect that data are updated once a day, so what you get is not the last 24 hours (from 10 am yesterday to 10 am today when you look at it). So it is more appropriate to say that' yesterday, from midnight to midnight. However, I noticed the counter may tell a positive number of units but none shown in graphics. I just filed a bug report – FB15722868

Yes you have to provide for one iPhone (6.7 or 6.9") and one iPad (12.9"). No, you have not to provide for the 20 cases ! In your case, a short video could be a good option. At the end, it is not a user manual, it is more marketing material. What is expected is that user understands how it will play the game. And also find it attractive to play. Which means that it is probably not the best thing to "shows all modes and the next screen which compactly shows all the games, example of dark mode"

Usually (at least that's how I use it), selection is a Set: @State private var selectedID: Set<UUID> = [] Of course, you have to extract from set to pass to navigation, but that's easy, as set has usually a single item. You could create a computed var to do so. . Then, clearing the selection is simply done by resetting to empty set.

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.