Overview

In Instruments, I'm seeing "Zero Time Stamp" events in the "Audio Server" lane. What does that mean?

My app has now been back and forth stuck in review for a couple weeks. This is a crucial update which we promised users weeks ago. We tried expedited review a week ago and was quickly reviewed and rejected and apple mention not to use it again. However, my next reviews have been stuck for 5 days. I have tried to expedite again but no luck. Is there something wrong with my review or is this a worldwide problem?

I think if your buffer is less than 4k its recommended to use setVertexBytes, the question I have is can I keep hammering on setVertexBytes as the primary method to issue multiple draw calls within a render buffer and rely on Metal to figure out how to orphan and replace the target buffer? A lot of the primitives I am drawing are less than 4k and the process of wiring down larger segments of memory for individual buffers for each draw primitive call seems to be a negative. And it's just simpler to copy, submit and forget about buffer synchronization.

My app's in-app purchase works perfectly (i) locally (ii) in TestFlight internal testing (iii) in TestFlight external testing in the US. Where's the issue? Well I have one beta tester (TestFlight external tester) in the Philippines. She is unable to purchase. Her Apple ID region and device region are set to Philippines. My IAP has all regions and territories enabled and I can see the Philippine Peso pricing on App Store Connect. She keeps seeing the price in USD rather than PHP, which, based on my searching around, seems to be common in TestFlight. But, she also keeps getting an error "Account Not In This Store - Your account is not valid for use in the US Store. You must switch to the Philippine store before purchasing". Clicking on "Change Store" doesn't help. From searching, it seems despite seeing the price in $ she ought to be able to complete the fake purchase. Is this expected in TestFlight? I am apprehensive before submitting my app for final approval if there are going to be issues in purchasing internationally. The code is StoreKit2's product.purchase() - it's opaque to developers, and Apple is supposed to handle it correctly. Not sure what else I can do as far as the code goes. I have successfully been able to view pricing in dollars, euros, and Philippine Peso by setting the storefront to the US, Germany, and Philippines in a local Storekit config file on an iOS simulator. So I am kind of confident that it is a TestFlight issue, but it feels weird to say something like 'ah it's a TestFlight issue, it'll work in production' :) Ideally TestFlight should be identical to production. Shouldn't it? I am waiting on another international tester (this one is in Brazil) to get another data point. Has anybody encountered something similar to this before? Also, any pointers for writing an automated UI test for this? What API / sample code etc.?

Anyone knows to comply with Laws in Brazil, should we use all of the available age verification categories except the case selfDeclared category? In other words does Apple have a specific recommendation on which IOS categories for the verified age categories are recommended/not recommend to use for compliance? I didn't find any info regarding this

Hi everyone, I’m looking for some guidance regarding my app review process. I submitted my iOS app (version 1.0) and it has been in “Waiting for Review” status for quite some time now. I understand that review times can vary, but this is taking longer than I expected, and I’m not sure if this is normal or if there might be an issue with my submission. For some additional context: The first time I submitted the app, it was rejected. Since I’m new to the Apple Developer platform, I mistakenly removed the rejected build instead of addressing the rejection and resubmitting. After that, I submitted the app again, and now it’s been waiting for review. My question is: Could removing the rejected build have caused any delays or issues with the review process? Or is the current waiting time unrelated to that? I would really appreciate any advice from experienced developers on whether I should just continue waiting or if there’s something specific I should check or do. Thank you in advance for your help!

I have opened a developer account couple of month ago, and enrolled successfully. Did the app store connect and put the app for testing. The company decided to change legal entity, and thus, I had to create a new developer account. So, I have enrolled to a new developer account. My enrollment is pending for almost 3 weeks, while I do not understand what is the status. I have tried sending emails to support and also calling support, but no success. What can I do?

Hello Apple Developer Technical Support Team, I’m working on an iOS banking/security SDK and we’re trying to match an Android feature that reads payment cards via NFC (EMV). On Android, this is implemented using an NFC scanning screen (e.g., “NfcScanActivity”) that can read EMV data from contactless credit/debit cards. Could you please clarify the current iOS capabilities and App Store policy around this? On iOS, is it currently possible for a third-party App Store app to read contactless credit/debit cards using Core NFC (i.e., accessing EMV application data/AIDs from payment cards)? If this is possible, what are the supported APIs/frameworks and any entitlement requirements (if applicable)? If this is not possible for App Store apps, could you recommend the closest acceptable alternatives for achieving a similar user outcome? For example: Using Apple Pay / PassKit flows for payment-related experiences Card scanning alternatives (camera-based OCR) for capturing card details (if allowed) Using an external certified card reader accessory (MFi) and required approach/entitlements Any other Apple-recommended approach for “card verification / identification” without reading EMV NFC data Our goal is not to bypass security restrictions, but to provide a compliant solution on iOS comparable to Android’s NFC-based card reading, or to adopt an Apple-approved alternative if direct EMV reading is not supported. If helpful, I can share a brief technical summary of the Android behavior and the exact data we need to obtain (e.g., whether it’s card presence verification vs. reading specific EMV tags). Thank you for your guidance. Best regards, Anis

