“xcode github”

Ignore my Dropbox post. I set something up in Github instead. I hope this helps someone:) https://github.com/psulak/Tahoe-Sequoia-Hybrid-Icon

Thanks so much for this post. That documentation you provided should have work on this sections https://developer.apple.com/documentation/xcode/installing-the-command-line-tools#Uninstall-the-Command-Line-Tools-for-Xcode-package sudo rm -rf /Library/Developer/CommandLineTools To delete the package receipt, run the sudo pkgutil command with the --forget option in Terminal: sudo pkgutil --forget com.apple.dt.commandlinetools I would recommend to go over all the steps on the documentation If the task succeeds, pkgutil prints the following message: sudo pkgutil --forget com.apple.dt.commandlinetools No receipt for 'com.apple.dt.commandlinetools' found at '/'. Albert
  Worldwide Developer Relations.

Hello @kai_, Your sample code uses a standard font which will adapt to the users selected font size. iOS provides a wide range of text sizes for the user to select from. Build your app to be accessible to users who select a different text size. For more information see Typography and Font. When I run your code on an iPhone 15 with 26.4, I can see the full text. It seems the size of the text in your environment does not fit within its content margins. To see these margins, try using Xcode's Debug View Hierarchy feature. Take look at these margins and resource, let me know what you find.  Travis

My test projects for anyone who wants to try this madness. Requires installing Xcode 26.0.1. Follow the 2 Read Me files included. At some point I may clean this up and post it on Github. But Dropbox will have to do in a pinch: https://www.dropbox.com/scl/fo/pyqw2s06pzc4gacdrysmf/AHp6Bqy7dzfGZz34jOoG6F0?rlkey=cziky74r2hwxfo9m4gpd6fpif&st=8z7au8wn&dl=0 If someone comes up with a cleaner way to do this, please share with the whole class:)

Thank you for your post and for your patience in awaiting a response. I initially anticipated a response from an Apple Watch engineer. However, your post may benefit from additional information or a link to the App Store where the app can be downloaded to add the complication and observe the issue? As I’m not an expert on that. Is your complication using WidgetKit or ClockKit? Please provide as much background information as possible and take a look at this documentation if you haven’t done it before: https://developer.apple.com/documentation/widgetkit/converting-a-clockkit-app When a user downloads your app from the App Store, the iPhone’s Watch app which is responsible for configuring the watch face on iOS attempts to read the complication descriptors/metadata from your iOS app's bundle or the bundled Watch app. Ask a user to download the app from the App Store, launch the iOS app, launch the watchOS app, and then try to add the custom watch face from the iPhone. Is that working? Since you cannot attach Xcode

[quote='885427022, DTS Engineer, /thread/812992?answerId=885427022#885427022'] Did anyone file a bug about this? [/quote] Filed the bug report Reproduces the 'lying delete' + stuck Deleting state on Xcode 26.4.1 / macOS 26.4.1, plus a second orphan revealed by scan-and-mount.

Thanks for the post. This normally occurs when updating to newer versions of Xcode as swift support requirements, the validator checks the swift the executables from Frameworks folders in the app, and makes sure that the names match 1 to 1. The libswiftCompatibilitySpan.dylib library. The ITMS-90429 error triggers because App Store Connect is extremely strict about how Swift dynamic libraries are packaged inside your exported .ipa file. What version of Xcode are you using? When you manually copy the .dylib into the app's Frameworks folder, it fails App Store validation because Apple requires Swift libraries to exist inside the folder at the root of the .ipa archive. Are you manually doing that? Or are you are using CocoaPods? I would recommend to also check this thread https://discussions.apple.com/thread/256135560?sortBy=rank Albert
  Worldwide Developer Relations.

Same symptom on a different Team ID (MCN4U9B2K4, bundle com.michaeltocco.Sanbox, Xcode 17, iOS 18.5, Automatic signing). ShazamKit ticked in App Services and persisting across portal reloads; Xcode fails with Entitlement com.apple.developer.shazamkit not found and could not be included in profile. The profile Apple just issued (2026-04-22) for my App ID carries only application-identifier, keychain-access-groups, get-task-allow, and com.apple.developer.team-identifier — no com.apple.developer.shazamkit. Already tried: deleting + recreating the App ID from scratch, the uncheck/save/wait/re-check/save capability-toggle trick, purging cached profiles between every attempt, -allowProvisioningUpdates, device target (not Simulator). Same issuance pathology persists. Runtime (when forced against a team wildcard profile for testing) returns com.apple.ShazamKit Code=202 Missing entitlements → AMS 306 → HTTP 401 from api.shazam.apple.com/v1/catalog/US/match, which is consistent with the entitlement ne

Thanks for the post. It looks like also yesterday you open a bug? Can you confirm that providing the FB number here? For that entitlement there is an additional approval step required. The com.apple.developer.proximity-reader.payment.acceptance entitlement is a restricted entitlement. This means you cannot simply add it to your .entitlements file in Xcode and check a box in the Developer Portal; you must explicitly apply for it and be granted permission before your provisioning profiles will actually include it. Because your Apple Developer account hasn't been officially granted this entitlement yet, the provisioning profiles you are regenerating do not contain it. When Xcode archives the app and verifies it against the profile for TestFlight, it sees the mismatch and throws that exact error. Request the Entitlement from Apple. You must submit a request for the Tap to Pay on iPhone entitlement. https://developer.apple.com/contact/request/tap-to-pay-on-iphone/ Albert
  Worldwide Developer Re

@Steve4442 Quick FYI: I actually have the 2 different icons working now (Liquid Glass Icon Composer .icon appears in Tahoe, and my current Legacy .icns appears in Sequoia). It's a huge mess to do, but it is possible. In my case I had to: Generate a Legacy .icns via Terminal (instead of using an Asset Catalog in Xcode) Install Xcode 26.0.1 Create a simple test app with a Shell Script that runs actool to build the Asset.car file. Build my test app with Xcode 26.0.1 Copy the resulting Assets.car and the Terminal-built .icns, into my Xcode 24.3 production project. Tweak my Xcode 24.3 production project's Info.plist and build. Final app displays two different icons: LG in Tahoe, Legacy in Sequoia. To give you an idea of how messy this is, I had to follow much of John Siracusa's advice from here: https://mjtsai.com/blog/2025/08/08/separate-icons-for-macos-tahoe-vs-earlier/ If anyone really wants to go through this major hassle, I can try to write up instructions here. Bu