Welcome to the forum. Your question is not about app development. So you'd better ask on Apple Support Community: https://discussions.apple.com/welcome Or file a bug report here: https://feedbackassistant.apple.com and provide as miuch information as possible on your iPhone configuration.

Appstore provides a solution for your case: If you are unable to provide a demo account due to legal or security obligations, you may include a built-in demo mode in lieu of a demo account with prior approval by Apple. Ensure the demo mode exhibits your app’s full features and functionality. You should probably contact developers' support to get some help.

It's great to provide screenshots, but please, reduce the size of each image. Read advice 10 here: https://developer.apple.com/forums/thread/706527 There are a lot of amounts, but are they prices ? Are any of them references to the price of the app or the service it provides ? If it is, as @endecotp wrote, remove them, replacing by $***. ** If not, explain very clearly to reviewer that the $ amounts are not related in anyway to the price of the service, they are just illustration of what a user finances may look like. Another thing. Are they real simulator screenshots ? We see the Dynamic Island partly below the notch, in a way I never saw before.

precise name of the color, material, or blend mode value employed for the border. Do you mean the border of a usual window ?

@Quinn, I'm missing something here. init?(dictionary: [String: Any]) { fatalError() } So why does this call not trigger fatalError ? guard let response = MyResponse(dictionary: responseDict)

Did you consider using NSNotification instead ? addObserver in the window, which will close it Declare at top level (outside any class) public static let kForceClose = Notification.Name("forceClose") In viewDidLoad of the NSWindowController: NotificationCenter.default.addObserver(self, selector: #selector(closeIt(_:)), name: .kClose, object: nil) @objc func forceClose(_ sender: Notification) { self.window?.close() } Send notification in Button IBAction NotificationCenter.default.post(name: .kForceClose, object: self)

This should give a solution: https://stackoverflow.com/questions/42762856/nswindow-with-round-corners-in-swift let effect = NSVisualEffectView(frame: NSRect(x: 0, y: 0, width: 0, height: 0)) effect.blendingMode = .behindWindow effect.state = .active effect.material = .dark effect.wantsLayer = true effect.layer?.cornerRadius = 15.0 window.contentView = effect window.titlebarAppearsTransparent = true window.titleVisibility = .hidden window.isOpaque = false window.backgroundColor = .clear Does it ?

I could not test on iOS 17 (my sample project crashes Xcode 15.3). Do you confirm it works there ? I see the same on iOS 18: DetailView initialized DetailView appeared DetailView task executed -->> button tapped DetailView disappeared DetailView appeared DetailView disappeared DetailView task executed This discussion may be interesting to read, even it did not let me understand what happens: https://fatbobman.com/en/posts/mastering_swiftui_task_modifier/

Crypto apps are very closely monitored on Appstore. So, you have to check every third party for evidence of evidence of "permissions, registrations, and/or licenses to distribute an app with exchange services." That may be pretty hard to get.

Welcome to the forum. There are multiple reasons for spam rejection. your app is too similar to another app or shares a lot of similar code with another app your app belongs to a category which is over crowded and thus rejected unless it has very specific and valuable features Could you show the complete rejection message and tell which category your app is ?

How long is it since you installed Xcode ? Xcode may still be doing some tasks in the background to completely set up the environment. That mays last a couple of days.

Reproduced the problem. All buttons are put behind the first in the HStack. Removing buttonStyle on the last button (whatever style) .buttonStyle(.borderedProminent) solves the problem. Or removing the menu also solves. Removing the Stack does NOT solve. So, HStack is not the problem. Bizarre. This fails as well. No Menu, one button without style ToolbarItem(placement: .bottomBar) { HStack { Button {} label: { Label("Foo", systemImage: "square") } .buttonStyle(.bordered) Button {} label: { Label("Bar", systemImage: "circle") } // .buttonStyle(.borderless) // Menu { // Button {} label: { Label("One", systemImage: "figure.arms.open") } // Button {} label: { Label("Two", systemImage: "figure.2.arms.open") } // } label: { Label("Baz", systemImage: "star") } Button {} label: { Label("Quux", systemImage: "triangle") } .buttonStyle(.borderedProminent) // Causes buttons to stack on one another } Restoring the style for the circle makes it work. So issue seems to be when one item has no style (which is the case of Menu) But if we remove style of a second item, it works. => Problem when 2 items in the toolbar have style and some other has not…

Guideline is very clear: 5.2.3 Audio/Video Downloading: Apps should not facilitate illegal file sharing or include the ability to save, convert, or download media from third-party sources (e.g. Apple Music, YouTube, SoundCloud, Vimeo, etc.) without explicit authorization from those sources. Streaming of audio/video content may also violate Terms of Use, so be sure to check before your app accesses those services. Authorization must be provided upon request. For you to solve, you have to get the explicit authorisation from the platforms. Some apps also offer similar features. So, how were these apps published? Do you know if they got such authorisation ? In any case, the fact that other app with similar feature has passed the review, in compliance with guidelines or not, is never an argument. And those apps, if not in compliance, may be rejected at a future review.

You probably did it, but: Check that English appears in Bundle's Settings check that English is in InfoPlist

This appears to be an old problem. You may find some solution here: https://github.com/expo/eas-cli/issues/2111   PS: the maximum length on these forum posts is crazy small! You can attach a long text as file