Hello Apple Developer Technical Support Team, I’m working on an iOS banking/security SDK and we’re trying to match an Android feature that reads payment cards via NFC (EMV). On Android, this is implemented using an NFC scanning screen (e.g., “NfcScanActivity”) that can read EMV data from contactless credit/debit cards. Could you please clarify the current iOS capabilities and App Store policy around this? On iOS, is it currently possible for a third-party App Store app to read contactless credit/debit cards using Core NFC (i.e., accessing EMV application data/AIDs from payment cards)? If this is possible, what are the supported APIs/frameworks and any entitlement requirements (if applicable)? If this is not possible for App Store apps, could you recommend the closest acceptable alternatives for achieving a similar user outcome? For example: Using Apple Pay / PassKit flows for payment-related experiences Card scanning alternatives (camera-based OCR) for capturing card details (if allowed) Using an external certified card reader accessory (MFi) and required approach/entitlements Any other Apple-recommended approach for “card verification / identification” without reading EMV NFC data Our goal is not to bypass security restrictions, but to provide a compliant solution on iOS comparable to Android’s NFC-based card reading, or to adopt an Apple-approved alternative if direct EMV reading is not supported. If helpful, I can share a brief technical summary of the Android behavior and the exact data we need to obtain (e.g., whether it’s card presence verification vs. reading specific EMV tags). Thank you for your guidance. Best regards, Imran

Hi, I’m looking for clarification on what concurrency and consistency guarantees Apple provides when multiple targets (main app + Widget extensions) access shared storage. Specifically: 1. UserDefaults (App Group / suiteName:) • If multiple processes (app + multiple widget instances) read and write the same shared UserDefaults, what guarantees are provided? • Is access serialized internally to prevent corruption? • Are read–modify–write operations safe across processes, or can lost updates occur? 2. Core Data (shared SQLite store in App Group container) • Is it officially supported for multiple processes to open and write to the same Core Data SQLite store? • Are there recommended configurations (e.g. WAL mode) for safe multi-process access? • Is Apple’s recommendation to have a single writer process? 3. FileManager (shared container files) • If two processes write to the same file in an App Group container, what guarantees are provided by the system? • Is atomic replaceItemAt the recommended pattern for safe cross-process updates? Additionally: • Do multiple widget instances count as separate processes with respect to these guarantees? • Is there official guidance on best practices for shared persistence between app and widget extensions? I want to ensure I’m following the correct architecture and not relying on undefined behavior. Thanks.

