Search results for

Xcode

92,319 results found

Post

Replies

Boosts

Views

Activity

When xcode is tried again, it always fails to install the app
When xcode is installed on a mobile phone, the first run always fails. The second run usually works normally.The certificate signatures have been checked and all are normal。This problem will also occur if you stop the running xcode and then run it again。please help me. Mac mini:Apple M2 Pro mas os 15.2 (24C101) Xcode: Version 16.2 (16C5032a) The first failed print is as follows: 无法安装“xxx” Domain: IXUserPresentableErrorDomain Code: 14 Recovery Suggestion: Failed to verify code signature of /var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.uRA3Gt/extracted/Payload/xxx.app : 0xe8008001 (An unknown error has occurred.) User Info: { DVTErrorCreationDateKey = 2025-11-20 02:50:17 +0000; IDERunOperationFailingWorker = IDEInstallCoreDeviceWorker; } Failed to install the app on the device. Domain: com.apple.dt.CoreDeviceError Code: 3002 User Info: { NSURL = file:///Users/shenchunxing/Library/Developer/Xcode/DerivedData/VideoGo-dwhfrhswidapcydbmfuamplrtvso/Build/Prod
1
0
109
Nov ’25
OTP AutoFill Not Working Properly on iOS 26.x in Multi-TextField OTP Input Scenarios
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
1
0
129
Nov ’25
Xcode Cloud, Bitbucket
Hello, While setting up Xcode Cloud using Bitbucket, I encountered an issue with Source Control and providing access to the repository. The problem most likely stems from the fact that Bitbucket has updated its policy, and the use of app passwords is no longer available (at least for new ones). However, in Xcode → Settings → Source Control, the login flow still requires an app password, which makes it impossible to authenticate using the new API tokens. Attempting to authenticate via SSH also does not resolve the issue. After connecting to GitHub, I also tried to connect through the web version, but I'm getting the same message: Bitbucket Cloud installation was incomplete. I received this same message when I first tried to connect through Xcode. This problem does not occur when connecting to GitHub. I would appreciate receiving feedback from the Apple team on this issue. System Info: Xcode: 16.2 (latest from App Store) macOS: Sequoia 15.1
1
0
138
Nov ’25
Game Center leaderboards not posting scores
My app is live but the leaderboards still aren’t updating. App was built with unreal engine 5 with blueprints. I have the leaderboard stat info entered into the node for write integer to leaderboard and a node for show platform specific leaderboard. The leaderboards are shown as live on app connect. When I run the app, the Game Center login functions and the leaderboard interface launches as expected but it just lists a group of friends to invite. There are no scores listed and it says number of players 0 even though I have scored on two different devices and accounts. I have the Game Center entitlement added in Xcode. Not sure where else to look.
0
0
611
Nov ’25
Mac Catalyst Crash on App Launch on macOS 26.1: Assertion failure in -[NSToolbarItemGroupView _layoutWrapperViewsWithAttributes:], NSToolbarItemGroupView.m:599
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
4
0
181
Nov ’25
Reply to Xcode 26.1.1 related issue.
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:
Nov ’25
Reply to Standalone Watch App Woes
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
Nov ’25
Reply to WatchOS version lower than deployment target in Xcode 26
Thanks for verifying this on your side. Please find the answers to your queries. iOS’s Apple Watch version:
The paired Apple Watch is running watchOS 10.6.1 on a physical device. It is paired with an iPhone running iOS 18.x. Regarding the minimum deployment target: 
You are correct that the watch app’s minimum deployment target is set to watchOS 10.0, 9.6 was typo error.
The issue I am reporting is that Xcode still displays the error “watchOS version lower than deployment target” even though the physical Apple Watch is running 10.6. This should satisfy the 10.0 deployment requirement, but Xcode continues to block installation. So we are observing the unexpected behaviour with the below configuration : Physical device: watchOS 10.6 Deployment target: watchOS 10.0 Xcode error: “watchOS version lower than deployment target” The error should not appear. Additionally, I’m still seeing the same issue even on the latest environment: Xcode 26.1.1 macOS 15.6 I performed a clean buil
Topic: UI Frameworks SubTopic: UIKit Tags:
Nov ’25
Reply to Xcode 26 Crashes on Launching App After macOS + Xcode Update (M3 Mac)
I update to the latest Xcode : Version 26.1.1 (17B100) Toolchain: Swift 6.2 Release 2025-09-11 (a) and MacOS to the latest : 26.1 (25B78) and still have the same crash problem, I give the crash report to an AI to summarize it : Primary Issue Assertion Failure in Scheme Execution: The crash occurred during scheme execution operations, specifically when Xcode was trying to create an execution operation for running a scheme. Key Technical Details Crash Location Thread 0 (main thread) crashed with SIGABRT (Abort trap: 6) Trigger: Assertion failure in IDEScheme class Specific Method: -[IDEScheme _executionOperationForSchemeOperationParameters:build:onlyBuild:buildParameters:title:buildLog:dontActuallyRunCommands:restorePersistedBuildResults:deviceAvailableChecker:error:actionCallbackBlock:] Crash Sequence Assertion triggered in IDEScheme operations Assertion handler called abort() Main thread terminated with abort signal The crash appears to be an internal Xcode assertion triggered by in
Nov ’25