I just purchased the Apple Developer Paid Account on the 3rd of October to start development on an App and hasn't been able to use it even once I’m having an iOS code-signing/provisioning issue where development/Ad Hoc builds complete successfully, but the app cannot be installed on my registered iPhone. The same issue occurs with builds produced through both Xcode and Expo EAS Build, so at this point I don’t think this is specific to EAS. When installing the app on the device, iOS shows: Unable to Install “Sencard” This app cannot be installed because its integrity could not be verified. The device logs give a much more specific error. Environment Apple Developer account type: Individual Team ID: 26K9NDX728 Main bundle identifier: com.sencard.mobile Widget extension bundle identifier: com.sencard.mobile.widgets App Group: group.com.sencard.mobile Physical iPhone registered in the Apple Developer portal Expo SDK: 57 EAS distribution: Internal / Ad Hoc The same device is included in both provisioning profiles The issue also occurs when building/installing through Xcode The application contains a WidgetKit extension, so there are two targets: Sencard com.sencard.mobile ExpoWidgetsTarget com.sencard.mobile.widgets Both targets use the same Apple Distribution certificate, with separate provisioning profiles as expected. Current signing configuration I completely reset the signing credentials and let EAS regenerate them. Both targets now use the same distribution certificate: Distribution Certificate Serial: 64FE74F9A8F0091A81671D9CDE9F7CDB The main application has its own active Ad Hoc provisioning profile: Bundle ID: com.sencard.mobile Provisioning Profile: 7D9CS7B97R Status: active Registered device: included The widget extension has a separate active Ad Hoc provisioning profile: Bundle ID: com.sencard.mobile.widgets Provisioning Profile: DY3D63UHPX Status: active Registered device: UDID: 00008130-************001C EAS reports: All credentials are ready to build @sencard/sencard (com.sencard.mobile, com.sencard.mobile.widgets) The build itself completes successfully. Device-side failure I captured the device system log while reproducing the installation failure. The important part appears to be Apple’s online provisioning authorization service rejecting the profile: online-auth-agent: The server returned: {"actions":["REJECT_PROFILE"],"authorized":false,...} online-auth-agent: Permanently rejected profile This is immediately followed by: installd(libmis.dylib): No online authorization (0x2) installd(libmis.dylib): validation failed because of failing online authorization (-402620392) Then MobileInstallation reports: The identity used to sign the executable is no longer valid. and: Failed to verify code signature of .../Payload/Sencard.app 0xe8008018 (The identity used to sign the executable is no longer valid.) Finally: Verification stage failed and the installation fails. What seems particularly significant is that the device contacts the online authorization service successfully, but the response is explicitly: "actions":["REJECT_PROFILE"] "authorized":false Things I have already tried I have done a fairly extensive clean reset of the signing configuration: Deleted the existing Ad Hoc provisioning profiles. Removed the existing distribution certificates from EAS. Revoked the corresponding distribution certificates in the Apple Developer portal. Created a completely new Apple Distribution certificate. Generated completely new Ad Hoc provisioning profiles. Verified that the provisioning profiles show as active in EAS. Verified that both profiles contain the physical iPhone being used for testing. Verified that both targets belong to Apple Team 26K9NDX728. Configured both the main app and widget extension to use the same distribution certificate. Created separate provisioning profiles for: com.sencard.mobile com.sencard.mobile.widgets Confirmed the App IDs still exist in the Developer portal. Confirmed the App Group exists and is assigned correctly. Confirmed the registered iPhone is present in the Developer portal. Rebuilt the app from scratch after regenerating all credentials. Confirmed that the EAS build succeeds. Reproduced the installation failure again on the physical device. Captured the iPhone system logs using idevicesyslog. Reproduced the problem with Xcode as well as EAS. Initially, before resetting the credentials, I also encountered a build-time error similar to: Provisioning profile ... doesn't include signing certificate "iPhone Distribution: ... (26K9NDX728)" I then deleted and regenerated the certificates/profiles and ensured both targets shared the same distribution certificate. That resolved the build failure — the application now builds successfully — but the resulting application is still rejected by iOS during installation with the REJECT_PROFILE / 0xe8008018 error above. What I’m trying to determine Is there some server-side state associated with my Apple Developer team/account that can cause a newly generated, apparently valid Ad Hoc provisioning profile to be returned as: REJECT_PROFILE by Apple’s online authorization service? Specifically: What causes online-auth-agent to return REJECT_PROFILE for a newly created provisioning profile? Can an Apple Developer team/account get into a state where newly generated Development/Ad Hoc profiles are rejected by device-side online authorization? Is there any additional server-side reset or validation Apple Developer Support can perform for Team ID 26K9NDX728? Is error -402620392 associated with a specific provisioning/profile authorization condition? Is there anything else I should inspect in the .mobileprovision file or code signature to determine exactly why Apple is rejecting it? Since I can reproduce this with both Xcode and EAS, is there any known issue affecting Ad Hoc/Development profile authorization rather than the build tooling itself? At this point I’m reluctant to keep generating new certificates and provisioning profiles because I’ve already done a complete signing reset and the newly generated profiles are still being rejected. Any guidance on what REJECT_PROFILE means internally, or what Apple Support should check on the Developer account/team, would be greatly appreciated.

