Search results for

xcode github

94,028 results found

Post

Replies

Boosts

Views

Activity

Xcode not updating recent projects
My Xcode does not show my Recent projects for a while now. I have different projects on my Mac that I open using Xcode and it can't remember the recent ones and never shows it. Does anyone know how to fix that? I've tried to clean caches, restart the Mac, download the Xcode again... MacOs: Tahoe 26.1 Xcode: 26.1.1
1
0
38
2w
macOS 15 (Sequoia): Endpoint Security client runs by hand, but LaunchDaemon fails with TCC “Full Disk Access” denial on unmanaged Macs
Platforms: macOS 15.x (Sequoia), Intel-Based App type: Endpoint Security (ES) client, notarized Developer ID app + LaunchDaemon Goal: Boot-time ES client that runs on any Mac (managed or unmanaged) Summary Our ES client launches and functions when started manually (terminal), but when loaded as a LaunchDaemon it fails to initialize the ES connection with: (libEndpointSecurity.dylib) Failed to open service: 0xe00002d8: Caller lacks TCC authorization for Full Disk Access We can’t find a supported way to grant Full Disk Access (SystemPolicyAllFiles) to a system daemon on unmanaged Macs (no MDM). Local installation of a PPPC (TCC) profile is rejected as “must originate from a user-approved MDM server.” We’re seeking confirmation: Is MDM now the only supported path for a boot-time ES daemon that requires FDA? If so, what’s Apple’s recommended approach for unmanaged Macs? Environment & Artifacts Binary (path placeholder): /Library/Application Support///App/.app/Contents/MacOS/ Universal (x86_64 + arm64
10
0
1.3k
2w
Reply to Popovers are broken on macCatalyst
@stoope Thanks for your post and code. Using your code I was able to show the popover without seen a crash using Xcode Version 26.2 beta (17C5013i) that is in beta at the developer website. Can you try that and let me know if resolves your issue? I would recommend to provide a focused sample and a link to the repository so we can test and see the issue. If you're not familiar with preparing a test project, take a look at Creating a test project. Albert Pascual
  Worldwide Developer Relations.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
2w
Reply to moving project to new account
Thank you for your post. Migrating your Swift project from a free Apple Developer account to a paid one does not necessitate rebuilding the project from scratch. Here is a step-by-step guide to facilitate a seamless transition: Log into Your Paid Account: Sign in to your Mac using the Apple Account associated with your paid Developer account. Open Xcode and navigate to Xcode > Preferences > Accounts. Click the “+” button to add your paid Apple ID if it is not already listed. Update Code Signing: Open your Xcode project. Select your project in the Project Navigator to access the project settings. Navigate to the “Signing & Capabilities” tab for your target. Ensure that your team is configured to your paid account. If not, click on the team dropdown and select your paid developer account. Adjust Provisioning Profiles: Xcode typically automates the downloading of provisioning profiles when signed in with the paid account. You can force a refresh by visiting Window &g
2w
Reply to UITabBar ignores font in iOS 26.2
Thanks for your post. Do you have a focused sample project where we can see the fonts in the bundle but the iOS 26.2 is ignoring but working on previous versions? To ensure your custom font is applied to UITabBar items on iOS 26.2, consider the following steps: Double-Check Font Availability: Ensure that the custom font AvenirNext-DemiBold is included in your app's bundle. Check your Info.plist to confirm that the font is properly listed under the UIAppFonts key. Use configureWithOpaqueBackground: Try setting the appearance configuration using configureWithOpaqueBackground, which might provide better consistency across different iOS versions. Debug Using Runtime: Use Xcode's debugger to inspect the titleTextAttributes at runtime on iOS 26.2 to verify if your attributes are being overwritten or ignored. I would be delighted to assist you if you could provide a focus sample that I can analyze against iOS 26.2. If you're not familiar with preparing a test project, take a look at Creating a test project.
Topic: UI Frameworks SubTopic: UIKit Tags:
2w
Reply to 90714: Invalid binary.
@nicholas3388@sina.com As you know where the issue is, if is your code or an external module, that needs to be rewritten, make sure you compile your code with the latest Xcode available and remove 3rd parties if they return that issue or use the latest version of those 3rd parties. I always point to this post where there is better guidance: https://developer.apple.com/forums/thread/793991?page=1#851267022 Albert Pascual
  Worldwide Developer Relations.
