Apparently the code should not have used AsyncImage for a local file - but the logic remains the same

Revised code with raw file taken from Xcode asset (Still have the same issue) struct ContentView: View {   @State private var image: Image?   var body: some View {     VStack {       image?         .resizable()         .scaledToFit()     }     .onAppear(perform: loadImage)   }   func loadImage() {     guard let asset = NSDataAsset(name: "Rawsample") else { return }     let data = asset.data     image = Image(uiImage:UIImage(data:data)!)   } }

Yes same here

No - all the information is there - its just very difficult to access using the tools Apple provides.

Did you find a solution? I'm getting the same message and I've done this many times for this app in the past.

Hmm - it seems that changing Signing Certificate to Development works in my situation

Same problem - I've gone as far as completely reinstalling Xcode - no change. Google gave a couple of suggestions where this message has shown up in the past - but they did no good either.

Working OK now (without any further changes at my end)

The background process only needs access to the files while the metadata are extracted - nothing needs to persist. If the client wanted more or different metadata - even from the same image file - it would be acceptable to run the procedure again.

The current method of launching the server process: try SMAppService.loginItem(identifier: "abcd").register() I am open to any suggestions.

Thanks a lot - I will give this a try - it is not a problem for all the clients to share the same app group and be published by the same team. I have done something similar using an XPC service with a single client but that seems much more straightforward to implement. Generating the named XPC endpoint from a Swift app appears more complicated and tutorials/examples hard to find. ChatGPT points me to using launchctl from the command line to register a MachServices name but this would make it complicated to distribute the application.

Thanks again - plenty to think about here

Before I get too far into inter process communication I've been testing the concept of passing file descriptors using XPC by using an XPC Service (this should allow me to debug the XPC communication syntax). Is it sufficient to pass a FileHandle? Passing a FileHandle is straightforward and works well with the XPC Service but would it work across processes or do I need to find some way of passing a raw file descriptor? Passing raw file descriptors seems much more complex - especially in a pure Swift application. I tried passing UnsafeMutablePointer but that failed and crashed the application.