Overview

This is my first attempt at creating a Wallet pass, actually a generic store card. When I see it with Pass Viewer on macOS, I get 1 look, when I see it with the iPhone simulator or iPhone proper, I get a different view. Neither is what I was hoping for, a simple vertical layout of an address. Could someone steer me in the correct direction? My json: "formatVersion": 1, "passTypeIdentifier": "pass.org.danleys.4KSBarcode", "serialNumber": "__SERIAL__", "teamIdentifier": "----", "organizationName": "4 K.I.D.S. Sake", "description": "4KSBarcode", "logoText": "4 K.I.D.S. Sake", "foregroundColor": "rgb(255, 255, 255)", "backgroundColor": "rgb(255,0,0)", "storeCard" : { "primaryFields" : [ { "key" : "ClientID", "label" : "", "value" : "" } ], "auxiliaryFields": [ { "key": "street", "label": "Address", "value": "339 Remington Blvd" }, { "key": "city", "label": "", "value": "Bolingbrook, IL 60440" } ] }, "barcode": { "format": "PKBarcodeFormatCode128", "message": "__SERIAL__", "altText": "__SERIAL__", "messageEncoding": "iso-8859-1" } } On macOS: On iOS: Thank you. Ed

Hi, I have completed the payment for my Apple Developer membership but my order (W1388955794) is still showing as pending. Could you pls review and confirm the payment. Thanks

We have tried numerous times to register a developer account for a company that is one of our clients. Each time, the application has been denied for a different reason. The last time, they said that the website ‘does not load,’ which is untrue. The website belongs to a government entity and is fully accessible from our country and from around the world, as verified by Google Analytics. We do not know what is happening, but we would like to know if anyone has experienced something similar and how they resolved it. Thank you. Translated with DeepL.com (free version)

I am looking for some guidance regarding a significant delay in the review process for my app update. Platform: iOS Submission Date: February 10, 2026 Current Status: Waiting for Review It has now been 16 days, and the status has not progressed to "In Review." I have checked my App Store Connect "App Review" section, but there are no outstanding requests for information or messages from the review team. I have already attempted to contact the App Review team via the official "Contact Us" form but have only received generic automated responses. Is anyone else experiencing similar delays this month? Are there currently known backlogs, or should I consider canceling this release and re-submitting? Thank you for any insights.

Hello, I am writing to ask for assistance regarding two of my apps that have been stuck in “Waiting for Review” for an extended period. At the moment: App ID 6497716649 — Waiting for Review since Feb, 19 at 11:45 AM App ID 6743224713 — Waiting for Review since Feb, 15 at 10:26 PM There are no warnings, Resolution Center messages, or visible issues in App Store Connect. All Agreements, Tax, and Banking information are active and up to date. The builds were uploaded successfully, and no further action appears to be required on my side. Could you please help confirm: Whether there is any hidden blocker or account-related issue? Or if this delay is currently due to review queue processing times? If additional details are needed (bundle IDs, app category, sign-in requirements, encryption/export compliance, etc.), I will be happy to provide them immediately. Thank you very much for your time and support. Best regards,

Hello, I have a policy-related question regarding App Store Review for dating apps. As a development agency, we build apps based on client requirements. Recently, we received feedback from App Review stating that the dating app category is saturated and that the app should demonstrate unique features to avoid being considered spam or a duplicate of existing apps. In such cases, what is the recommended approach for developers working on client projects? If a client requests a standard dating app with common features (profiles, matching, chat, etc.), is it likely to be rejected under the spam/duplicate guideline (4.3)? Should developers proactively advise clients to include clearly differentiated features before submission, even if the app is functionally complete and complies with technical guidelines? Any clarification on how App Review evaluates dating apps for uniqueness under Guideline 4.3 would be very helpful. Thank you.

I realize there are already several posts here about the unusually long review times for app submissions. There are some replies from Apple stating that they are looking into it or that specific issues have been resolved, but the problem persists and no one seems to understand what is actually happening or what can be done to improve the situation. I have been experiencing the same issue over the past six weeks. My app (submission ID: 75aed892-ee07-49e1-b62b-fdd54f1b04f8) was rejected because the reviewer stated that it needed “citations, such as links to resources.” I therefore added citations with functional links to online resources directly on the page where the claims were made, yet my app was rejected again with exactly the same copy-and-paste feedback. I then asked for clarification, but my question has remained unanswered for a week. There seems to be a fundamental problem in the App Store review process. For me, it has become a cumbersome issue, as the unexpectedly long response times are causing me to miss deadlines with my customers. We fix and resubmit our app within minutes, literally, but every time we have to wait weeks for the next reply from Apple. Should we pause submissions for a while and focus on other activities, and manage expectations with our customers accordingly? Or is this a temporary situation that is likely to improve soon? Any insights or tips would be much appreciated. Thank you.