When I end editing pressing the escape key, the system sometimes plays NSBeep(). I noticed this with NSBrowser. Every time I press escape to end editing the system beeps. At first I thought it was somewhere in my app but I set a symbolic breakpoint and discovered it was not coming from my code. I filed FB22127038. Since then I discovered that NSBeep playing at inappropriate times is not exclusive to NSBrowser. It appears if there is a NSTableView in the window and you just press the escape key (even if you aren't editing anything) AppKit beeps. It can be traced to: #0 0x0000000199e3184c in NSBeep () #1 0x000000019aa03fac in -[NSWindow doCommandBySelector:] () #2 0x000000019ac1d01c in -[NSTableView(NSTableViewViewBased) cancelOperation:] ()

Hi everyone, I've exchanged several emails with support already and didn't receive meaningful answer. Everything sounds automated or the person responding is very ... not paying attention to my questions let's say. The problem I'm facing is I have released an app more than a year ago. Someone else released app with identical name few weeks after me. Developer support mentioned something about localisations and that apps with different localisations can have same name. To be honest, I don't understand that at all. Facts: both apps have identical name both apps are available only in english language according to the store listing both apps are available in same regions I wouldn't be bothered about it too much, but my "competition" is not really great and have received some bad reviews. The problem is obvious. Users are mixing my app with my competitor, writing bad feedback, asking questions about the other app and it generally is starting to be a problem now that my app is gaining more traction. It also isn't really great if you want to point someone to your app and you have to mention more details than a name so they can find MY app. So I have two questions. How the hell could someone release an app with identical name? Is there anything I can do about it? A way to fight it? I have no legal rights for the name obviously, but it isn't anything general and I did spend quite some time finding right name that wasn't already taken.

Hi, My app has been in Waiting for Review since February 21, 2026. I submitted a support ticket 3 days ago and haven't received any response. App Name: PocketMoney Bundle ID: co.mypocketmoney.app Submission date: February 21, 2026 Is there anything I can do to move this forward? Has anyone else experienced unusually long wait times recently? Any guidance appreciated.

Hello, I'm trying to enroll in the Apple Developer Program but I'm running into an ID verification issue. I'm in Canada and my ids are Canadian but I think my apple account still thinks my region is France (I changed back to Canada a few months ago and it shows Canada in Settings) since I had set it to France for when I was there. Also my phone number is still French. On Mac: my Canadian passport and Canadian driver's license are rejected as not valid for my region. On iPhone: the app just tells me to contact support. I've already reached out to Apple Developer Support but I have had no response for a few days. Is there a fix for this? I have already tried uninstalling and reinstalling the developer app.

I requested tratder status for the EU-countries on february 25th. Now, on march 4th the status is still 'in review', whilst it should be solved within 48 hours. my app is still not available in the EU. Who can help?

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.

Hi everyone, My previous updates were usually processed within 24-48 hours, so I’m concerned if there might be an issue or if there's a general delay in the review queue. Should I continue to wait, or is it time to contact the App Review team directly or Shall i re-submit another build ? Has anyone else experienced similar delays recently?

A user of my app sent me a crash report. I have never seen one like this before. All of my app's symbols are replaced with three question marks (???) Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 ??? 0x10844eb40 ??? 1 CoreFoundation 0x7ff80f155518 __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 137 and the binary image as 0x0 - 0xffffffffffffffff ??? (*) <00000000-0000-0000-0000-000000000000> ??? so I cannot find out where exactly the crash happened. What can cause this kind of crash report and can I do anything with it? crash.ips

Hello, I have a collection view that uses a diffable data source, and I am initiating an API call while configuring a cell RuntimeCell in the cell registration block inside setupDataSource(). The cell has a runtimeLabel property whose text I am setting inside a configureLabel(movieId:) function. I noticed that the collection view does not automatically refresh the text label once this API call finishes and after setting the text property on a UILabel in the collection view cell to a value retrieved during the API call. I presume this is because I need to call dataSource.apply(snapshot) myself to reload the changes in the collection view after the API call finishes retrieving the runtime data. However, since the API call happens via the configuration of the cell in the cell registration closure, this API call ends up being called infinitely if I call dataSource.apply(snapshot) every time the API call finishes (i.e. calling dataSource.applySnapshot() calls the closure for the cell registration handler which re-triggers the API call). What is the correct architecture to apply to accomplish reloading the collection view so that the text label appears once the API finishes calling? Thank you class MovieDetailViewController: UIViewController { func setupDataSource() { // ... let runTimeCellRegistration = UICollectionView.CellRegistration<RuntimeCell, Item> { cell, indexPath, item in cell.runtimeLabelDelegate = self cell.configureLabel(movieId: self.selectedMovie.id) } dataSource = UICollectionViewDiffableDataSource(collectionView: collectionView, cellProvider: { collectionView, indexPath, itemIdentifier in let section = Section(rawValue: indexPath.section) switch section { //... case .runtime: return collectionView.dequeueConfiguredReusableCell(using: runTimeCellRegistration, for: indexPath, item: itemIdentifier) //... } return nil }) } } protocol RuntimeLabelCellDelegate: AnyObject { func didUpdateRuntime() } class RuntimeCell: UICollectionViewCell { var runtimeLabel: UILabel! //... UI Setup func configureLabel(movieId: Int) { Task { do { let details = try await movieSearchService.fetchMovieDetails(movieId: movieId) await MainActor.run { let minutes = details.runTime let durationText = "\(minutes)m" var emojiText = "" if minutes < 90 { emojiText = "Short & Sweet ⚡️" } else if minutes > 150 { emojiText = "Get the snacks ready 🍿" } runtimeLabel.text = emojiText.isEmpty ? durationText : "\(durationText) • \(emojiText)" runtimeLabelDelegate?.didUpdateRuntime() } } catch { print("Failed to load details: \(error)") } } } } extension MovieDetailViewController: RuntimeLabelCellDelegate { func didUpdateRuntime() { var snapshot = dataSource.snapshot() snapshot.appendItems([.runtime], toSection: .runtime) dataSource.apply(snapshot, animatingDifferences: true) } }

Hello everyone, I am an iOS developer and both my apps are experiencing an unusual App Store review delay that I have not been able to resolve through the normal support channels. These are existing apps on app store with simple updates. It has not moved to “In Review”, and I have not received any rejection message or request for additional information from the App Review team. AppleID: 6756242440 and 6746870245 Please help us resolve the issue. Thanks in advance