I'm using Dynamic Font throughout my entire app yet the audits in Accessibility Inspector will give me a ton of "Dynamic Type font sizes are unsupported: User will not be able to change the font size of this SwiftUI.AccessibilityNode" warnings. This is incorrect because users are able to change the font size. I can even move to the inspector panel and adjust the font and see it all change right within the Accessibility Inspector. I assume this is a bug since I can change the font but I was also wondering if there's some special thing I'm missing that could prevent these warnings from appearing especially when management runs audits to look for deficiencies.

I'm trying to download the iOS 26.2 simulator, but it fails both in Xcode and via the command line. When I run: xcodebuild -downloadPlatform iOS -buildVersion 26.2 -exportPath ~/Downloads It returns: iOS 26.2 is not available for download. I would like to know: Why iOS 26.2 simulator cannot be downloaded at the moment. Whether iOS 26.2 simulator is still available, or if it has been removed or replaced. How to properly get and install the iOS 26.2 simulator. Any official explanation or solution would be greatly appreciated. Thank you!

I am a long time developer but have never incorporated an IAP into any of my work so this is very new to me. So to save time I have used some AI for coding, but the code is having an issue and I'm not sure whether it is in the code or in Xcode. Xcode 27 on macOS 27.0.1 for iOS 27.0.1. IAP is to unlock full access after a 14-day trial. DESCRIPTION OF PROBLEM In local Xcode StoreKit testing, Product.purchase() returns .pending (as expected, since "Ask to Buy" is enabled), and Xcode’s transaction manager continues to show “Pending Approval.” After closing and reopening the app’s purchase sheet, the same transaction appears as verified and non-revoked in Transaction.currentEntitlements and is delivered through Transaction.updates, giving full access to the app. This reproduces in a standalone UIKit test app (linked below). The source file in question is AppAccessManager.swift. The relevant functions are: AppAccessManager.purchaseProduct() Calls product.purchase(). Handles .pending by recording a request reminder and displaying feedback. AppAccessWindowViewController.viewDidLoad() Runs when the purchase-options sheet is opened. Calls manager.start() followed by manager.refreshAccessState(). This is the sheet-opening path associated with the unexpected transaction delivery. AppAccessManager.refreshAccessState() Iterates Transaction.currentEntitlements. A transaction still labeled “Pending Approval” in Xcode is returned here as verified and nonrevoked. AppAccessManager.startListeningForTransactionUpdates() and handleTransactionUpdate(_:) The same pending transaction is also delivered through this sequence as verified and nonrevoked. The handler applies access before calling transaction.finish(). AppAccessManager.applyVerifiedPurchase(_:) Applies verified transactions received from successful purchases or the listener. STEPS TO REPRODUCE https://avliscoding.com/storekittest.zip Launch app Select "Open Purchase Sheet" Start trial Quit app, enable "Ask to Buy" in StoreKit file configuration settings Restart app. Select Purchase (will give a pending message in response) Close sheet Reopen sheet The app now believes it has made that purchase even though the purchase is still "Pending" in Xcode.