We have tried using multiple test devices to dev and test Digital Wallet provisioning and unable to do it successfully as the rule decision goes into orange flow. This is a blocker for our project involving digial wallet provisioning testing. Is there a way that our test devices could be excluded from hitting orange rule so we can continue with provisioning?

Hello, We submitted a v1 of our app in December, it took a day to review. The v1 was just a test version to make sure Apple were happy with it. We submitted v1.1 last Friday (20th) and are still sat in "Waiting for Review" - I can see a fair few other people are waiting, but does anyone know the reason why? Our launch is tied to national and trade press, which we're now going to have to push back at cost to the business. Any advice from anyone? App ID is 6753305041 Thanks

My code that streams buffers into AVAudioPlayerNode is stuttering when the buffer is finished and before the next one is played. while engine.isRunning { let framesToCopy = min(buffer.frameLength - framePosition, Self.BufferSize) let srcRaw = UnsafeRawPointer(srcPtr) let playbackBuffer = AVAudioPCMBuffer(pcmFormat: buffer.format, frameCapacity: Self.BufferSize)! let playbackPtr = playbackBuffer.floatChannelData![0] let destRaw = UnsafeMutableRawPointer(mutating: playbackPtr) memcpy(destRaw, srcRaw, Int(framesToCopy) * MemoryLayout<Float>.stride) srcPtr = srcPtr.advanced(by: Int(framesToCopy)) playbackBuffer.frameLength = framesToCopy await player.scheduleBuffer(playbackBuffer, at: nil, options: [], completionCallbackType: .dataRendered) } I've tried to schedule multiple buffers at once using a combination of both the synchronous and async versions of scheduleBuffer because I thought the delay might be but it still stutters and the data copied into the playbackBuffer matches the source buffer. I've tried all combinations of options and completionCallbackType but no luck. I've tried increasing the buffer size but that just spaces out the stutters because the buffer is larger. What am I missing about this API?

Hi, I did submit my app to review on 7th February, but it is still waiting for review. No status change, no feedback even if i created support ticket. I wonder if this is normal process or something is wrong on my submission. I see people are complining about waiting times but 20 days don't seem an ordinary. It is my first app and market submission.

iOS | 26.3 specific | Google Map hangs after sharing the location to other app which open the location in new app Device: iPhone 13 Pro Max
iOS Version: iOS 26.3
Google Maps Version: 26.08.2 Steps to Reproduce: Open Google Maps. Select any location Tap Share. Share the location to another app (e.g., navigation app, co - pilot or any third party apps). Return to Google Maps. Expected Result:
Google Maps should continue functioning normally. Actual Result:
Google Maps becomes unresponsive and hangs.

After nearly ten years in Android development, I finally built a native iOS app, sharing the journey publicly while learning Swift and SwiftUI, using AI selectively, and finding the platform familiar yet different in tooling, concurrency, and culture. I reached production without initially buying a developer account and faced a stricter, iterative App Store review process than the Play Store, with several rejections that ultimately clarified Apple’s quality standards and expectations.

