Overview

Hi everyone, I am developing a benchmarking tool to measure memory latency (L1/L2/DRAM) on Apple Silicon. I am currently using Xcode Instruments (CPU Counters) to validate my results. In my latest run for a 128 MB buffer with random access, Instruments shows: Latency (cycles): ~259 cycles (derived from LDST_UNIT_OLD_L1D_CACHE_MISS / L1D_CACHE_MISS_LD). Manual Timer Result: ~80 ns. To correlate these two values, I need the exact CPU Frequency (GHz) at the time of the sample. My Questions: Is there a recommended way to programmatically fetch the current frequency of the Performance cores (p-cores) during a benchmark run? Does Apple provide a "nominal" frequency value for M-series chips that we should use for cycle-to-nanosecond conversions? In Instruments, is there a hidden counter or "Average Frequency" metric that I can enable to avoid manual math? Hardware/Software Environment: Tool: Instruments 26.3+ (CPU Counters Template). Chip: A19, iPhone 17 pro. OS: 26.3.

Hi， Apps crashed when GCDAsyncSocket closeWithError，since iOS 16 。 Crash stack like this： Hardware Model: iPhone10,1 Code Type: ARM-64 (Native) Parent Process: [1] Date/Time: 2022-06-09 08:59:02.201 +0800 OS Version: 16.0 (20A5283p) Report Version: 104 Last Exception : 0 libsystem_platform.dylib 0x000000021bc1f08c 0x000000021bc19000 + 24716 1 libsystem_platform.dylib 0x000000021bc19898 0x000000021bc19000 + 2200 2 CoreFoundation 0x00000001a4dfa3e0 CFSocketInvalidate + 132 3 CFNetwork 0x00000001a5667830 _CFNetworkErrorGetLocalizedDescription + 307856 4 CoreFoundation 0x00000001a4d55f4c CFArrayApplyFunction + 72 5 CFNetwork 0x00000001a56453ac _CFNetworkErrorGetLocalizedDescription + 167436 6 CoreFoundation 0x00000001a4d5d118 0x00000001a4d49000 + 82200 7 CoreFoundation 0x00000001a4dfa718 CFSocketInvalidate + 956 8 CFNetwork 0x00000001a5651e84 _CFNetworkErrorGetLocalizedDescription + 219364 9 CoreFoundation 0x00000001a4d631d4 0x00000001a4d49000 + 106964 10 *** 0x000000010c1bc490 -[GCDAsyncSocket closeWithError:] + 260 11 *** 0x000000010c1c0b54 -[GCDAsyncSocket doReadEOF] + 360 12 *** 0x000000010c1bf1fc __69-[GCDAsyncSocket setupReadAndWriteSourcesForNewlyConnectedSocket:]_block_invoke + 88 13 libdispatch.dylib 0x00000001a4a330f4 0x00000001a4a2f000 + 16628 14 libdispatch.dylib 0x00000001a4a36584 0x00000001a4a2f000 + 30084 15 libdispatch.dylib 0x00000001a4a49b04 0x00000001a4a2f000 + 109316 16 libdispatch.dylib 0x00000001a4a3a684 0x00000001a4a2f000 + 46724 17 libdispatch.dylib 0x00000001a4a3b2f8 0x00000001a4a2f000 + 49912 18 libdispatch.dylib 0x00000001a4a45ebc 0x00000001a4a2f000 + 93884 19 libsystem_pthread.dylib 0x000000021bc210a8 _pthread_wqthread + 288

在iOS 26.4 beta3版本中，当前支付完成，获取的票据是上次支付的票据，在拉起一笔支付成，获取的又是上次支付的票据

Hey has someone figured out how or when does a report request become inactive? Is there like a fixed time period for how long an ONGOING accessType stays active? And does the same rule apply for ONE_TIME_SNAPSHOP? Has someone managed to create multiple active reports for both accessTypes per one app? And can you have multiple inactive ones? Sadly couldn't find answers to my questions from the App Store Connect API documentation :(

I am the Account Holder (Team ID: KCRXG75U7S). Since January 18, 2026, I cannot access developer.apple.com — it redirects to the "Need assistance" contact form. App Store Connect works fine. I have live apps on the App Store. On January 18, I received unexpected "Welcome to the Apple Developer Program" and "You're invited to join a development team" emails, even though I was already a member. After that, all access to the developer portal was lost. I have submitted 9+ support requests since February 11. Not a single one has received a response. Chat support disconnects. Phone support only creates new cases. Case IDs: 102835281938, 102824841068, 102819959750, 20000111583405, 20000111568823 Can any Apple engineer please look into this?

I’m experiencing an issue with my app submission that has been stuck in “Waiting for Review” for several days, and I wanted to check if others are facing a similar situation or if this is currently expected. apple ID:6758572992

Hey has someone figured out how or when does a report request become inactive? Is there like a fixed time period for how long an ONGOING accessType stays active? And does the same rule apply for ONE_TIME_SNAPSHOP? Has someone managed to create multiple active reports for both accessTypes per one app? And can you have multiple inactive ones?

