“xcode github”

Thank you for your post. While I do not have an answer for you, I would recommend formatting the code in a way that is easily copyable and readable, such as using code block formatting like, but make sure to provide character returns as well, if you copy from Xcode will look way nicer. nt CDib_ARGB::Load(LPCSTR pFilename) { int rc = 0; if (NULL == m_pRaw_vImage_Buffer) { NSString *pNS_filename = [[NSString alloc]initWithUTF8String:pFilename]; NSImage *pNSImage = [[NSImage alloc] initWithContentsOfFile:pNS_filename]; if (nil == pNSImage) rc = -1; else { int width = pNSImage.size.width; int height = pNSImage.size.height; if (pNSImage.representations) { NSImageRep *imageRep; int jj; width = 0; height = 0; for (jj = 0; jj < pNSImage.representations.count; jj++) { imageRep = pNSImage.representations[jj]; if (imageRep.pixelsWide > width) width = imageRep.pixelsWide; if (imageRep.pixelsHigh > height) height = imageRep.pixelsHigh; } } NSSize imageSize = NSMakeSize(width, height); NSRect imageRect =

Thanks for your post and description. Although I am not an expert in watchOS, I would like to inform you that the bug is present in the latest version of the operating system. However, I was unable to reproduce the issue on a real device. I attempted to reproduce the issue on a read device, but it did not work. I then restarted the device on the simulator, restarted the simulator, and ran the project using Xcode 26.2 and 26.3 beta with different simulators. Hopefully someone with better experience in watchOS can jump into this thread to also try your focused simple project on the bug. I just wanted to make sure to let you know we got the bug and the team has been working on that, but a better workflow how to reproduce into the bug will help. For more details on when you'll see updates to your report, please see What to expect after submission. Albert Pascual
  Worldwide Developer Relations.

Thank you for sharing the post and the partial code. I suggest posting the code starting from the Toolbar instead of providing only a ToolbarItem. Hope other SwiftUI gurus here can jump into this thread as my SwiftUI skills are not as good as others for sure!! Looking at your item it seems like you are setting the frame to 20x20? I think by default in SwiftUI only registers taps within the bounds of its content. Taps on the surrounding padding or button area are ignored. To ensure taps anywhere within the trigger the action, we can use a to expand the tappable area, see your frame? The modifier ensures that taps anywhere within the defined shape are recognized. // Removing the Toolbar too :-) ToolbarItem(placement: .navigationBarTrailing) { // guessing on toggleBookmark :-) Button(action: toggleBookmark) { ZStack { Circle() .foregroundColor(.clear) .frame(width: 54, height: 54) // Adjust size as needed Image(systemName: isBookmarked ? bookmark.fill : bookmark) .resizable() .aspectRatio(contentMode: .fit) .fra

Thanks @DTS Engineer, I have already read that documentation. You advised that I should enable all the settings. However, I noticed that for Memory Tag Pure Data, the description states that “it may incur a performance overhead”. I am therefore inclined not to enable it. Regarding Enable Soft Mode for Memory Tagging, the description states that “memory tagging faults will not crash and will be logged instead”. I am inclined to leave this disabled, as I would prefer the application to crash so that I can receive a crash report and potentially fix the issue. I am not entirely sure what is meant by logging in this context, would this appear in the Xcode console when running in Debug mode? As you are knowledgeable about AppKit and Mac computers, may I ask if you would mind looking at my other post about StoreKit 2? I am at my wits’ end, as I would like to ship the Cocoa app using the API but cannot because it is not behaving as expected. I am tempted to submit a code-level support request for this.

Albert, thanks for the reply. Remote hosted Live Activities I believe is a iOS 26.x system feature → No developer adoption. My steps: Preparation: Make sure iPhone and Mac (and/or Watch) are signed in with the same AppleID New iOS Project New Widget target, using standard template (In the new target UI also check that you want the live activity) Build and run to a physical iPhone Notice Live Activity exists on iPhone, Mac and Apple Watch [Example: From macOS, iOS Live Activity appears] In this case, I haven't built for any other platforms at all. I believe this is a feature, but I'm attempting to understand what I need to do to make it stop showing up in places that don't make sense for this app. Just made a simple project using the Xcode templates provided, then start the live activity on app launch. https://github.com/ioloro/LiveActivityWillTravel Thanks, John Marc

[quote='876494022, ellinj, /thread/815390?answerId=876494022#876494022, /profile/ellinj'] Is there any Keychain support for non-X.509 certificate formats? [/quote] No. Or, more specifically, the keychain only supports X.509 for kSecClassCertificate items. That doesn’t stop you storing the raw data as kSecClassGenericPassword. As to what you should do, that depends on how you’re using the word “certificate”: Apple uses [1] certificate to refer to the signed wrapper around the public key. We then use digital identity to refer to the combination of a certificate and the private key that matches the public key in that certificate. See TN3161 Inside Code Signing: Certificates for more on this. However, it’s common for folks to use a single term, certificate, to refer to both the certificate and digital identity, with ‘hilarious’ confusion being the result. So, if you’re using certificate ‘correctly’ then the certificate contains just the public key and you can store it wherever you want

[quote='876460022, jamie_sq, /thread/805609?answerId=876460022#876460022, /profile/jamie_sq'] If it's possible to provide positive confirmation [/quote] Yep. My reading of FB20884404 is that we identified the underlying issue and rolled that fix into Xcode 26.4b1. You should’ve also been notified of the fix in Feedback Assistant. [quote='876460022, jamie_sq, /thread/805609?answerId=876460022#876460022, /profile/jamie_sq'] thanks to whoever worked on this! [/quote] I’ll pass that along. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

You can find your answer on the submission form. You select your runtime environment using a popup, and below that popup is this text: Xcode app playgrounds are run in Simulator. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[Different DTS engineer here; I’m picking up this thread because it’s directly aligned with my area of expertise.] [quote='876554022, Tenjikato, /thread/815899?answerId=876554022#876554022, /profile/Tenjikato'] it does not appear in Xcode Organizer. [/quote] Right. The issue here is that you have a third-party crash reporter installed and it’s failing to preserve the Apple crash report. Let’s look at the backtrace in your first post: Crashed: com.apple.main-thread 0 KSCrash … ksmemory_notifyUnhandledFatalSignal + 12 1 KSCrash … handleSignal + 100 2 libsystem_platform.dylib … _sigtramp + 56 3 libsystem_kernel.dylib … mach_msg2_internal + 76 4 libsystem_kernel.dylib … mach_msg_overwrite + 428 5 libsystem_kernel.dylib … mach_msg + 24 6 CoreFoundation … __CFRunLoopServiceMachPort + 160 7 CoreFoundation … __CFRunLoopRun + 1188 8 CoreFoundation … _CFRunLoopRunSpecificWithOptions + 532 9 GraphicsServices … GSEventRunModal + 120 10 UIKitCore … -[UIApplication _run] + 792 Frames 10 through 3 are all standard