Also facing this issue. I created an xcprivacy file for the sample app and it only pulls in it's own data, nothing from a third part

Thanks for the response @eskimo! Does that mean that I need to keep expired certificates around forever? For App Store releases revoking expired certificates had no impact, but now when we use a certificate to sign an XCFramework it would seem that that is no longer a safe step to take. Is this correct?

@eskimo thinking about it I have another question as well. You mentioned how this is a critical feature for Developer ID apps, and digging in more, Developer ID certificates last for 5 years vs iOS certificates only lasting 1. Is it possible to use a Developer ID certificate to sign an XCFramework and reduce the number of expired certificates we would nee to maintain?

Bump on this. I have the same problem as @baker2795 where I got it for the main app but forgot I needed it for the device activity extension. I think I’ve requested it three times now. Contacted Apple support who asked if I received a follow up number which I have not. Does that mean it wasn’t submitted correctly? This whole process is so unclear and frustrating. @baker2795 you said you spoke to the entitlements team. Could you share cost contact info for them? I’d be very grateful

@MCStoufer1's suggestion helped, I can now successfully pause at breakpoints. However, I can't debug. Printing out anything just gives me the memory address of the variable as opposed to it's value. The second I hit a breakpoint, lldb spits out: Couldn't find the Objective-C runtime library in loaded images Running Xcode 16.3 and macos 15.4. This is a massive blocker for me.