@DTS Engineer I actually figured out the issue. The problem was using a protocol for the dependency. Once I switched it to a concrete class, the error went away. Also, using SwiftUI lifecycle FWIW

Hey Ed (@DTS Engineer) appreciate the response. I tried your suggestion, and I'm hitting an error when I try and run the intent: WFActionErrorDomain error 16. I'm not really sure what this means and there's no info on it. While rewatching the "Migrate custom intents to App Intents" WWDC to see if I missed anything I noticed the speaker said "App Intents cannot be added to a framework target", which seems to contradict what you said earlier. Any advice (picture of the WWDC video attached)? https://developer.apple.com/videos/play/tech-talks/10168 @ 7:25

I have opened a feedback for this, including a sample project: FB14323687

Still an issue in Xcode 16.0 beta (16A5171c)

All respect eskimo, but "working with your IS department" is not a feasible solution for those of us that work in large companies. Using a VPN is a very common requirement for corporate work, and intentionally breaking that workflow is a slap in the face to those of us in the corporate world that are passionate about iOS development. I'm hopeful that Apple sees this and walks back this requirement.

@Gualtier Malde can you elaborate on the known issue? We're seeing the same thing, and want to verify it's only happening to devices that have had dev versions of the app installed.