Hi, I am reaching out to seek assistance with a persistent code signing issue that is preventing our team from installing our iOS app, Scoopz (https://apps.apple.com/us/app/scoopz-real-life-real-video/id6449206831) on physical devices. We suspect there may be an issue with our Apple Developer account, as we have exhausted all standard troubleshooting steps without success. Below, I’ve provided details about the issue, the error logs, and the steps we’ve taken. Issue Description: When attempting to install the app on an iPhone using Xcode, we encounter the following error: Unable to Install “Scoopz: Debug” Domain: IXUserPresentableErrorDomain Code: 14 Recovery Suggestion: Failed to verify code signature of /[REDACTED_PATH]/OurApp.app : 0xe8008018 (The identity used to sign the executable is no longer valid.) The app builds successfully to the iOS Simulator and can be released to the App Store without issues, but it fails to debug on physical devices. Steps Taken: Our team has attempted the following t
Search results for
Xcode
92,321 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
We have encountered a consistent problem with OTP (One Time Password) autofill on iOS versions 26.0.1 through 26.3. The issue pertains to apps implementing OTP input using multiple UITextFields (often 6 or 7 separate text boxes for each digit). Problem Details: When tapping the OTP autofill suggestion from Messages or supported third-party apps, iOS autofill pastes the entire OTP string into just one UITextField (commonly the second or focused field) rather than distributing digits across the individual text fields. The delegated UITextField methods such as textField:shouldChangeCharactersInRange:replacementString: receive an entire OTP string at once, but the usual event handlers like UIControlEventEditingChanged do not always trigger, breaking existing logic relying on those. This results in the OTP input UI showing incorrect or partial OTP, confusing users and forcing manual re-entry. Many popular apps employing multi-field OTP input UIs face similar autofill malfunctions on iOS 26.x, impacting us
The Declared Age Range APIs are available in iOS 26 or later. The iOS 26 SDK requires Xcode 26 or later as shown in Xcode Releases. Testing age assurance in the sandbox requires a device running iOS 26.2 beta or iPadOS 26.2 beta, and Xcode 26.2 beta 2.
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
Is Xcode 26 required for DeclaredAgeRange APIs? We ask because there appears to be a serious legal deadline on January 1, 2026 and if Xcode 26 is required to meet this deadline, it's about to be a huge burden for us to upgrade to it over the holidays. Our app does support teenagers.
from my understand, yes, Xcode 26 is required, it's a bit unfortunate if it's a huge burden to upgrade. some APIs need Xcode 26.2 https://developer.apple.com/documentation/permissionkit/askcenter
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
Hello, When using ASWebAuthenticationSession with an HTTPS callback URL (Universal Link), I receive the following error: Authorization error: The operation couldn't be completed. Application with identifier jp.xxxx.yyyy.dev is not associated with domain xxxx-example.go.link. Using HTTPS callbacks requires Associated Domains using the webcredentials service type for xxxx-example.go.link. I checked Apple’s official documentation but couldn’t find any clear statement that webcredentials is required when using HTTPS callbacks in ASWebAuthenticationSession. What I’d like to confirm: Is webcredentials officially required when using HTTPS as a callback URL with ASWebAuthenticationSession? If so, is there any official documentation or technical note that states this requirement? Environment iOS 18.6.2 Xcode 16.4 Any clarification or official references would be greatly appreciated. Thank you.
Topic:
Privacy & Security
SubTopic:
General
Tags:
iOS
Security
Authentication Services
Universal Links
Returning to a Mac Catalyst app that I put to the side for awhile..when running it on Xcode 26.1 it crashes at launch with: Assertion failure in -[NSToolbarItemGroupView _layoutWrapperViewsWithAttributes:], NSToolbarItemGroupView.m:599 No attributes were found for item Call stack has a bunch of Autolayout code in AppKit like: [NSWindow(NSConstraintBasedLayoutInternal) _layoutViewTree] + 120 50 AppKit 0x00000001911e8a10 -[NSWindow(NSConstraintBasedLayoutInternal) layoutIfNeeded] + 240 51 UIKitMacHelper 0x00000001a98f293c -[UINSWindow layoutIfNeeded] + 56 A few unnamed symbols mixed in maybe that's that Swiftness beneath the surface. App is just murdered on launch. I assume this is related to using NSToolbarItemGroup when building an NSToolbar... I do see this log out: NSToolbarItemGroup does not support selectionMode. Create the group with one of the class constructors to support selection. Which is an interesting log so I commented out all calls to setSelectionMode: but still the same crash. I do set
Summary I’m experiencing two issues with SwiftUI’s navigationTransition(.zoom) on iOS 26.0 and 26.1 that break previously smooth transitions. These issues appear both on real devices and Simulator. The same code works correctly on iOS 18. Issue 1 - Source View Disappears After Drag-Dismiss When using .navigationTransition(.zoom(sourceID:..., in:...)), the source view disappears completely after the transition finishes. This only happens when the detail view is dismissed via drag (interactive dismiss). When the view is dismissed by tapping the back button, the source view remains visible as expected. Reproduced on: iOS 26.0, iOS 26.0.1 (17A400), iOS 26.1 (Simulator + physical device) Issue 2 — Flickering and Geometry Mismatch During Transition Compared to iOS 18 behavior, the outgoing view and incoming view no longer share consistent geometry. Current behavior on iOS 26: The disappearing view flickers during the drag-dismiss interaction. The source and destination views no longer align geometrically. Instead o
Topic:
UI Frameworks
SubTopic:
SwiftUI
I'm running into an issue where my application will hang when switching tabs. The issue only seems to occur when I include a Swift Chart in a navigation label. The application does not hang If I replace the chart with a text field. This appears to only hang when running on macOS 26. When running on iOS (simulator) or visionOS (simulator, on-device) I do not observe a hang. The same code does not hang on macOS 15. Has any one seen this behavior? The use case is that my root view is a TabView where the first tab is a summary of events that have occurred. This summary is embedded in a NavigationStack and has a graph of events over the last week. I want the user to be able to click that graph to get additional information regarding the events (ie: a detail page or break down of events). Initially, the summary view loads fine and displays appropriately. However, when I switch to a different tab, the application will hang when I switch back to the summary view tab. In Xcode I see the following mes
Same here, xcresulttool from Xcode 26.0.1 is working, from Xcode 26.1 it's terminating, Xcode 26.2 Beta 2 is terminating too unfortunately.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
I’m experiencing an issue after building the project with Xcode 26.1.1. In my code, I have a UICollectionView that contains multiple cells, and each cell has a slider. When I move a slider in one cell, sliders in other cells also move. This issue does not occur in Xcode 16.4 – it works perfectly there. If anyone has a solution or knows if this is related to Xcode 26 changes, please let me know. Thanks!
Thanks for the post. Do you get the same results with just the relevant code in a small test project? Would be great to be able to see the issue and test it in Xcode 16.4 and Xcode 26.0 as well as the new beta Xcode. Have you tried the newest Xcode in beta? If so, please share a link to your test project. That'll help us better understand what's going on. 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:
UIKit
Tags:
I'm having this issue as well on Xcode 26.1 (17B55) and macOS 26.1 (25B78). My last successful run for this app was on the same environment on the 13th November, 2025. Xcode 26.1.1 (17B100) also has this same issue.
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
Tags:
More Context: Xcode 26.1.1 New standalone watchOS project - default settings. There is a project with two targets - an iOS target and a watchOS target. The iOS target is at default - no code added or taken away all certificates and profiles point to my distribution certificate and provisioning. The bundle_id's seem good. The Project and ios share a bundle id of com.myteam.myapp The watchOS bundle id is com.myteam.myapp.watchkitapp There are identifiers for both in App Store Connect. The app compiles and runs on the simulator with no errors, all sizes, all languages. I do not have a watch connected to the account, but the code has been tested and I can't imagine that the lack of a physical device is causing the problem The scheme has the 3 archs in top to botton project, ios, watchOS - all marked to do everything they can and everything I see is marked to release. This is my first swift program and xcode experience, so I am confident that the error is my understanding of the workflow. thank y
Topic:
Developer Tools & Services
SubTopic:
Xcode
Hello I have developed a standalone app for watchOS - trying my best to use best practices and floowing the (limited)documentation. But here I am, unable to distribute - or even Validate - my apps archive in Xcode. As far as I can tell, bundle_id's are correct. It has an iOS wrapper (set up by New Project), Skip install has been tried in every combination. I'm at a loss. I'm sure there is some simple setting or workflow that I am missing, but I've been at it for days. Yes. Days. Has anyone recently created and successfully distributed a standalone watch app that could help me troubleshoot? I would be extremely appreciative. My kids would too. They miss their dad (just one 5 more minutes, I think I got it!)(I didn't get it) Thank you bob
Topic:
Developer Tools & Services
SubTopic:
Xcode