Target 'PCS_EmpApp' (project 'PCS_EmpApp') has copy command from '/Users/mayankjain/Documents/05-NOV-2025-SWETA_IOS/PCS_EmpApp/PCS_EmpApp/xcode-out/Platforms/iOS/Info.plist' to '/Users/mayankjain/Library/Developer/Xcode/DerivedData/PCS_EmpApp-chsylqbxjptobeawzzckymqzagvr/Build/Products/Debug-iphonesimulator/PCS_EmpApp.app/Info.plist That's telling you that you have a copy command in the Build Phases that's copying your Info.plist file, and a second process that's generating the file. Both processes try to put it in the same place, hence the 'multiple commands produce...' error. Remove that copy command, and the build should work.

Yes, you can raise feedback reports, because they're bugs just like bugs in software. Please raise the issues separately (because they relate to separate documents) at https://feedbackassistant.apple.com/ then post the FB numbers here.

You've raised this before on these forums, but you're in the wrong place. These Developer Forums are for developers from around the world to ask for hints and tips on coding apps for Apple's platform. We aren't employed by Apple, so bugs posted on here won't get anywhere. You need to raise each issue you find separately at https://feedbackassistant.apple.com/ You can post the FB numbers here if you want, so that others can track them.

You should raise this as a bug in the usual way. It won't really get progressed if it's only posted in these Developer Forums. Especially given we aren't Apple's actual developers; we're just random people from around the world writing apps for Apple's platforms. These Developer Forums are for us to ask for hints and tips on coding. You need to raise each issue you find separately at https://feedbackassistant.apple.com/ You can post the FB numbers here if you want, so that others can track them.

Do you mean 'crashing'? Which version is 'iOS public beta'? Is it iOS 26.2 beta? Or is this the public beta before iOS 26 was first released in September? What code are you using, and what is the crash? You say you're using .glassEffect(_in:) but you don't give any actual values.

I don't know, but you're also in the wrong place. We're just third-party developers writing apps for Apple's platforms. We don't work for Apple, so posting your issue here isn't going to progress it. Just raise separate feedback reports for each individual issue - as you noted - and see if Apple can fix them.

As far as I know you cannot change the styling for a menu item because the menu is displayed appropriately for the operating system it's running on. So, trying .foregroundColor(), .foregroundStyle(), .tint() etc. likely won't work. The only way you can make a menu item red is by giving the Button the destructive role. This, by default, makes the item red, but it may also have other side effects that you may not want: Button(role: .destructive) From the documentation: Use this role for a button that deletes user data, or performs an irreversible operation. A destructive button signals by its appearance that the user should carefully consider whether to tap or click the button. For example, SwiftUI presents a destructive button that you add with the swipeActions(edge:allowsFullSwipe:content:) modifier using a red background. So please, use it wisely. In the meantime, why not raise a feedback request, and ask for a way to tint a menu item? https://feedbackassistant.apple.com/

Okay, so in the meantime you could use something like this: public struct Conditional<Content> { public let content: Content public init(_ content: Content) { self.content = content } } extension View { var conditional: Conditional<Self> { Conditional(self) } } @ViewBuilder func showAccessory(_ enabled: Bool, accessoryContent: View) -> some View { if(enabled) { if #available(iOS 26.2, *) { content .tabViewBottomAccessory(isEnabled: enabled) { accessoryContent } } else { if #available(iOS 26.0, *) { content .tabViewBottomAccessory() { accessoryContent } } else { content } } } else { content } } // Use it like this: ... MyView { } .conditional.showAccessory(true /*or false*/, accessoryContent: MyAccessoryView()) Caveat: I have not tried this.

I couldn't work around the many issues with tabViewBottomAccessory, so I just decided not to use it at all. Maybe I'll revisit it in future, but right now, nah.

From this thread: You'll want to use the new api tabViewBottomAccessory(isEnabled:content:), which allows you dynamically show and hide the view instead of an EmptyView. When isEnabled is true, the accessory view is shown, and when isEnabled is false, the view is hidden. Does that help?

These forums are not for advertising - as you have already been told. Please stop posting about your app on these forums. These forums are for developers to ask for hints and tips on coding, not for advertising apps. I have once again reported your post. No doubt you'll come back with some pointless response again, but you're in the wrong here, as you were last time.

Payment for what? If you want to pay for the Apple Developer Program, it should be in the "Account" section at the top of the page on these forums. And, why have you tagged your post with "Widgets & Live Activities"? Is this related to widgets and Live Activities or not? If not, please don't use unrelated tags on your posts.

Speak to Revolut?

Please stop using AI for simple things. There is widely available information on how the App Store review process works. You do not need to use AI to find that out. https://developer.apple.com/distribute/app-review/

It just says ItemListView: _dismiss changed. in the console. I've put the code here: https://github.com/darkpawuk/DismissFail Just create a new iOS project in Xcode, remove the standard ContentView.swift and App.swft files, and drop these ones in. Runs on iOS 17 and above (because it uses @Observable).