“xcode github”

[quote='876600022, anosidium, /thread/815819?answerId=876600022#876600022, /profile/anosidium'] You advised that I should enable all the settings. [/quote] Well, yes, if you read that one sentence in isolation. However, I made it clear that one specific setting, Enable Soft Mode for Memory Tagging, reduces security, so if you goal is security then enabling that is probably not a good choice (-: [quote='876600022, anosidium, /thread/815819?answerId=876600022#876600022, /profile/anosidium'] I am therefore inclined not to enable it. [/quote] Or you could profile your app and see if it makes a difference in pratice. That’s generally the best way to approach performance trade-offs. [quote='876600022, anosidium, /thread/815819?answerId=876600022#876600022, /profile/anosidium'] I am not entirely sure what is meant by logging in [Soft Mode] [/quote] Quoting Enabling enhanced security for your app: This entitlement makes hardware memory tagging operate in soft mode, where the system produces a simulated crash instead

There isn’t a specific affordance for renewing certificates. Rather, you simply create a new one. That’s the same for all our code-signing certificate types. For Developer ID I generally do this using the Developer website rather than Xcode. That’s because Developer ID certificates are precious, as I explain in The Care and Feeding of Developer ID. When you create a certificate using the website, you supply a certificate signing request (CSR). This includes the public key that’ll be embedded in the certificate, the one that matches your private key so that, when the website issues your certificate, the certificate and the private key form a code-signing identity. That gives you two choices: You can create a new CSR, containing the public key from a newly generated key pair. You can reuse the CSR you used previously. Note From a certain perspective, you could interpret the first option as ‘creating a new certificate’ and the second option as ‘renewing a certificate’, but that’s a bit of a stretch. I p

Thank you for doing some testing. That is great. I am a little confused though. I uploaded the image file earlier on the thread. I have reuploaded for this reply. Its name is PXL_20251217_201630453.MP.jpeg . Note also that the sample code contained the line: format.bitmapInfo = kCGImageAlphaFirst | kCGBitmapByteOrderDefault;//ARGB8888 That is slightly different than what you tried. Note also that my code did not crash. vImageBuffer_InitWithCGImage returned with the error code kvImageInvalidParameter. A complete project to reproduce the error has been uploaded as a zip archive via Feedback Assistant. Feedback Assistant designates the report as FB21893783 . The jpeg file is also in the zip archive. Xcode debug console: -[MoeDocController openDocumentWithContentsOfURL:display:completionHandler:] file:///Users/elliotleonard/test/PXL_20251217_201630453.MP.jpeg fence tx observer 1f8eb timed out after 0.600000 <<<< CMPhotoJFIFUtilities >>>> signalled err=-17102 at <>:1776 <&

Update xcode for macOS 26, and it fixed the problem.

Hi @Duynguyentan, You wrote: After configuring this key, the issue still persists with the same logs. PNO also reported that they still do not receive any calls from Apple services for the eligibility check step. Could you please help us check this? The response error associated with the logs provided in FB21945664 are different from the previous errors found in FB21352672. Since the PNO is not receive any Apple Pay requests, they should use the metadata provided to you within FB21945664 to investigate further. If needed, they can submit their own code-level support request so I can investigate. Thank you for your patience so far. Cheers, Paris X Pinkney |  WWDR | DTS Engineer

I have a small external app that puts up a modal dlog on receipt of the openDocuments event. I created a fake job in the big app that sends all the events, and had it send an kAEOpenDocuments to the small app, using kAEWaitReply so it will just sit there until the small app dismisses the modal dlog. I then ran a normal job that hammers InDesign with thousands of scripts. I got this in the Xcode log of the big app: AddInstanceForFactory: No factory registered for id F8BB1C28-BAE8-11D6-9C31-00039315CD46 A few minutes later the big job got stuck and I noticed two of these in the Xcode log: Received XPC error Connection interrupted for message type 1 kCFNetworkAgentXPCMessageTypePACQuery The big job's thread at this point: ProofProcessor - FAKE1 Queue : Job Queue (QOS: USER_INITIATED) (concurrent) #0 0x00000001948e1c34 in mach_msg2_trap () #1 0x00000001948f43a0 in mach_msg2_internal () #2 0x00000001948ea764 in mach_msg_overwrite () #3 0x00000001948e1fa8 in mach_msg () #4 0x0000000194a0ec0c in _

Hello. I tested using Xcode Version 26.2 (17C52) on macOS 26.2 (25C56) using your code with the following color format files and I was unable to reproduce a crash. Can you provide a copy of the image file you are using for testing? Formats I tried: RGB_NoneSkipFirst_8bit 8 bits/component, 32 bits/pixel RGBX format (no alpha, skip first byte) sRGB color space AlphaInfo: kCGImageAlphaNoneSkipFirst RGB_NoneSkipLast_8bit 8 bits/component, 32 bits/pixel XRGB format (no alpha, skip last byte) sRGB color space AlphaInfo: kCGImageAlphaNoneSkipLast RGB_AlphaPremultFirst_8bit 8 bits/component, 32 bits/pixel ARGB format with premultiplied alpha sRGB color space AlphaInfo: kCGImageAlphaPremultipliedFirst RGB_AlphaPremultLast_8bit 8 bits/component, 32 bits/pixel RGBA format with premultiplied alpha sRGB color space AlphaInfo: kCGImageAlphaPremultipliedLast RGB_AlphaPremultLast_16bit 16 bits/component, 64 bits/pixel RGBA format with premultiplied alpha sRGB color space AlphaInfo: kCGImageAlphaPremultipliedLast RGB

I am trying to paste from Xcode without much success. The dev forum tool is pretty awful. Is should not really matter though. The vImageBuffer_InitWithCGImage() call is pretty clear. I will try to attach a file with the code fragment. I note that the add file option does not let me add a file with a .mm extension. I will change it to .txt and see what happens. xdibARGB_fragment copy.txt

The Xcode team is here! Thanks for reporting this, I'm seeing the lost prompt as well when starting a new conversation. The crash sounds quite unfortunate and is not something I've seen. A bug report would be great, especially if you have reproducible steps or a screen recording. Even the crash report would be very informative. Thank you for reporting!

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.