@kevdoescode you ask if the post is correct. That probably means it does not work properly. If so, do you get and error message ? Is the result different from what you expected ? To use the forum properly, you have to provide this information, not just ask someone to correct your code. I advise also to read the very good post on how to properly use the forum: https://developer.apple.com/forums/thread/706527 A simple code sample here: https://forums.swift.org/t/sending-an-http-post-request-to-an-api-using-swift/62457

It was effectively a bad idea to submit the app from a differentl account. Now, the app is viewed as belonging to it. Are you sure the spam is related to this former submission ? If so, did you explain in the notes to reviewer, with a written and signed statement from the junior engineer confirming what you say here ? If that's not enough, may be you should also have the letter certified by a legal officer.

Welcome to the forum. Do you mean you received a notification of approval ? From which country are you applying ? There could also be delays because of holidays. If you've not received anything by monday, you should contact the support.

Welcome to the forum. You place both buttons as topBarLeading. Is it on purpose ? No issue if this second button is topBarTrailing The same occurs if MyButtonStyle is first: it gets clipped. Idem if MyButtonStyle is the only button: And if image is removed, Text is truncated with ellipsis… But setting a frame width for the text (or even better, the HStack) solves the problem: struct MyButtonStyle: ButtonStyle { func makeBody(configuration: Configuration) -> some View { HStack { Image(systemName: "chevron.backward") Text("Back") .frame(width: 80) // <<-- ADDED } } } So looks like that without setting the frame, frame is considered zero (or very small), probably to optimise space ? You could file a bug report.

Forum is not for app advertising. Please refrain.

I had issues with BarButtonItems, as described here. https://developer.apple.com/forums/thread/787177 Not exactly the same as yours but background issues as well.

It’s really important for me that the review does not get delayed further. Unfortunately, the forum is not the place to get it accelerated. By experience, the time "in review" can vary largely, from 1 hour to more than a day. I noticed that if there was a previous issue with submission, it can take a bit longer.

Forum is for technical discussion for those who want to engage in such discussions. Good bye and good continuation so.

From what I read, looks like it starts by collapsing at the lowest level and to the next if you repeat. But I'm not using Studio, so that's just a guess. In anywise, you could file a bug report asking for evolution.

Here is the structure of a project with a Watch companion app (it was created several years ago, with Xcode 9 or 10 probably and uses WatchKit and not SwiftUI): I have highlighted the 3 info.plist the first is the usual for iOS app, in iOS section (bundle display name is 'MyApp') Second in myApp Watch (bundle display name is 'MyApp'). The content is: third info.plist in myApp Watch Extension (bundle display name is 'MyApp Watch extension'). Its content is: Note also infoPlist, which contains some localizations, with keys as CFBundleName, NSCameraUsageDescription I don't remember how they were created (I think it was automatic when creating watch companion, but you can probably recreate manually). Hope that helps.

Effectively, exploring what could be done with UIRequiredDeviceCapabilities in Info.plist appears the best option. https://stackoverflow.com/questions/10191657/restrict-to-certain-ios-target-devices-for-app-store-submission May be you can find a listed capability that matches approximately with support of Apple Intelligence. But unfortunately, gaming seems to be the only one to discriminate for A17 chip. https://developer.apple.com/support/required-device-capabilities/

Welcome to the forum. Until you receive a request from reviewer, there is nothing to do. What type of app is it ? Does it include in app purchase ? Is it a paying app ? You should also note that this forum is not an official channel to Apple, even though some Apple's engineer contribute to it. So you'd better contact support.

My understanding is it is because folding is multi level. Unfold is easy: everything that was folded, whatever level, will unfold. But folding all: what you you keep ? Just very top level, at class level, where you see nothing more ? At the first level func ? So you should have to specify the level to make it any use. So, imagine what should be the result of a fold all and you may find it is impracticable.

Finally, to give you in depth explanation about the use of @State in DataView: https://forums.swift.org/t/im-so-confused-why-state-var-inside-a-view-do-not-change-when-you-call-a-method-on-this-view-from-some-outer-view/31944/7 And you can test with a Binding: struct DataView2: View { @Binding var datum: Data2 var body: some View { Text("DataView \(datum.str)") } } calling it with DataView2(datum: $data[index]) Good continuation.

Finally, to give you in depth explanation about the use of @State in DataView: https://forums.swift.org/t/im-so-confused-why-state-var-inside-a-view-do-not-change-when-you-call-a-method-on-this-view-from-some-outer-view/31944/7 And you can test with a Binding: struct DataView2: View { @Binding var datum: Data2 var body: some View { Text("DataView \(datum.str)") } } calling it with DataView2(datum: $data[index]) Good continuation.