Hello team, We are testing the Declared Age Range/Age Signal functionality in a TestFlight build and would appreciate guidance on the correct setup and testing process. Current Behavior Observed We are seeing inconsistent behavior between the Sandbox environment and the age-range results returned to the application. Scenario 1: Apple Account Signed In A regular Apple ID is signed in on the device. The TestFlight build is installed and launched. The application returns Verified Adult (18+). We then sign in to the Sandbox environment using a Sandbox Test Account and select a different test scenario (for example, a child/minor scenario). After relaunching the application, the age signal response still remains Verified Adult (18+). Scenario 2: Apple Account Signed Out We sign out of the Apple account from the device. As a result, TestFlight is also signed out. When the application is launched, the response changes to Unable to Verify. Even after changing Sandbox test scenarios (such as child, teen, or adult scenarios), the application continues to return Unable to Verify rather than the selected test case response. Based on this behavior, it appears that the application is not reflecting the scenario selected in the Sandbox environment. Questions What is the correct process for connecting an application to the Sandbox environment when testing Declared Age Range scenarios? Does the Apple ID used for TestFlight need to be associated with or match the Sandbox Test Account? Should the device remain signed in to a regular Apple ID while the Sandbox Test Account is used for testing? How does the app determine whether it should use the selected Sandbox scenario versus the signed-in Apple account? Are there any additional device settings, account requirements, or configuration steps required for Sandbox age-range testing? Is there a way to verify that the application is successfully connected to the Sandbox environment and consuming the selected test scenario? If the Sandbox scenario is configured correctly, should we expect the API response to change immediately when switching between child, teen, and adult test cases? At present, regardless of the Sandbox scenario selected, the application either continues to return Verified Adult (18+) or Unable to Verify, and we have been unable to validate the documented Sandbox test scenarios. Could you please provide guidance on the expected setup and testing workflow for TestFlight applications using the Declared Age Range feature? Thank you for your assistance.

Feedback Assistant report: FB25173765. I am investigating an iOS Simulator runtime verification failure on an Apple M1 Mac: macOS 27.0.1 (26A434) Xcode 27.1 RC (27A9275) CoreSimulator 1174.9.2 iOS 27.1 RC Simulator runtime, arm64, build 24A94232 The official download/export command completed successfully: xcodebuild -downloadPlatform iOS -exportPath <export-directory> -buildVersion 27.1 -architectureVariant arm64 It registered the runtime and produced a complete .exportedBundle, including ExportedMetadata.plist, BuildManifest.plist and the Cryptex support files. Xcode's required components are installed, and xcodebuild -checkFirstLaunchStatus returns 0. Updating macOS from 27.0 to 27.0.1 did not resolve the verification failure. xcrun simctl runtime list -j reports a Ready “Patchable Cryptex Disk Image” with signatureState Unknown. Running: xcrun simctl runtime verify <runtime-image-identifier> returns exit code 1 with: Signature verification failed: (-67054 a sealed resource is missing or invalid The registered iPhone Duo simulator has not been booted. No security protections, signing settings or quarantine attributes have been changed, and the existing runtime has not been forcibly removed. Xcode 26.4 release notes, issue 166834291, document secure import of the complete .exportedBundle with xcodebuild -importPlatform. I have not yet run that separate import. Is reimporting the complete bundle a supported recovery for this failure? Does the importer reuse an already registered identical build, and what additional or temporary internal disk space should be reserved? If a different recovery is appropriate, could Apple provide a supported procedure that retains signature and Cryptex validation? Also, is simctl runtime verify the appropriate validation for this runtime format? I have seen community reports involving the inner DMG, but have not assumed those are a confirmed fix or that their validation is equivalent. I would appreciate an official recommendation before proceeding.

