Similar issue, after few days submitted for expedited review. Rejection on expedited review for use of background entitlement. Submitted new build and responded to reviewer with live demo and reason for use of entitlement-- waiting for a few days now. App has been extensively tested. I really hope the volume of slop apps aren't negatively affecting review processing and testing for apps specifically designed for Apple using the latest technology, design standards, quality and performance testing. I even attended in person performance and design events at Dev Center to make sure I got everything right.

They're updating App Store Connect on August 8. Most likely cause of issue.

Waiting 3 days for review. (Longer than ever before) Let's see what happens, considering expedited review request due to application quality thoroughly tested already - everything is good to go for release.

How many screens do you have for your onboarding how fast do you get there user to their first win/core experience?

One of my screens is gesture based, when testing for Voice Control the controls that are activated via gesture are not visible as there's not visible button UI. The solution I have now is to add a toolbar action item to make controls visible but this changes the experience of the UI by having fixed control always visible. If there was a was to detect Voice Control being active I'd be able to show the toolbar action item control ONLY in Voice Control mode while maintaining the same visual interface.

User can set the parameter in Shortcuts and save it as a name. If no parameter is provided it will prompt (let's say you have a Shortcut Control/Intent). Otherwise create an intent without a parameter and it will open to that page. That's how I'd do it.

I have text from a "document" in my app what schema should I conform too? Its plain text

There needs to be a visual wizard for App Intents built into Xcode as either a template or an instrument.

Any update on this?

You're the best, Apple. Thank you. Hopefully see you there. https://developer.apple.com/events/view/8D4G7DD8LR/

The voices are intellectual property of Apple and cannot be re-sold/commercialized as your own.

Would you please provide code sample for conditional branding and how to do this for example if targeting iOS 26+ and future versions? Lets say API availability in 26, new update to 26.4 so theres newer functionality in 26.4 how would you set up these branches? Please advise.

Figured out the implementation! For anyone interested in implementing in IOS 26+ @Namespace private var namespace @State private var presentDialog: Bool = false and in the toolbar ToolbarItem(placement: .cancellationAction){ Button(role: .destructive) { presentDialog = true } label: { Text("Delete") } .confirmationDialog( "Delete?", isPresented: $presentDialog, titleVisibility: .visible ) { Button("Delete", role: .destructive) { // perform delete } Button("Cancel", role: .cancel) { } } }

Quality product Clear value Marketable, and different my strategy

I sincerely hope you get this resolved, especially if you invested time, energy thought into creating a unique and thoughtful experience that can deliver value to people on the App Store!