2w
Reply to URLRequest(url:cachePolicy:timeoutInterval:) started to crash in iOS 26
Hi @DTS Engineer and thanks :) I hope that your boss will get you a iPhone 17 😅 I'm trying to attach the ips-file again. I added the.txt extension to make it possible to attach it. I hope it will not screw up and make it an inline text-box when I git 'Reply' 😬 Looking at the ips-file I found that it does not show the finding that Xcode show, e.g., Thread X: Use of deallocated memory but it then misses Memory allocated by Thread 1 and Memory deallocated by Thread 1, so I am not sure the ips-file is that useful for MTE :( CrashReport-2025-11-28-141148.ips.txt
2w
Reply to Concurrency warning in Translation API
This is tricky. My best guess is that translationTask(_:action:) is missing all the magic concurrency decorations required to make this work nicely. To get this to build right now you can mark the closure as sendable, like so: .translationTask(configuration) { @Sendable session in do { try await session.prepareTranslation() } catch { // Handle any errors. } } This compiles in Xcode 26.1 using the Swift 6 language mode and: Approachable Concurrency enabled Default Actor Isolation set to MainActor Note I’m using prepareTranslation() in my examples because it’s simpler, and that makes it easier to focus on the core issue. The drawback to this is that you can no longer access main-actor-isolated state from the closure. You can work around that using MainActor.run(…): try await session.prepareTranslation() … no isolation … await MainActor.run { … main-actor isolated … } Clearly this is less than ideal and I encourage you to file a bug against… actually, I think it’d be best to file a bug against the Trans
Topic: App & System Services SubTopic: General Tags:
2w
KeyChain Sharing with App Extensions
Hi, We are trying to use Apple Security API for KeyChain Services. Using the common App Group : Specifying the common app group in the kSecAttrAccessGroup field of the KeyChain query, allowed us to have a shared keychains for different apps (targets) in the app group, but this did not work for extensions. Enabling the KeyChain Sharing capability : We enabled the KeyChain Sharing Ability in the extensions and the app target as well, giving a common KeyChain Access group. Specifying this in the kSecAttrAccessGroup field also did not work. This was done in XCode as we were unable to locate it in the Developer portal in Indentifiers. We tried specifying $AppIdentifier.KeyChainSharingGroup in the kSecAttrAccessGroup field , but this did not work as well The error code which we get in all these 3 cases when trying to access the Keychain from the extension is error code 25291 (errSecNotAvailable). The Documentation says this error comes when No Trust Results are available and printing the error in xcode
4
0
121
2w
Reply to KeyChain Sharing with App Extensions
[quote='868260022, Infibrite, /thread/809012?answerId=868260022#868260022, /profile/Infibrite'] our earlier “Network Extension” tag was a mistake. [/quote] And presumably so was the reply you posted about 10 hours before this one |-: Anyway, the behaviour you’ve described doesn’t gel with Network Extension at all, so I’ve re-tagged your thread accordingly. When dealing with keychain sharing, there are two factors in play: Build time Run time I’m gonna focus on the build-time stuff, because a) that’s where you seem to be stuck, and b) I’m not familiar with Matter extensions and there could be run-time restrictions I’m not familiar with. So, regarding your build, you wrote: [quote='868260022, Infibrite, /thread/809012?answerId=868260022#868260022, /profile/Infibrite'] Could you enable Keychain Sharing for these iOS App IDs … ? [/quote] There’s nothing for us to enable here. Every App ID supports keychain sharing [1]. To illustrate this: I using Xcode 26.1 to create a new test project from the iOS >
2w
Local Network Discovery Works in Debug but Not in TestFlight (Wi-Fi Speaker Connection Issue)
Hi team, I’m having an issue with my iOS app related to local network communication and connecting to a Wi-Fi speaker. My app works similar to the “4Stream” application. The speaker and the mobile device must be on the same Wi-Fi network so the app can discover and connect to the speaker. What’s happening: When I run the app directly from Xcode in debug mode, everything works perfectly. The speaker gets discovered. The speaker gets connected successfully. The connection flow completes without any problem. But when I upload the same build to TestFlight, the behaviour changes completely. The app gets stuck on the “Connecting…” screen. The speaker is not discovered. But the same code is working fine on Android It never moves forward from that state. So basically: Debug Mode: Speaker is detected and connected properly TestFlight: Stuck at “Connecting…”, speaker does NOT get connected This makes me believe something related to local network access, multicast, Wi-Fi info permissions, or Bonjour discovery i
1
0
139
2w
App Sandbox denies mach-register for Developer ID signed app but allows it for Apple Distribution signed app
I'm working on a multi-process macOS application (based on Chromium/Electron) that uses Mach ports for inter-process communication between the main app and its helper processes. Background I have an MAS build working successfully via TestFlight for internal testing. However, public TestFlight testing requires Apple review, and while waiting for that review, I wanted to provide a directly distributable build for external testers. I attempted to create a Developer ID signed build with App Sandbox enabled, expecting it to behave similarly to the MAS build. The Problem With App Sandbox enabled (com.apple.security.app-sandbox) and identical entitlements, I observe different behavior depending on the signing certificate: Apple Distribution certificate: App launches successfully, mach-register and mach-lookup work Developer ID certificate: App crashes at launch, mach-register is denied by sandbox The Console shows this sandbox violation for the Developer ID build: Sandbox: MyApp(13605) deny(1) mach-register XXXXXXXX
2
0
118
2w
Can't Provision A Device
Hi First, I hope I'm in the right place, I'm not certain. I'm having my first attempt at IOS development and want to see the progress I've made on my phone. I plugged it in to my Mac and selected it as a preview device and got the following messages in the Signing & Capabilities screen: Your team has no devices from which to generate a provisioning profile. Connect a device to use or manually add device IDs in Certificates, Identifiers & Profiles. https://developer.apple.com/account/ No profiles for '...' were found: Xcode couldn't find any iOS App Development provisioning profiles matching '...'. My account and personal team are shown in the Xcode settings, but it says 0 Provisioned Devices. I also tried restarting, and enabled developer mode on the phone. I checked the provided link, but saw nowhere to add a device ID. Clearly I don't understand what I'm doing. Can anyone help me make sense of this?
2
0
191
2w