Thanks, Rico. Unfortunately, CloudKit can’t replace the app group for my use case, so I’ll need to separate the targets. Hopefully, future versions of Xcode will eliminate the need for this workaround.

I just had the same error with the signing errors. For com.apple.developer.icloud-container-environment i set production or development, however it has to be Production or Development. Capital P or D. :)

You can respond and explain that your app displays non-App Store apps. Ensure everyone understands that your app focuses solely on desktop console video games.

One reason for this could be that a parent view already has a fileImporter modifier. For example the initial content view.

Thanks, but it doesn't seem to be a workaround anymore. :( import TipKit struct ContentView: View { struct ExampleTip: Tip { var title: Text { Text("title") } var message: Text? { Text("message") } } var body: some View { Text("Hello world") // .popoverTip(NewSnippetTip()) //This works .toolbar(content: { ToolbarItemGroup(placement: ToolbarItemPlacement.bottomBar) { Button(action: {}) { Label("New Snippet", systemImage: "doc.badge.plus") } .buttonStyle(.plain) // WORKAROUND: Adding this line does NOT fix the issue. .popoverTip(ExampleTip()) } }) } }

Have you been able to fix the issue? I've got the same error. On macOS it works fine, on iOs it gives me this error. url.startAccessingSecurityScopedResource() does not help. Also it works with request.requiresOnDeviceRecognition = false

You could als just use ToolbarItemGroup: struct ContentView: View {   var body: some View {     NavigationView {       List {         ForEach (1..<10) {           row in           Text("\(row) - Test").foregroundColor(Color.white).fontWeight(.bold)         }         .listRowBackground(Color.burgundy)       }             .navigationTitle(Text("List Background Color Test"))       .navigationBarTitleDisplayMode(.inline)       .toolbar {         ToolbarItemGroup(placement: .bottomBar) {           HStack {             Button(action: {}, label: {               Text("One").foregroundColor(Color.white)             })             Spacer()             Button(action: {}, label: {               Text("Two").foregroundColor(Color.white)             })             Spacer()             Button(action: {}, label: {               Text("Three").foregroundColor(Color.white)             }).foregroundColor(.blue)           }         }       }           }               } }

Vincent, you have to uncheck "Ask Where To Save"

So your Shortcuts Workflow looks more or less like this? Did you check the Privacy section?

Hi there, yes I do receive the file from the input and I've also figured out how to access the file with the Sandbox enabled:     func handle(intent: ExamplePDFIntent, completion: @escaping (ExamplePDFIntentResponse) -> Void) {         if let files = intent.files, {             var outputFiles = [INFile]()             for file in files {                 if file.fileURL!.startAccessingSecurityScopedResource() { //do your work here file.fileURL!.stopAccessingSecurityScopedResource() } else { //don't forget error handling } } } } So we have to use security scopes: https://developer.apple.com/documentation/foundation/url/1779698-startaccessingsecurityscopedreso Makes sense now that I know it :) Cheers

You have to contact Apple directly via https://developer.apple.com/contact/topic/select That's probably because depending on the state of your business, they need some legal documents.

You can contact them here: https://developer.apple.com/contact/topic/select

Update: Developer ID signed apps can be activated by manually by the Developer Technical Support."Generally speaking, the Privileged File Operation entitlement is for apps destined for the Mac App Store, as there’s no other way to accomplish the tasks it enables there (unlike non-Mac App Store apps, which don’t have some of those restrictions).That said, we can enable it for this app to ensure a consistency in your codebase."

Thanks. I will open a TSI and update this thread as soon as I know more.

Anyone? eskimo? 🙂