Hey has someone figured out how or when does a report request become inactive? Is there like a fixed time period for how long an ONGOING accessType stays active? And does the same rule apply for ONE_TIME_SNAPSHOT? Has someone managed to create multiple active reports for both accessTypes per one app? And can you have multiple inactive ones?

Can't able to run the Create ML for training and I upgraded to MacOS 26.3 beta and I have tried older and newer

Hi, we are trying to have our app approved since 2 weeks now with the subscription attached, now we are in a very strange situation where the app is approved but the subscription is still "Waiting for review" and we don't understand how is possible considering the app binary have the subscription flow inside. Can you help us? We also asked an expedited review today for the app due to business needs and just the app is approved without the subscription. The app is "Hey Clary" ID: 6752716476 Thanks

I'm new to graphics and game design and I just wanted to know if a compute pipeline could be as efficient as a render pipeline for rasterization and an explanation on how and why. Also is it possible to manually perform rasterization with a render pipeline as in manipulate individual pixel data in a metal texture yourself but do it with a render pipeline?

I purchased my Apple Developer program on March 2nd, and received payment confirmations, but have not yet received a final approval email. It has been more than 48 hours. Please help check the status

Hello, I am in Nigeria and I am having a problem with my Apple Developer Program enrollment. I enrolled through the Apple Developer app and was charged, but when I tried to log in on the web it asked me to make the payment again. Now the Developer app shows this message: “Enrollment through the Apple Developer app is not available for this Apple Account. Visit developer.apple.com/programs/enroll/.” My account is not active even though I have already been charged. Has anyone experienced this issue or knows how it can be resolved? My Enrollment ID is 9VP8HU4KC5. Thank you.

