“xcode github”

Thank you for the post. Associated Domains work the same in the watchOS. There is an important note: https://developer.apple.com/documentation/xcode/supporting-associated-domains#Add-the-associated-domains-entitlement-to-your-app For a single-target watchOS apps, add the Associated Domains capability to the watchOS app target. For watchOS apps with separate WatchKit extensions, you must add the Associated Domains capability to the WatchKit Extension target. Because the Apple Watch lacks a traditional web browser and has a smaller screen, testing and diagnosing Associated Domains (like Universal Links) requires a slightly different workflow. Just like on iOS, if your apple-app-site-association (AASA) file is hosted on a local server or a dev environment not reachable by Apple's CDN. Since you cannot paste a link into a Diagnostics menu, you have to trigger the link exactly how a user would encounter it on their wrist. The most reliable way to test is to use the Messages or Mail app. Send the Universal

Sorry for asking after such a long time,isn't there any way to add a thumbnail to replace the blue swirl galaxy ? Actually,the person for whom i made the thumbnail reverted to me after long time asking can you try and see if there is any further way to show the thumbnail in the screen saver or make it look a little more professional ? Also installing the screensaver on their Mac shows the security warning so i guess it would be solved by just signing the screensaver. I haven't signed any screensaver before so i have no idea. Let me know if there is any other steps apart from just enabling signing in Xcode.

Thanks, I believe you also sent a code level support request? The watch as the error “untrusted” occurs when the app provisioning profile is missing. Have you deployed the app using Xcode? I requested the sysdiagnose from you to check on the untrusted app trying to launch. Thanks Albert
  Worldwide Developer Relations.

An update: when I remove ALL of my keychain groups except for com.apple.token (i.e. I removed the one for pivtoken), it works ONLY WITH my enterprise provisioning profile. For some reason, xcode is OK with me manually modifying my .entitlement file to remove the app prefix ID that xcode is automatically adding. If I use my own personal account, xcode is NOT OK with me modifying the provisioning profile to remove the app prefix from com.apple.token (xcode says my provisioning profile doesn't match the entitlements file's value for the keychain-access-groups entitlement. ) I'd like to get it working in both scenatios. Is there something I can do in xcode to make my automatically-managed one work?

I've run into the same issue as you. I also tried installing Xcode 26.4, Can you please share the any resolution ?

@DTS Engineer Quinn, Thank you for your reply; I think I'm on a better path now. Unfortunately, I'm now getting an -34018 error and nil with the code below: var result: CFTypeRef? let status = SecItemCopyMatching([ kSecClass: kSecClassCertificate, kSecAttrAccessGroup: kSecAttrAccessGroupToken, kSecMatchLimit: kSecMatchLimitAll, kSecReturnRef: true, ] as CFDictionary, &result) print(status=(status) result=(String(describing: result))) I've tried your trouble shooting steps mentioned in your other posts, including printing out my app's entitlements, and they all look correct: application-identifier MY_APP_ID.MY_APP_BUNDLE_ID com.apple.developer.default-data-protection NSFileProtectionComplete com.apple.developer.team-identifier MY_APP_ID com.apple.security.application-groups get-task-allow keychain-access-groups MY_APP_ID.com.apple.token MY_APP_ID.com.apple.pivtoken MY_APP_ID.MY_APP_BUNDLE_ID I've tried both an xcode-managed provisioning profile, and an enterprise one owned by my org, and n

I've run into the same issue as you. I also tried installing Xcode 26.3, and opening the project with the older version did work once. But for some reason the same problem reappeared later, and using 26.3 no longer helps.

This is definitely unusual. You’ve already eliminated a bunch of the more common causes of issues like this. AFAICT your team received the Contactless Pass Provisioning (SharableCredential) capability for all App IDs. I’d like to exploit that fact to run a diagnostic test: Using the same Xcode, create a new project from the iOS > App template. When creating the project, enter a new test bundle ID and select your standard team (Team ID S7AUTD2C2B). In Signing & Capabilities, make sure automatic code signing is enabled for all configurations. And that the correct team is selected. At the top, make sure that you have a test device selected as the run destination. Then add the Contactless Pass Provisioning (SharableCredential) capability. Automatic code signing should kick in and create a new development provisioning profile. Wait for that to finish. Assuming that works, try running the app on a test device. What do you see? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ App

has there been any update to this? This is still happening on latest xcode