xcode github

If you transfer an app that uses iCloud key-value store (NSUbiquitousKeyValueStore), the transferred app should use the orignal store identifier, which by default is the bundle ID prefixed with the orignal team ID, so it still has the access to the existing data. The orginal store identifier is embedded in the new provisioning profiles you create for the transferred app. What you need is to update your entitlements plist with the full KVS value in your provisioning profile. This is documented in in the “Apps using iCloud” section here. In your case, is 57AWJ345M2 the new team ID? Using the new team ID as the prefix of the key-value store will lose the access to the orginal store. I believe that's why Xcode gives you the error. Best, —— Ziqiao Chen  Worldwide Developer Relations.

Hello? #1 - I said I am not using XCode. Says so in the Subject. #2 - Your App Review Manager TOLD me voice in a webex meeting to post here in the forum to get an answer from an Apple Engineer! This is insane. You guys really seem to be struggling with this and providing a solution. I'm not using XCODE - I gave the exact situation above, I've been a developer for 35 years. My information above is enough for Apple engineer to give a solution.

watchOS 26.2.1 seems a worse pain than previous watchOS versions to copy cache over to Xcode 26.2 than before.

It sounds like you're aware of what a routing app is, but just to confirm details: A routing app provides navigational directions between two locations. It is enabled inside of an Xcode project by going to the Capabilities tab, and adding the Maps capability, which will then show you a list of checkboxes for the transportation modes by which you're able to provide navigational directions between points. Those checkboxes correspond to values added to your Info.plist file under a key named MKDirectionsApplicationSupportedModes. It sounds like you're not providing directions, but you should check to make sure the above capability isn't enabled accidentally. And if you're not providing directions, also don't enable this capability just to try and solve this error, as I've seen people get tangled up further by trying that. If all of that looks good and that capability wasn't accidentally enabled, then the next thing you should do is to open a bug report with the details of your App ID and the build number

Ok, so just to make things clear, is it expected that whenever I want to change the SpriteKit scene and also avoid concurrently accessing objects that may be changed in the current thread, I have to queue the SpriteKit changes by capturing all the needed state? It's just surprising to me that this is needed when SpriteKit is used as an overlay in SceneKit, but when running SpriteKit alone, it doesn't seem to be needed. I filed at least one feedback recently about crashes happening only when SpriteKit is used as SCNView.overlaySKScene. Is it expected that one has to use this... boilerplate code when embedded in SceneKit? Couldn't one do without it by simply overlaying a SkView on top of SCNView? class SceneController { private var shapeNode: SKShapeNode! func main() { let shapePath = CGPath(rect: CGRect(x: 0, y: 0, width: 10, height: 10), transform: nil) GameViewController.shared.updateSpriteKit { [shapeNode, shapePath] in shapeNode!.path = shapePath shapeNode!.fillColor = .systemRed } } } cl

Consider the tiny test program at the end of this post. For context, https://apple.com redirects to https://www.apple.com, so this exercises the redirect case. When I run it on my Mac (Xcode 26.2 on macOS 26.2) I see this: will run task will redirect did run task, status: 200, downloaded: file:///…/CFNetworkDownload_WvKFij.tmp That is, it fetches apple.com, which redirects to www.apple.com, that’s reported to the delegate, and then it continues the download. IMPORTANT This uses a standard session. If you’re using a background session, the system doesn’t call this delegate method. We even mention that in the docs (-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com import Foundation final class Delegate: NSObject, URLSessionDownloadDelegate { func urlSession(_ session: URLSession, task: URLSessionTask, willPerformHTTPRedirection response: HTTPURLResponse, newRequest request: URLRequest) async -> URLRequest? { print(will redirect) r

What's the issue ? That's a method that creates and returns a cell view. It gets called frequently and not by you. It's not an appropriate place to set a tableview property that you only need to set once, when you want it set. I change my mind to stay consistent with system behaviour and will change the color of the text (to white) when selected, to make it more readable. What if the user's in dark mode? I checked some code where I was doing this. What I'm doing is subclassing the row view and overriding this method: // Customize selection. override func drawSelection(in dirtyRect: NSRect) { if self.selectionHighlightStyle != .none { let frameColor = NSColor.selectedContentBackgroundColor NSGraphicsContext.current?.saveGraphicsState() frameColor.setStroke() let rect = CGRect( x: box.frame.minX + 5, y: box.frame.minY + 4, width: box.frame.width - 10, height: box.frame.height - 10) let roundRect = NSBezierPath(roundedRect: rect, xRadius: 4, yRadius: 4) roundRect.lineWidth = 4 roundRect.stroke(

