build disappears

[quote='803047021, sigma2025, /thread/803047, /profile/sigma2025'] 1- What is the purpose of OID 1.2.840.113635.100.6.1.13? [/quote] In general, you can find answers to questions like this in the various docs on the Apple PKI page. In this case, you can find that OID documented in Developer ID CPS, which currently leads to Certification Practice Statement Developer ID, Version 4.0, October 16, 2024. That doc lists the OID as being critical and non-optional. An to what it means, TN3127 Inside Code Signing: Requirements has this to say on that topic: the OID 1.2.840.113635.100.6.1.13 … is present in the Developer ID Application signing certificates issued by Apple [quote='803047021, sigma2025, /thread/803047, /profile/sigma2025'] 2- Why is it marked as critical only for Turkish certificates? [/quote] That’s not my experience. Here’s a dump of my individual test Developer ID Application signing identity: % openssl x509 -inform der -in Developer ID Application: Quinn Quinn (SKMME9E2Y8).cer -text Certificate: … Si

I’m facing a similar issue with arm64e on macOS. When I turn on the Authenticate Pointers feature for my macOS app target on Xcode 26, the app target prompts requiring the 'arm64e-apple-macos’ target, the same warning message as the original poster, for local swift packages using in the main target and the target is no longer able to build. @WangZiYuan If you received any personal response from Feedback Assistant, could you please share it? @DTS Engineer Is there any way to detour it? Should I create a new post in this forumn/feedback? My environment is: macOS: Version 26.1 Beta (25B5042k) Xcode: Version 26.1 beta (17B5025f)

It now looks like the minus.capsule and minus.capsule.fill symbols have disappeared in the latest version of the SF Symbols app.

Thank you, I've created FB20529610 and attached *.xctestproducts.zip build artifact, I hope that allows you to reproduce the issue? When you say @DTS Engineer Be sure to include links to failing builds in the report. you mean the url when opening the build via AppStoreConnect, right? (Like https://appstoreconnect.apple.com/teams/{teamit}/apps/}appid}/ci/builds/{buildid}/summary ) Because when looking at it in xcode there is no share button or copy url, is there?

Had the same problem Xcode 26.0.1, Unity 6000.2.6f2. Searched the forums and tried couple of methods, finally the following worked. Min version to 16.0 Other Linker Flags in target Build, removed -ld64. Other Linker Flags in UnityFramework Build, removed -ld64. Kept the rest of the flags. Clean build, cleaned Derived Data. Compiled and it worked. Hope it will be the same for you.

For your info, I made some updates to my fix-16k branch. Also, after investigating more (thanks to Claude Code), here what seems to happen: ShazamKit AAR contains libraries with 16KB alignment (0x4000) During Android build, these libraries are re-aligned to 4KB (0x1000) The Android Gradle Plugin's strip/packaging process is changing the alignment So, are we sure that ShazamKit Android AAR has been verified to work with AGP 8.5.1+ and maintains 16KB alignment through the full build process? Maybe I missed something but at this point, I really don't know.

I'll explain what I experienced and how I solved it. iPhone was not detectable in any way (nor was the apple watch), I tried getting latest beta of Xcode, I tried latest stable release, nothing seemed to work. I waited for final release which came up shortly and still no luck. What ended up working was a thunderbolt cable. I went to an Apple Store and they told me to wipe the phone completely because I still had the beta installed, which attending to build number was wrong, but something was off so I wiped the phone. That fixed the issue, although I lost a couple of pictures and some minor data for apps that didn't save it in cloud. Hope this helps someone in the future :) As a side note, debugging on an Apple Watch is becoming really really difficult... sometimes it just does not want to connect

Your post is extremely interesting and definitely requires more thought on my part. It seems that what you're doing is to build a FocusCoordinator, conceptually similar to a Navigation Coordinator (although I think that there may be some missing APIs preventing a comprehensive solution. My immediate interest is on tab-navigation and I have some new information to offer about it. It turns out that in most cases, sending a to a focueed TextField will cause focus to change, BUT if the TextField is instantiated with the axis: AXIS parameter, the is added to the TextField body instead. I don't know how Apple will classify it, but I'm calling this a bug and have reported it. (FB20505919).

Hey! Try running in Terminal: sudo pkill coreaudiod It will prompt for a pwd also. After this it will shutdown the audio but system will bring it back very shortly and the issue should disappear (for me helps for few days)