When will TrustInsights be available to test

Are you sure you’ve selected an iOS run destination? I just tried reproducing your issue and everything worked for me.

Specifically:

1. Using Xcode 27.0b2 on macOS 26.5, I created a new app project.

2. I saved it as “Test835771”.

3. At the top, I selected Any iOS Device as the run destination.

4. In the Signing & Capabilities editor, I set the bundle ID to something unique (com.example.apple-samplecode.eskimo1.Test835771).

5. And chose my team, an Individual team, in the Team popup.

6. And added the Trust Insights capability.

7. In ContentView.swift, I added this to the import section:

   import TrustInsights
   

8. I chose Product > Build, and the app built just fine.

Now, obviously that’s not the same as me actually using the API, but it should be enough to get you started (-:

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Hi! After successfully adding the capability to my project, I am also not able to „import TrustInsights“ using Xcode 27 beta 2.

Error: "Unable to resolve module dependency: 'TrustInsights'"

Thanks, Alex

I suspect you’re building for the simulator. Note step 3 in my previous post. While I don’t expect TrustInsights to actually work on the simulator, right now it won’t build for it, which is very inconvenient. I’ve filed my own bug about that (r. 180909555).

Pending a fix for this you can use targetEnvironment(simulator) to disable your TrustInsights code in simulator builds. For example

#if !targetEnvironment(simulator)
import TrustInsights
#endif

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Would Apple consider providing an API or URL scheme to navigate users directly to the Impersonation Risk Detection settings page?

Once a user denies the authorization prompt, the AuthorizationStatus returns .denied with no programmatic way to re-request permission. Unlike other privacy permissions (e.g., Notifications via UIApplication.openNotificationSettingsURLString), there is currently no mechanism to deep-link users to the "Share with App Developers" toggle under Impersonation Risk Detection settings.

This creates a dead-end UX — developers have no way to guide users back to re-enable the feature short of providing manual navigation instructions (Settings > Privacy & Security > Impersonation Risk Detection).

A dedicated URL (similar to UIApplication.openNotificationSettingsURLString) or a framework method to open the relevant settings pane would significantly improve the recovery flow for users who initially deny and later wish to opt in.

That seems like a pretty reason enhancement request, and I encourage you to file it as such.

Please post your bug number, just for the record.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"