Ok thank you. And I don't have to have the in app purchase capability to make in app purchases work? If you use the iMessage App template to create the app and extension, there is nothing to do. The template doesn't allow you to add the In-App Purchase capability to both the app and capability. If you use another Xcode template that allows you to create your app and add the In-App Purchase capability, remove the capability if you added it. So do I need to embed my iMessage extension inside the imessage app container? If you use the iMessage App template, the extension is automatically embedded into the containing app. If you use the iMessage extension template to create the extension, Xcode automatically adds it to the app selected in the Embed in Application field.

First off, a clarification here: I am attempting to write a bridging driver for an older UPS that only communicates via RPC-over-USB rather than the HID Power Device class the OS requires. What's your final goal here? That is, are you: Trying to create a seamless bridge to HID and then relying on the system’s support. OR Direct communication via user client to your own app. In the first case, how seamless do you actually want this to be? Do you not want any app at all? The issue here is that you don't actually need to use DriverKit to talk to a USB device. You could also use the USBHost framework, which would let your app just talk to the device. Unless you're specifically bridging to HID, then I wouldn't use DriverKit at all. In addition, if you're planning to bridge to HID but you're also planning to have an app/daemon, then you could also do this by using the USBHost framework to communicate with your device and a virtual HID device to expose that device to the system. The right choice here really depends

@hieronim-bosch AppKit is my favorite framework, nothing else comes close. Until proven otherwise there is still no better way to make a Mac app IMHO. That said I never got into Storyboards on Mac. In Xcode 26.2 I can still create an AppKit project the old way which is New Project -> macOS -> App then change Interface to XIB then you get a project without a storyboard. If you want to go completely without Interface Builder you can but I don't think Apple ever had a template for that setup (well if they did I never noticed or it must have been a really long time ago). You can set the NSApplication delegate in main. #import @interface AppDelegate : NSObject @property (strong) NSWindowController *mainWindowController; @end @implementation AppDelegate -(void)applicationDidFinishLaunching:(NSNotification*)aNotification { NSLog(@Hello world!); NSWindow *firstWindow = [[NSWindow alloc]initWithContentRect:NSMakeRect(50.0, 50.0, 400.0, 400.0) styleMask:NSWindowStyleMaskTitled backing:NSBackingStoreBu

@AET720 I then began by using the iMessage App template in xCode. And BAM right off the bat, I could not get the In-App Purchases capability to show up when I select my iMessage extension target. When you add the In-App Purchase capability to a target in Xcode, it adds the com.apple.developer.storekit entitlement string. This entitlement isn't a supported entitlement as explained in Determining if an entitlement is real. For a list of entitlements Apple supports, see Capabilities overview > Supported capabilities. if you added the In-App Purchase capability to your app target in Xcode, remove it. It is unnecessary. This capability is already enabled when you use an explicit App ID. If your iMessage extension uses an App ID, In-App Purchase is already enabled.

FYI, things work better if you just reply to the thread instead of using comments. Honestly, the comment feature doesn’t really work. First, let me start with the error messages you posted: Thank you. Yesterday, I accidentally removed arm64e from the compilation architecture and kept only x86_64 and arm64 architectures. The problem of Domain=NSPOSIXErrorDomain Code=8 Exec format error was solved. One thing you need to be careful about when looking at our log messages is focusing too much on the EXACT error code/detail instead of the overall flow. Looking at this message as an example: KernelManagerd: Error Domain=NSPOSIXErrorDomain Code=8 Exec format error This format structure: Error Domain= Code= ...is a common structure used by NSError to describe error codes from lower level subsystems. In this case, it's saying this was a POSIX error code, meaning error code 8 from the ERRNO range, or ENOEXEC. The string Exec format error is actually the generic POSIX error string description returned by perror(). All