I am unable to build to my Series 12 which is on watchOS 27.2 beta 2, I have macOS 27.2 beta 2 and Xcode 27.2 beta 2 but when I open up Device Hub, and click on my watch, it says Tunnel State("Connecting" then "Disconnected") and won't ever connect. the app im building is watchOS only and so iPhone is incompatible and I've tried restarting every device but nothing works.

When working with an Objective-C project in Xcode 26.5, I'm unable to establish outlet and action connections by dragging between XIB files and the corresponding .h header files. This drag-and-drop connection works perfectly after switching to Xcode 26.3.0. In addition, under Xcode 26.5, drag-and-drop linking works normally for projects using Swift files together with XIB files. The issue only occurs with Objective-C .h files and XIB files.

I've never had anything but trouble with xcappdata, but I got what I wanted working in the previous xcode version, I could specify the xcappdata in my testplan and it would work on the simulators. Now, on XCode 27, the xcappdata doesn't load. I look in the xcode 27 release notes and see there is indeed an issue with xcappdata, and a workaround. Workaround: To make a .xcappdata bundle for use in Xcode’s Run scheme action do the following. Add .xcappdata to the folder created by Device Hub when downloading app data containers. Inside that folder make a new folder named AppData. Move the other content in that folder into AppData. For example, com.example.MyApp/{Documents,Library,tmp} becomes: com.example.MyApp.xcappdata/AppData/{Documents,Library,tmp} This is completely unhelpful. When am I downloading app data containers? What folder is created by Device Hub? Where is it? How does this apply to my testplan? What if I have multiple xcappdata bundles for different test plans? It looks to me like this workaround would be part of a script where at some magic moment I inject my app data into a simulator. Which might not be too bad So if I wanted to build this script it I imagine it looks like create a simulator install the app on the simulator find the folder related to the simulator copy in my xcappdata? Then I can run my tests?

Hello. I have just updated to Xcode 27 to support this version, however... my app is a navigation app with CarPlay support... The I/O > External Displays option through the Simulator helps a lot when testing it, but I’ve noticed it is now gone Why? Who thought this was a good idea? Some of us support apps that are beyond a simple ToDo app So now I have to go back to the previous version of Xcode, or what?

How do we get distribution available on Apple HomeView is this iPhone or iPad in Supported Destinations? Thank you.

On Xcode 27 with macOS 27.0.1, I observed Xcode marking an existing project as locked because its file supposedly did not exist. The project used the traditional project.pbxproj format. That file existed, parsed successfully, was readable, and had no filesystem lock flags. Command-line builds succeeded, but the editor continued to show the lock warning. Selecting Unlock produced this error: The file “project.xcproj” could not be unlocked. Could not find the file. There was no project.xcproj in that PBX-format project. A separate minimal iOS project also reproduced the same missing-file lock warning. That sample contains one application target, a minimal Swift source file, and signing disabled. This reproduction suggests the warning is not specific to the main application's source or extensions. These observations were recorded on 10 October 2026. I have not retested the sample today. Apple Developer Technical Support directed me to post the issue here. Is this a known project-lock tracking issue involving the alternative project filenames? What supported diagnostic evidence would help establish why Xcode reports the project as locked, and is there a supported workaround that preserves the existing project format? A standalone reproduction was prepared during the investigation. I can arrange to share it after checking the files for public release.

I’m sharing my experience with an Apple Watch Ultra 2 and Xcode 27.0 in case it helps someone troubleshooting a similar problem. Developer Mode would switch on, restart the Watch, and ask me to confirm “Turn On.” Even after that confirmation, it would revert to off. Xcode detected my iPhone but not the actual Watch, and pairing remained at “Waiting to pair.” The changes that stood out in my case were removing a corporate management/configuration profile that required a complex passcode, changing the Watch to a simple passcode, and putting my Mac, iPhone, and Watch on the same private Wi-Fi network. I also temporarily disabled VPN, restarted both the iPhone and Watch, and enabled Developer Mode again. After these changes, the connection succeeded. I changed several things together, so I can’t identify which change was responsible or claim this is a universal fix. This confirms the connection in my case; installing and running an app on the Watch is still being verified. If your device is managed, consult your organization’s IT team before changing profiles or security settings. This is a report of what happened on my setup, not a recommendation to weaken passcodes or bypass organizational policy.