I have a group of XCUItest suites that were designed to run in parallel on simulators. They run fine in xcode 16.2, but when I try to run them in Xcode 26 they run fine the first time, but on the second time I get an error that the simulator cannot be found: "No matching device (62621AD4-C8D6-4A1B-B511-79236113FD94) ". This UDID seems to be from one of the clones that were spawned on the previous test run. No matching device (62621AD4-C8D6-4A1B-B511-79236113FD94) in set at /Users/myUser/Library/Developer/XCTestDevices Domain: com.apple.CoreSimulator.SimError Code: 404 User Info: { DVTErrorCreationDateKey = "2026-02-26 22:52:53 +0000"; IDERunOperationFailingWorker = "_IDEInstalliPhoneSimulatorWorker"; } If I clean all simulators and try to run again without closing Xcode, it keeps trying to access the clone that no longer exists. If I close an reopen xcode after removing all simulators ~/Library/Developer/XCTestDevices, xcode keeps trying the wrong device and I get the following error: Failed to clone device named 'iPhone 17 Pro'. (Underlying Error: The operation couldn’t be completed. Device was allocated but was stuck in creation state. Check CoreSimulator.log for more information.) This is what I get from CoreSimulator log: Feb 26 17:24:34 Mac-GD6GX5XH CoreSimulatorService[99200] : Device 3C7BE1BE-416E-480A-BDA6-ADE8F0ADF818 encountered in creation state at launch. The device will be re-created. Feb 26 17:24:34 Mac-GD6GX5XH CoreSimulatorService[99200] : Failed to clone the device data path from /Users/MyUser/Library/Developer/CoreSimulator/Devices/7A5377DC-3ED9-4C8B-96EB-8DF7BEF4AE8B/data to /Users/MyUser/Library/Developer/XCTestDevices/3C7BE1BE-416E-480A-BDA6-ADE8F0ADF818/data, error = Error Domain=NSCocoaErrorDomain Code=260 "The file “data” couldn’t be opened because there is no such file." UserInfo={NSFilePath=/Users/MyUser/Library/Developer/CoreSimulator/Devices/7A5377DC-3ED9-4C8B-96EB-8DF7BEF4AE8B/data, NSURL=file:///Users/MyUser/Library/Developer/CoreSimulator/Devices/7A5377DC-3ED9-4C8B-96EB-8DF7BEF4AE8B/data, NSUnderlyingError=0x600000d04120 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}} Feb 26 17:24:34 Mac-GD6GX5XH CoreSimulatorService[99200] : Failed to re-create device that was encountered in the creation state (Clone 1 of iPhone 17 Pro (3C7BE1BE-416E-480A-BDA6-ADE8F0ADF818, iOS 26.2, Creating)): Error Domain=NSCocoaErrorDomain Code=260 "The file “data” couldn’t be opened because there is no such file." UserInfo={NSFilePath=/Users/MyUser/Library/Developer/CoreSimulator/Devices/7A5377DC-3ED9-4C8B-96EB-8DF7BEF4AE8B/data, NSURL=file:///Users/MyUser/Library/Developer/CoreSimulator/Devices/7A5377DC-3ED9-4C8B-96EB-8DF7BEF4AE8B/data, NSUnderlyingError=0x600000d04120 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}} Feb 26 17:24:34 Mac-GD6GX5XH CoreSimulatorService[99200] : New device is stuck in creation state, deleting: Clone 1 of iPhone 17 Pro (3C7BE1BE-416E-480A-BDA6-ADE8F0ADF818, iOS 26.2, Creating) Feb 26 17:24:34 Mac-GD6GX5XH CoreSimulatorService[99200] : Error Domain=NSPOSIXErrorDomain Code=22 "Invalid argument" UserInfo={NSLocalizedFailureReason=Device was allocated but was stuck in creation state. Check CoreSimulator.log for more information.} Feb 26 17:24:34 Mac-GD6GX5XH CoreSimulatorService[99200] : Error Domain=NSPOSIXErrorDomain Code=22 "Invalid argument" UserInfo={NSLocalizedFailureReason=Device was allocated but was stuck in creation state. Check CoreSimulator.log for more information.} Feb 26 17:24:34 Mac-GD6GX5XH com.apple.dt.Xcode[2744] : Error Domain=NSPOSIXErrorDomain Code=22 "Invalid argument" UserInfo={NSLocalizedFailureReason=Device was allocated but was stuck in creation state. Check CoreSimulator.log for more information.}

Hi, We're experiencing a WKWebView issue where the screen intermittently turns pure magenta (#FF00FF) in our production iOS app. After investigation, we traced this to WebKit's internal WKCompositingView.mm where [UIColor magentaColor] is used as a pending state indicator when coverView.hidden == NO. This matches rdar://163597990 / WebKit Bug 303157 ("Magenta flash when loading page"), which was fixed in commit 303720@main on 2025-12-01 via PR #54499. My question is simple: which iOS/Safari release includes this fix? We're on iOS 26.3 and still seeing the issue. We need to know: Is the fix already in iOS 26.3? (If so, there may be another unfixed code path) If not, which upcoming iOS version will include it? Our environment iOS 26.3, iPhone 15 Pro Max WKWebView with complex web content App codebase contains zero magenta color usage — this is purely from WebKit Related rdar://163597990 Bug 303157 — RESOLVED FIXED Bug 230531 — "Pages render as magenta after being in background" PR #54499 — Merged to main 2025-12-01 Any information about the release timeline would be very helpful. Thanks!

Your enrollment could not be completed. Your enrollment in the Apple Developer Program could not be completed at this time.

Problems searching in mail after upgrade to Tahoe 26.4 Beta (25E5218f). Removing the index files and requesting rebuild results in a hung rebuild process. In the activity monitor I see Indexing... and a bar that is stuck at 0%. I have rebooted and restarted mail. No change. I was able to rebuild the spotlight search, and it is working properly.

I get the message on my iphone 14 as below. "Contact Us to Continue There may be an issue with your account that needs to be resolved before you can continue. Please contact support." I raised the case no. 102822291300 to apple support and they replied to my email they can assist in identity verification and I cannot use developer account. It is very sad to see there is no support from apple to be able to resolve the issue. Their tool flagging the issue seems to have bugs and support team has expressed their inability to provide resolution. Can anyone support how this issue can be fixed? Thanks a lot for your support in advance. Kind Regards, Pradeep

Dear All, I am writing to report what appears to be a bug in the Apple Developer App’s enrollment verification system that is incorrectly flagging personal hardware. Problem Statement: I am unable to complete enrollment for the Apple Developer Program. On the "Personal Information" or "Identity Verification" stage, the app displays: "Contact Us to Continue. There may be an issue with your account that needs to be resolved..." Hardware History: Device: iPhone 14 (iOS latest) The device was previously owned by a family member who never enrolled in the Developer Program. The device was factory reset/wiped before my account was added. Despite this, Support (Case 102822291300) states the device is flagged as a "shared device" and refuses to proceed with identity verification. The Impasse: Support has indicated they cannot provide further assistance. However, as an individual developer, this is my primary device. If the system is flagging a reset device as "shared" when there is no history of developer use, it suggests a flaw in the automated verification logic. Request: Can a moderator or support representative look into Case 102822291300 to verify why this specific hardware is being restricted? Is there a manual path for identity verification (Passport/National ID) that doesn't rely on the Apple Developer App's automated device check? Allow me to do manual verification and provide the resolution to the issue. I am eager to bring my app to the platform and would appreciate a path to resolution. Kind Regards, Pradeep Bangalore

Hi all, We're looking for some level of explanation explaining the delay in review times since the New Year. I develop an Application that has been on the AppStore for almost a decade and this is a fully functional business. Historically, Apple were quite good with review times and feedback but since the New Year we're suffered massively trying to get important fixes out to our users. This has begun to negatively effect the bottom line of the business. On top of that, when we ARE lucky enough to get a review, Reviewers have started to make complaints about certain Info.plist declarations that we've had for the longest time with no issue, and they're only being raised as issues now. These rejections lead to further 4-5 day wait times for a review and our customers are on our backs daily looking for answers of why we can't deploy these fixes. Is this the new reality at Apple? What is the reasoning for these delays? Influx of new apps? Cuts to your review department? Change in how Applications reviews are prioritised? Not even Expedited Reviews are helping as they should. Please provide us with an explanation of what's going on here because our customers are furious. Kind regards, K