“Xcode”

Thanks for that, always hard to read XML as Xcode presents that pretty good. It looks completely clean and the com.apple.developer.associated-domains only contain keys that are allowed https://developer.apple.com/documentation/BundleResources/Entitlements/com.apple.developer.associated-domains Will be good to go over that: https://developer.apple.com/documentation/bundleresources/entitlements/com.apple.developer.associated-appclip-app-identifiers So the string should start with applinks: and the section for app domains should only contain the app clips: https://developer.apple.com/documentation/xcode/supporting-associated-domains. I'm going to post a way for us to connect and go over your project to review the project. Probably we will need to go over Xcode. I'd like you to submit a code-level support request so we can discuss this further privately. When you create the request, indicate that you were referred by me at Apple and make sure to include a link to this thread. Albert Pas

I was offline for a couple of days. I stepped through the above steps. Step one was working OK. Step 3 was working OK. I have no idea what is going wrong. I think I will revoke my developer certificate an try to start with a fresh one. Xcode must store some information outside of of the source code with is GIT controlled.

For future reference, I'd recommend replying by posting as a fully reply instead of using the comments feature, as full replies are harder to mess in our tooling than comments. Thanks for the update, the bug is already created: FB16923149 Perfect! Please try adding the entitlement again, as this should now be fixed in both the portal and Xcode. Note that you may need to quit and relaunch Xcode for it to pick up the new entitlement option. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

Albert Pascual -- I am unable to send a code-level support request because I no longer have a paid developer account. Without going into grim detail, since I could no longer type very well after the accident, I had to leave my career as a developer. It sucked. I had been doing backend development back when there was a Mac OS X Server and an ADC membership was $500 a year. But being disabled as I am gave me a lot more appreciation for accessibility in macOS. Having these things working is important to my quality of life. Last night I installed 26.4 RC and there are multiple new issues. At this point I'm going to have to reset to 26.0 because too much of what I rely on either doesn't work or has become too irritating. A few examples: the orange dot in the upper right corner somehow became more distracting as it is now an orange square with a black border. Still just as useless but now extra annoying. Now when I say Hey Siri and my computer is locked, Siri responds with You will need to unlock

Definitely a hell of an experience in the worse way. Apple Watch Series 4 iPhone 11 Mac Neo I had 0 issues developing/deploying to Pixel WearOS, but obstacles after obstacles, developing for and deploying to Apple WatchOS. After several days of working around each obstacle with the help of Gemini, I'm adding the summary of what I had to do so far to get to initial deployment in case this helps Apple/others with fix/workarounds: Here is the complete technical post-mortem for the development environment setup. This summarizes the specific hurdles cleared to get a Watch Series 4 (watchOS 10.6.2) communicating with your Mac via a No-SIM iPhone bridge. 🛠️ Environment Recovery Summary The Networking Layer The primary blocker was extreme network instability on the default 10.0.0.x gateway. The Symptom: ping tests showed 62% packet loss and 1,000ms+ latency. The Fix: Migrated all devices to a clean 192.168.86.x subnet. The Result: Achieved 0% packet loss and ~13ms latency, providing the stable pipe required for the

Dear Quinn, In February 2021, when an Entitlement was added to Team ID WEJZZZZZZZ, I received the following email from Apple and learned how to add the Entitlement to a provisioning profile: Hi, Does Apple add entitlement to my team ? (== App ID: WEJZZZZZZZ) Yes, the entitlement was actually added to your “team”. That gives you the ability to add the entitlement to any app that’s managed by your “team”. Here is the configuration information you can use to check the current status and/or configure your own project: -To use the entitlement, you need to codesign your app with a provisioning profile that includes it. In the Apple developer portal website, you’ll need >to do the following: In the “Provisioning Profiles” section, click the “+” and to create a new profile In the “What type of provisioning profile do you need?” section, select “iOS App Development” Walk through the creation process and directly after the “Select devices.” section, you should see a new section titled “Do you need additional ent>

I am seeing a similar issue, but only for my Mac Catalyst archive on XCode 26. My app is a SwiftUI application that embeds an Objective-C framework built from a separate Xcode project. The framework binary itself does have UUIDs, but when I inspect the .xcarchive, the corresponding framework dSYM is missing from the archive’s dSYMs folder. What is confusing is that this does not happen for the iOS build. I use the same framework target, and when I archive the iOS app and upload to TestFlight, I do not get the warning. The problem only appears when I archive the Mac Catalyst version. So in summary: • The embedded framework binary is present in the archive • The framework executable has valid UUIDs • The app archive’s dSYMs folder does not contain the matching dSYM for that embedded framework • This only happens for Mac Catalyst • The same setup works correctly for iOS Has anyone seen Catalyst archives skip generating or packaging dSYMs for embedded frameworks, even though the binary itself co

Filed here: FB22276321 (Xcode Cloud build encountering persistent Connection Refused error)

Do these IP's ever change? Rarely, but it does happen. The list you see was recently updated, and these changes are announced through the Xcode Cloud Release Notes, so you can see when the recent update happened. Are there specific ports Apple uses? Would be nice to limit to only what's needed. None are documented, so you shouldn't make any assumptions about port selection. Do we have to open in-bound access or can we instead have our builds reach out with an outbound only setup? Xcode Cloud requires inbound access, that is noted in the document you linked to very briefly. — Ed Ford,  DTS Engineer

By contrast, I can sign in to the Sandbox Apple Account without issue on a physical device. The problem occurs only via Simulator. That is the expected behavior. To test in the sandbox environment, you need a physical device. For more information, see Testing In-App Purchases with sandbox. StoreKit Testing in Xcode is a local test environment for testing in-app purchases without requiring a connection to App Store servers. You can use it to test In-App Purchases in the Simulator without a Sandbox account.