Heya! I'm preparing my apps for the iPhone Duo, but having a hard time with the Simulator for it. Basically it's very very slow, crashes often (not speaking about my app but the device hub tool freezes or crashes). Restarting it often helps to kinda "cleanup" when it starts feeling like deep mud when using it, but it would not make it smooth just less deep mud feeling. I am running it on an M1, so that would probably be a good reason for it going this slow. However, any tips to make it run better? Things, settings I can toggle on and off?

For simctl shipped with Xcode 27.0 build 27A266a, is there a supported way to deliver launch stdout/stderr directly to an in-memory consumer without first writing raw output to a regular file, then stop the collector within a bounded time without forwarding a signal to, blocking, terminating, restarting, or changing signal policy in the launched application? Please identify the documented interface and supported OS/runtime scope, or explicitly state that this combination is unsupported. Do stdout/stderr path options officially accept a FIFO or other nonpersistent sink, and where is that sink resolved? What open/create/truncate/blocking behavior and reader-before-writer order are guaranteed? Which process owns the output writer after launch returns? Does simctl exit or collector detach close, transfer, or leave that writer alive? At consumer byte/time limit, EOF, reader closure, collector failure, or backpressure, what happens to App writes and signals, including SIGPIPE/EPIPE? Is there a supported independent detach/drain mechanism that avoids App effects and indefinite background collection? Can the supported interface guarantee no raw-output file or replay spool before the consumer, and which documented limits can the consumer enforce without affecting App lifecycle? Please identify the supported interface, applicable tool/runtime versions, and documented lifecycle guarantees, or clarify which requirements are unsupported. This request is limited to the public tool interface contract and contains no application logs, source code, device identifiers, customer data, or diagnostic attachments.

xcstringstool compile (and by extension CompileXCStrings in Xcode/Bazel builds) hangs indefinitely on .xcstrings files where one or more keys have a localizations entry count that is a significant outlier relative to the rest of the file's keys — even when total file size and total entry count are unremarkable. The tool produces no error, warning, exception, or log output; it simply spins at high CPU with flat memory until killed.

I am working on adding an iOS app to my existing MacOS app. However Transporter shows them both identically. They have the same icon and the same major version number. Please add some clue as to the OS type of each delivered submission so I can tell them apart.

Tried three times now and absolutely cannot get Xcode 27 to install iOS 27 Simulators. I have done a complete uninstall of Xcode (including things in ~/Library). And even purged /System/Library/AssetsV2/com_apple_MobileAsset_iOSSimulatorRuntime/ When Xcode 27 (27A266a; release version) is installed and run the first time, I'm greeted with the SDK screen. I select iOS and it downloads that runtime. I can see it in Xcode's Components panel in Settings. I only see Any iOS Device as a target device in Xcode. If I launch Device Hub, it's empty and I cannot add any devices since the Add dialog shows No Runtimes Available. Selecting "Add Platforms in Xcode" takes me back to Xcode, but I only ever see iOS 26.5 or older in the list. I've even tried the various xcrun simctl commands, but to no avail. Why is it so difficult to have a clean install of Xcode 27, have it install the iOS 27 SDK and then be able to build and run existing projects? I'm on the release version of macOS 27.0.1 though the problems persisted earlier today on macOS 27.0 as well.

The iOS 17 simulator does not respond at all when I try to interact with it. The simulator is not frozen as I can still control appearance and launch apps via the right sidebar. Things like the home button and clicking on the screen simply don’t work. I am using Xcode 27 beta 6. Feedback ID: FB24674634

Hey all, the codex sign in isn't working for me in Agents. I am using the 26.5 release candidate version. It always says "Not Signed In". I have completed the Sign In process multiple times. Anyone else seeing this? I have filed Feedback FB22732574