xcode github

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

Hi everyone, After updating my Mac and Xcode to 26, I’m running into a consistent crash whenever I try to launch an app from Xcode. Environment: Mac: Apple Silicon M3 macOS: 26.0 (25A354) Xcode: 26.0.1 (17A400) Issue: When I press Run on any project (including new, empty projects), Xcode immediately crashes. This started only after updating to the latest macOS and Xcode. Crash details: The crash log shows: Application Specific Signatures: ___localError Thread 0 crashed inside -[IDEScheme _executionOperationForSchemeOperationParameters:...] from IDEFoundation/IDEKit. I also noticed background threads calling DVTPortal (developer portal requests) right before the crash. What I’ve tried so far: Cleared DerivedData, ModuleCache.noindex, and Xcode caches. Signed out/in of my Apple ID in Xcode. Recreated project schemes. Verified provisioning profiles. Reinstalled Xcode 26. Unfortunately, the crash still happens. Question: Is this a known issue

iOS BGProcessingTask + Background Upload Not Executing Reliably on TestFlight (Works in Debug) Description: We are facing an issue with BGTaskScheduler and BGProcessingTask when trying to perform a background audio-upload flow on iOS. The behavior is inconsistent between Debug builds and TestFlight (Release) builds. Summary of the Problem Our application records long audio files (up to 1 hour) and triggers a background upload using: BGTaskScheduler BGProcessingTaskRequest Background URLSession (background with identifier) URLSession background upload task + AppDelegate.handleEventsForBackgroundURLSession In Debug mode (Xcode → Run on device), everything works as expected: BGProcessingTask executes handleEventsForBackgroundURLSession fires Background URLSession continues uploads reliably Long audio files successfully upload even when the app is in background or terminated However, in TestFlight / Release mode, the system does not reliably launch the BGProcessingTask or Background URLSession events. Te

I’m developing a Safari App Extension and I want to debug the background.js script. However, I can’t find any tool or option to do this. When I run the extension from Xcode using the ProjectName Extension (macOS) scheme, I expect to see a “ProjectName” item under the Develop → Web Extension Background Content menu. But there’s nothing there. Has anyone encountered the same issue? How did you fix it? Environment: Manifest Version: V3 Safari: 26.0.1 (21622.1.22.11.15) Xcode: 26.0.1 (17A400)

Hello everyone, I’m currently experiencing an issue where no subscriptions appear in my app when fetching products from StoreKit via react-native-iap. I would like to confirm whether this is related to my App Store Connect setup or a possible StoreKit limitation. Context My app uses react-native-iap and successfully initializes the StoreKit connection with: await RNIap.initConnection(); const items = await RNIap.fetchProducts({ skus: productIds, type: 'subs', }); productIds contains valid identifiers matching those configured in App Store Connect. The API /plan dynamically returns the correct product IDs. The fetch call completes successfully, but returns an empty array ([]). What I have already done Confirmed all subscription products exist and are correctly linked to the same app bundle ID. All subscriptions are currently in “Waiting for Review” status in App Store Connect. Verified that StoreKit connection is initialized correctly (RNIap.initConnection() returns successfully). Tested on a real device (iPho

The release prompt for xcode 26 is displayed, while other prompts are not

90714: Invalid binary. The app contains one or more corrupted binaries. Please rebuild the app and resubmit. Xcode Version 16.4 (16F6), minimum operating system iOS 17.6. 按照给出的终端命令，执行之后给出如下输出。但是我并不知道该如何进行下一步操作，代码中全局搜索也没有搜到类似@interface AUChangeSkinShell的代码或者framework，烦请您指导。 According to the given terminal command, the following output is given after execution. But I don't know how to proceed with the next steps regarding this information, We did not find any code or framework similar to '@ interface AUChangeSkinShell' in the global search of the code. Please guide us. % xcrun dyld_info -objc /Library/Developer/Xcode/Playload/EBCampus-ios.app/EBCampus-ios | grep (null) @interface AUUtils : (null) @interface (null) : (null) ... ... @interface (null) : (null) @interface (null) : (null) @interface AUChangeSkinShell : (null) @interface SSPBaseFormatMethod : (null)

When a subclass of UIInputView is created programmatically, a memory leak occurs. This issue can be easily reproduced even with a very simple sample project, so I’m submitting this report along with a minimal reproducible example. When a custom view subclassing UIInputView is instantiated in code, _InputViewContent retains the custom view, and the custom view also holds a reference back to _InputViewContent, creating a strong reference cycle that prevents deallocation. The issue consistently occurs and has been confirmed on Xcode 16.4, 26.0, and 26.1. As a workaround, initializing the view via Storyboard allows it to be properly deallocated from memory. (Please refer to the CustomInputView in the attached sample code.) import UIKit final class LeakInputView: UIInputView { deinit { print(LeakInputView deinit) // not called } } final class CustomInputView: UIInputView { required init?(coder aDecoder: NSCoder) { super.init(coder: aDecoder) } override init(frame: CGRect, inputViewStyle: UIInputView.Style