Our app has been rejected - requiring more information to proceed (2.1). The question asked relates to a query we had way back when we first launched the app to the app store, which at the time we amended and fixed to Apple's satisfaction and the app was launched. Since then, we have had a further 4 releases with no issue, not touching the area of the app in question throughout any of them. Until suddenly it got rejected for that same issue, again I stress nothing has changed in relation to the section of the app they are questioning. I've answered to this effect but received no reply. The reason for this release was that we have a critical payment bug issue in the previous release, which is literally all we changed from the previous version. We have a live app launch with over 300+ people attending on Saturday. We urgently need to get this through, and I seem unable to expedite the review (it doesn't give me the drop down and just says "There are no apps associated with this team.")

I have been waiting 8 days for a response regarding my Apple Developer Program enrollment. I submitted a support request on Feb 18, 2026 and sent a follow-up on Feb 23 — both times I only received automated replies. Case ID: 102824778431 Please escalate this case. It is blocking my app development. Thank you.

Hi everyone, I'm a developer from China, and my Apple Developer Program membership is currently in the renewal period. When I click the renewal button from the banner at the top of the Apple Developer website, the page redirects but consistently shows a 503 Service Unavailable error. This has been happening for several days now. I've already tried: Switching to different devices or Changing network environments Unfortunately, the issue persists in all cases. Has anyone else encountered this same situation? Any help or suggestions would be greatly appreciated! Thanks in advance.

macOS 26.4 Beta appears to have changed how built-in MacBook keyboard events are routed through IOHIDSystem. Third-party virtual HID devices loaded via DriverKit no longer receive events from the built-in keyboard. External keyboards are unaffected. This is already confirmed across multiple users: https://github.com/pqrs-org/Karabiner-Elements/issues/4402 One possible lead (from LLM-assisted code analysis, not independently verified): this could be related to a security policy referred to as com.apple.iohid.protectedDeviceAccess, which may block IOHIDDeviceOpen for the Apple Internal Keyboard via SPI transport (AppleHIDTransportHIDDevice). A "GamePolicy" check in IOHIDDeviceClass.m that gates HID device access could be involved. This is a hint, not a confirmed root cause. The impact goes well beyond a single project. Keyboard remapping on macOS is a thriving ecosystem — used for accessibility, ergonomics, developer productivity, and multilingual input. This is one of macOS's strengths as a platform. Many professionals specifically choose Mac because this level of customization is possible. If this capability is being removed without an alternative, it would significantly diminish what makes macOS attractive for power users and developers. Is this an intentional architectural change to the input event pipeline for built-in keyboards, or a beta regression? If intentional, what is the recommended alternative for developers?

Since macOS 26.4 Beta 1, virtual HID devices created via DriverKit can no longer intercept key events from the built-in MacBook keyboard. External keyboards still work. This is confirmed and tracked here: https://github.com/pqrs-org/Karabiner-Elements/issues/4402 One possible lead (from LLM-assisted analysis of Apple's open-source IOHIDFamily code and cross-referencing community reports): macOS 26.4 Beta may have introduced or modified a security policy referred to as com.apple.iohid.protectedDeviceAccess, which could block IOHIDDeviceOpen for the Apple Internal Keyboard connected via SPI transport (AppleHIDTransportHIDDevice). This appears related to a "GamePolicy" check in IOHIDDeviceClass.m that gates whether processes can open HID devices. This has not been independently verified and may or may not be the root cause. This has far-reaching consequences. Karabiner-Elements alone has over 21,000 GitHub stars and is used by hundreds of thousands of macOS users for keyboard customization, accessibility workflows, ergonomic setups, and multilingual input. This change completely breaks its core functionality on any MacBook. Beyond Karabiner, this affects every developer building keyboard remapping, input customization, or accessibility tooling via DriverKit virtual HID devices — including commercial applications currently in development. I'd argue that the power and flexibility of keyboard customization on macOS is a genuine competitive advantage for the platform. Developers and power users choose Macs partly because tools like this exist. Restricting this capability would be detrimental to the ecosystem and to Apple's appeal among professional users. I'd like to understand: is this an intentional security change or a regression? If intentional, is there a migration path?

As stated in the title, my device is M4 macmini, running macOS 26, with Xcode version 26.1. The error message is ": retrying debugserver without secure proxy due to error: Error Domain=com.apple.dtdevicekit Code=811 UserInfo={NSUnderlyingError=0xc42b07930 {Error Domain=com.apple.dt.MobileDeviceErrorDomain Code=-402653150 UserInfo={MobileDeviceErrorCode=, com.apple.dtdevicekit.stacktrace=, DVTRadarComponentKey=261622, NSLocalizedDescription=}}, NSLocalizedRecoverySuggestion=Please check your connection to your device., DVTRadarComponentKey=261622, NSLocalizedDescription=}, the official documentation does state that debugging is supported for devices running at least iOS 15. However, my 2019 MacBook Pro, with macOS 15.7.2 and Xcode 26.1 installed, can debug iOS 12 devices normally. The product manager has asked me to identify the issue, but I am at a loss. If anyone can provide a solution or confirm that support for iOS 12 is no longer available, we would be very grateful. Additionally, iOS 13 devices can all be debugged normally

Hi, On macOS 26.4 Beta (25E5218f) （macOS Tahoe 26 Developer Beta ）, the network filter causes network failures or slowdowns. This manifests as Chrome failing to access websites, while Safari can access the same websites without issue. The affected websites can be pinged locally. My situation is similar to this situation.The same question link is: https://github.com/objective-see/LuLu/issues/836 Have you been paying attention to this issue? Hopefully, it can be fixed in the official release. Thank you.