When I try to archive an app in order to submit it to the App Store I receive the following errors I do not know how to fix: error: Framework /Users/fbartolom/Library/Developer/Xcode/DerivedData/Virtual_Tags-apzduassdiglhcapscsllvzbfgid/Build/Intermediates.noindex/ArchiveIntermediates/Virtual Tags/InstallationBuildProductsLocation/Applications/VirtualTags.app/Frameworks/StoreKit.framework did not contain an Info.plist (in target 'VirtualTags' from project 'Virtual Tags') error: Framework /Users/fbartolom/Library/Developer/Xcode/DerivedData/Virtual_Tags-apzduassdiglhcapscsllvzbfgid/Build/Intermediates.noindex/ArchiveIntermediates/Virtual Tags/InstallationBuildProductsLocation/Applications/VirtualTags.app/Frameworks/Security.framework did not contain an Info.plist (in target 'VirtualTags' from project 'Virtual Tags') error: Framework /Users/fbartolom/Library/Developer/Xcode/DerivedData/Virtual_Tags-apzduassdiglhcapscsllvzbfgid/Build/Intermediates.noindex/ArchiveIntermediates/Virtual T
Search results for
Xcode
92,303 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
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
Topic:
App & System Services
SubTopic:
General
Tags:
App Store
Entitlements
App Sandbox
Developer ID
After having used Obj-C and C++ for years, I recently (~6 months) moved to Swift, which is hard for me but most often sends less obscure error messages (not always). My trouble is 1- why is it soooooo long (sometimes up to 20s - that's horrible) to get an object's variables accessible in the debugger? 2- In Xcode 16 why is it no longer possible to arrange my files as I did before (organised into folders from within Xcode - horrible when you get a bigger and bigger project)? 3- Why has it become impossible to see the retention cycles and retaining objects from with the memoryGraph (it's worth ~nothing) now !
Hello, My project is GitLab and to access it we need VPN. How to connect Xcode Cloud to that repo if VPN is required for read it? Any solution to this? Any help is appreciated
Summary NetworkConnection in iOS 26 Network framework throws POSIXErrorCode(rawValue: 22): Invalid argument when receiving WebSocket ping (opcode 9) or pong (opcode 10) control frames. This prevents proper WebSocket keep-alive functionality. Environment iOS 26.0 (Simulator) macOS 26.1 Xcode 26.0 Note: This issue was initially discovered on iOS 26 Simulator. The same behavior was confirmed on macOS 26, suggesting a shared bug in the Network framework. The attached sample code is for macOS for easier reproduction. Description When using the new NetworkConnection API introduced in iOS 26 or macOS 26, the receive() method throws EINVAL error whenever a ping or pong control frame is received from the server. This is a critical issue because: WebSocket servers commonly send ping frames to keep connections alive Clients send ping frames to verify connection health The receive callback never receives the ping/pong frame - the error occurs before the frame reaches user code Steps to Reproduce Create a WebSock
Thank you for your reply. I understand that the following is a reserved character in XML: & Below are the current expected and actual values. Driverkit expected value 0x00001916&0x0000FFFF Provisioning file contents 0x00001916&0x0000FFFF Entitlements file contents 0x00001916&0x0000FFFF I'm not sure why Xcode Signing Certificate status is Failed with the above configuration. It doesn't seem to me that Driverkit and the provisioning file expect & as the expected value. Based on the above, isn't it Xcode that expects &? I'm suspicious of Xcode's behavior. I'm worried that resubmitting the authorization request won't improve the situation. Is my understanding incorrect?
Topic:
Code Signing
SubTopic:
Entitlements
Tags:
Currently Xcode has iOS simulators that allow easily testing apps on older versions of iOS. It would be helpful if there was also a macOS simulator for testing apps on older versions of macOS. FB21229682 https://github.com/feedback-assistant/reports/issues/724
I am having the same problem. Brand new iPhone Air and Watch Ultra 3, all on OS26.1, xcode 26 just installed/upgraded everything. Creates a new watch app project, says WatchOS version lower than deployment target, unable to deploy to watch...
Topic:
UI Frameworks
SubTopic:
UIKit
Tags:
Thanks for the post. This is interesting you want to remove some support. On top of my head. What about setting the architecture the project supports? Xcode Project Settings: Open your project in Xcode. Go to your project settings by selecting the project file in the Project Navigator. Select your app target, then navigate to the Build Settings tab. In the search bar, type Valid Architectures. You may need to show all settings by clicking the All button at the top. Set Valid Architectures to arm64. This change ensures that your app is built only for Apple Silicon, which uses the ARM architecture. Will that work for what you trying to accomplish? Other developers here may have better ideas of how to drop support for Intel. Please be sure to note that if you targeting the App Store. In general, App Store does not allow you to ‘narrow’ your requirements. You can’t remove support for device type in a newer version. There is a device narrowing exception that you can apply for to allow this sort o
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports. Bug Reporting: How and Why? has tips on creating your bug report.
Topic:
Safari & Web
SubTopic:
General
Tags:
For iOS17 we've had no problem playing Apple Fairplay encrypted content with keys delivered from our key server running on FairPlay Streaming Server SDK 5.1 and subsequently FairPlay Streaming Server SDK 26. It's built and deployed using Xcode Version 26.1.1 (17B100) with no changes to the code and - as expected - the content continued to be successfully decrypted and played (so far so good). However, as soon as a device was updated to iOS26, that device would no longer play the encrypted content. Devices remaining on iOS17 continue to work normally and the debugging logs are a sanity-check that proves that. Is anyone else experiencing this issue? Here's the code (you should be able to drop it into a fresh iOS Xcode project and provide a server url, content url and certificate).
Hi @jrodriguer, it's not clear to me exactly what error or problem you are experiencing. If it's a build failure, can you copy and paste the failing command from the Build Log in Xcode, including both the command it attempted to run and the error message?
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Hi everyone, could you help us? We implemented a Flutter library that basically makes a call every x minutes if the app is in the background, but when I generate the version via TestFlight for testing, it doesn't work. Can you help us understand why? Below is a more detailed technical description. Apple Developer Technical Support Request Subject: BGTaskScheduler / Background Tasks Not Executing in TestFlight - Flutter App with workmanager Plugin Issue Summary Background tasks scheduled using BGTaskScheduler are not executing when the app is distributed via TestFlight. The same implementation works correctly when running the app locally via USB/Xcode debugging. We are developing a Flutter application that needs to perform periodic API calls when the app is in the background. We have followed all documentation and implemented the required configurations, but background tasks are not being executed in the TestFlight build. App Information Field Value App Version 3.1.15 (Build 311) iOS Minimum
Topic:
App & System Services
SubTopic:
Processes & Concurrency
I have been using Xcode Version 26.1.1 on macOS Tahoe Version 26.1. In VIM mode, whenever I quickly tap d twice, to delete the complete line, most of the time Xcode crashes. Is anyone else facing this issue? Should I move to any older version of Xcode or any other solve for this?
[quote='867739022, chrismuench, /thread/769472?answerId=867739022#867739022, /profile/chrismuench'] I still have this problem with Xcode 26! [/quote] That gels with my reading of this bug’s state (FB7791261). [quote='867739022, chrismuench, /thread/769472?answerId=867739022#867739022, /profile/chrismuench'] I still have this problem with Xcode 26! Is there any solution for this? [/quote] Solution to what? This bug prevents you from seeing the device’s profiles, but that doesn’t prevent you from developing. In the standard development workflow your app’s provisioning profile is embedded in the app itself, so this view is irrelevant. If the app is installed, it’s profile is installed. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Tags: