Overview

We're seeing some strange behavior of the appAccountToken when passing it to a purchase in the sandbox environment. Normally we'd expect the same account token to be set on the resulting verfication, but that's not the case. Instead the token seems to be persisted on the API side and reused for some amount of time, meaning there's a mismatch and the connection between account and purchase is lost. This happens consistently even if we send new tokens on each purchase. Has there been any updates to purchase flow in the sandbox environment on Apple's side? .purchase( options: [.appAccountToken(token)] )

I would like to renew my Apple Developer membership but I'm faced with this : I've filled the form and hit sent, but I didn't receive either a response or a receipt ; it's been multiple days. Is Apple ever going to respond ?

Death Stranding 2: On the Beach (v1.0.48.0, Steam) crashes during rendering initialization when running through CrossOver 26 with D3DMetal 3.0 on an Apple M2 Max Mac Studio running macOS Sequoia. The game successfully initializes Streamline, NVAPI, DLSS (Result::eOk), DLSSG (Result::eOk), Reflex, and XeSS — all subsystems report success. The crash occurs immediately after, during rendering pipeline creation, before the game reaches NXStorage initialization or window creation. Minidump analysis confirms the crash is an access violation (0xc0000005) at DS2.exe+0x67233d, writing to address 0x0. RAX=0x0 (null pointer being dereferenced), R12=0xFFFFFFFFFFFFFFFF (error/invalid handle return). The game appears to call a D3D12 API — likely CheckFeatureSupport or a pipeline state creation function — that D3DMetal acknowledges as supported but returns null or invalid data for. The game trusts the response and dereferences the null pointer. Two other Nixxes titles using the same engine and D3DMetal setup run without issue: Spider-Man 2 (~50 FPS) and Horizon Zero Dawn Remastered (~34 FPS). DS2 uses newer technology versions (DLSS 4, FSR 4, XeSS 2) and a newer DirectX 12 Agility SDK, which likely queries D3D12 features that D3DMetal does not yet fully implement. The crash also reproduces when D3DMetal reports as AMD vendor (1002) instead of NVIDIA (10de), crashing at the same executable offset, confirming it is a D3D12 feature reporting gap in D3DMetal rather than a vendor-specific issue. How To Reproduce Install Crossover 26+ on MacOS 26.4 Install Steam and download Death Stranding 2 Run Death Stranding 2 and check logs after crash in Documents\DEATH STRANDING 2 ON THE BEACH Feedback Requests FB22285513 — Game Porting Toolkit 3 issue with Modern Pipeline Creation

Hey everyone, I applied for the App Store Small Business Program on February 18th and I still haven't heard anything back, that's almost 20 days now. Is this normal? How long did it take for those of you who got approved? I'm starting to wonder if my application even went through correctly. Would really appreciate hearing your experiences — especially if you applied recently. Did anyone else wait this long? Thanks

I have an application which records video along with some custom metadata and a chapter track. The resultant video is stored in the Camera Roll. When sharing the video via the Share Sheet or AirDrop, the metadata track is stripped entirely (the chapter markers are preserved) Sharing via AirDrop with the "All Photos Data" option does include the metadata track, as does copying from the device with Image Capture but this is a bad user experience as the user must remember to explicitly select this option, and the filename is lost when sending this way. I have also tried various other approaches (such as encoding my metadata in a subtitle track, which I didn't expect to be stripped as it's an accessibility concern) but it's also removed. Essentially I am looking for a definitive list of things that are not stripped or if there's a way to encode a track in some way to indicate it should be preserved. The metadata is added via AVTimedMetadataGroup containing one AVMutableMetadataItem which has its value as a JSON string. I took a different approach with the Chapter Marker track (mainly because I did it first in a completely different way and didn't rework it when I added the other track). I post-process these after the video is recorded, and add them with addMutableTrack and then addTrackAssociation(to: chapterTrack, type: .chapterList) but I don't think that's the reason the chapter track persists where the custom metadata does not as other tests with video files from other sources containing subtitles etc also had their subtitle data stripped. tl;dr I record videos with metadata that I want to be able to share via Share Sheet and AirDrop, what am I doing wrong?

Hi, I am working on app at the moment that uses Icon Composer for all of its icons and variations. I want to add an iMessage App to my project however I get validation errors from App Store Connect even if I add an imessage app to my asset catalog and include all app icon assets. Is there any way to do this at the moment natively with Icon Composer? If not how do I manually overwrite the icon JUST for iMessage and not for my entire iOS app?

Hello, I started my Apple Developer enrollment using the Apple Developer app. However, the payment method available on my device cannot be accepted because the billing address is outside the United States. Is it possible to complete the membership purchase through the web instead of the app?

Hi everyone, I’m testing an iPhone app called Steady through TestFlight and would love honest feedback. Steady is built for the moment right before someone acts on an urge they may regret. The core idea is to create a short pause before action, then let the user log what happened so they can spot patterns over time. Use cases could be things like sending a text you shouldn’t, reacting too fast, opening something you wanted to avoid, or other impulsive moments. I’m mainly looking for feedback on three things: Does the concept feel useful in real life? Is the flow clear or confusing? What feels unnecessary or missing? TestFlight link: https://testflight.apple.com/join/YsnDsGR5 Appreciate any honest feedback.

Hi everyone, I’m currently trying to set up a business account on the Apple Developer Console, and I’ve run into a really frustrating issue. Last month, I was asked to submit additional documents for verification. I submitted everything as requested and received a confirmation email: “Thank you for providing the documents we requested. We will review them and follow up with you within two business days.” However, weeks passed with no update. About 1–2 weeks ago, I reached out to support again. I was asked to re-submit the same documents, which I did. Once again, I received the same confirmation email stating a response would come within two business days. It’s now been 7 days since that second submission, and still no response. At this point, I’m not sure what I’m doing wrong or if this is just a delay on Apple’s side. What’s more confusing is that we’ve successfully created developer accounts on other platforms (like Google Play) using the same business information and DUNS number, with verification completed in under 24 hours. Has anyone experienced something similar with Apple Developer business verification? Is there something specific Apple looks for that I might be missing, or is this just a backlog/delay issue? Would really appreciate any insights or advice. Thanks 🙏

Why the review process seems stuck? I contacted apple review support too multiple times and I am completely ignored they just forward the emails. Is there anyone I can talk to about this? We have an old app this is not a new app and this doesnt make sense at all. App id 1660054787.

Hello everyone, I wanted to check whether other developers are currently experiencing unusually long “Waiting for Review” times. Our app Aslan Wealth (App ID: 6755077470) has been stuck in Waiting for Review for quite a while and has never entered the “In Review” stage. Timeline Feb 18, 2026 – Version submitted for review Feb 23 – Contacted Apple Developer Support regarding review status Feb 24 – Received reply that the case was escalated to the review team Mar 3 – Still in Waiting for Review (confirmed by support that the app is still in the queue) Mar 7–11 – Followed up with Developer Support again Mar 12 – Still Waiting for Review So the app has now been waiting for review for more than 3 weeks without ever entering active review. Additional information All agreements are active No messages in Resolution Center Build was not modified after submission App status remains Waiting for Review Questions Has anyone else recently experienced similar multi-week delays in the “Waiting for Review” stage? If so: Did your app eventually move to In Review without changes? Did Apple provide any explanation for the delay? Is there anything developers can do to help move the process forward? Any recent data points or experiences would be really helpful. Thanks in advance.

Hi, To ensure the issue is not caused by an error within your app or web service request, please review the Apple Pay Merchant Integration Guide. Additionally, please review the following technotes on Apple Pay: TN3173: Troubleshooting issues with your Apple Pay merchant identifier configuration TN3174: Diagnosing issues with the Apple Pay payment sheet on your website TN3175: Diagnosing issues with displaying the Apple Pay button on your website TN3176: Troubleshooting Apple Pay payment processing issues TN3206: Updating Apple Pay certificates If the resources above don’t help identify the cause of the error, please provide more information about your app or web services to get started. To prevent sending sensitive credentials in plain text, create a report in Feedback Assistant to share the details requested below. Additionally, if the error is something we need to investigate further, the appropriate engineering teams also have access to the same information and can communicate with you directly within Feedback Assistant for more information, as needed. Please follow the instructions below to submit your report. For issues occurring with your native app or web service, perform the following steps: Install the Apple Pay profile on your iOS or watchOS device. If the issue occurs on Mac, continue to Step 2. Reproduce the issue and make a note of the timestamp when the issue occurred, while optionally capturing screenshots or video. Gather a sysdiagnose on the same iOS or watchOS device, or on macOS. Create a Feedback Assistant report with the following information: The serial number of the device. For iOS and watchOS: Open Settings > General > About > Serial Number (tap and hold to copy). For macOS: Open the Apple () menu > About This Mac > Serial Number. The SEID (Secure Element Identifier) of the device, represented as a HEX encoded string. For iOS and watchOS: open Settings > General > About > SEID (tap and hold to copy). For macOS: Open the Apple () menu > About This Mac > System Report > NVMExpress > Serial Number. The sysdiagnose gathered after reproducing the issue. The timestamp of when the issue was reproduced. Screenshots or videos of errors and unexpected behaviors (optional). Important: From the logs gathered above, you should be able to determine the cause of the failure from PassbookUIService, PassKit or PassKitCore, and by filtering for your SEID or merchant domain in the Safari Web Inspector. See Inspecting Safari on macOS to learn more. Submitting your feedback Before you submit to Feedback Assistant, please confirm the requested information above is included in your feedback. Failure to provide the requested information will only delay my investigation into the reported issue within your Apple Pay website. After your submission to Feedback Assistant is complete, please respond in your existing Developer Forums post with the Feedback ID. Once received, I can begin my investigation and determine if this issue is caused by an error within your web implementation, a configuration issue within your developer account, or an underlying system bug. Cheers, Paris X Pinkney |  WWDR | DTS Engineer

Summary When an app is associated with a domain via applinks in the Apple App Site Association (AASA) file, the app's icon is displayed next to passkey entries in the iOS passkey selection UI (e.g., in Safari's sign-in dialog). This occurs even when: The AASA file does not contain a webcredentials section The passkey's relying party ID (rp.id) matches the domain, but the app has no webcredentials association The URL path of the passkey login page does not match any paths specified in the applinks configuration Environment iOS 18.6.2 iPhone 16 Pro Safari / Passkey UI via WebAuthn Steps to Reproduce Create an iOS app and register it in App Store Connect (or distribute via TestFlight) Configure the AASA file on the domain with only applinks — no webcredentials section: json{ "applinks": { "apps": [], "details": [ { "appIDs": ["TEAMID.com.example.myapp"], "components": [ { "/": "/specific-path/*" } ] } ] } } Implement WebAuthn/passkey registration on the same domain with the domain as rp.id Install the app on the device (via TestFlight or App Store) Register a passkey on the website via Safari Navigate to the login page and trigger the passkey selection UI Expected Behavior Since webcredentials is not configured in the AASA file, the passkey selection UI should NOT display the app icon next to the passkey entry. The passkey icon should be the default website favicon or a generic icon. Actual Behavior The app icon (from App Store Connect / TestFlight) is displayed next to the passkey entry in the selection UI, even though: Only applinks is configured (no webcredentials) The current page URL does not match any paths in the applinks configuration Impact In our production environment, we have a single domain serving multiple partner bank apps. The AASA file contains applinks entries for many different apps (20+ partner apps). When a user accesses the passkey login page, the passkey UI may display an app icon from one of these partner apps, which can be confusing for users — especially if the displayed icon belongs to a different partner's app than the one the user intends to use. Questions Is this the intended behavior — that applinks associations influence the passkey UI icon display? Is there a way to prevent applinks associations from affecting the passkey selection UI without removing the applinks entries? Would adding a proper webcredentials section with the correct app ID override the icon source from applinks to webcredentials? Is there a recommended approach for domains that serve multiple apps via applinks but want to control which icon appears in the passkey UI?

I’ve been waiting for over a month after payment for Apple to activate my Developer account. I’ve sent countless emails and spoke to the Support on the phone and no one is able to assist me. I’m shocked how this has been dealt with.

There's a purchase I make pretty often on a particular site and I'm trying to automate the boring parts with a macOS app. I can pull the merchant session from their ValidateMerchant endpoint. I can see the Apple Pay dialogue appear, then it will disappear with "Payment Not Completed." Is it fundamentally not possible to use someone else's merchant session in your own app? Thanks

Hi Apple Pay Team, We are building a QR-based payment platform and planning to integrate Apple Pay on the Web as a Payment Platform Integrator. Our setup: We operate a single domain (e.g., pay.example.com) where all Apple Pay transactions take place When a customer scans a merchant's QR code, our hosted page opens with the Apple Pay button We process payments on behalf of multiple merchants (receivers), each with a separate merchant ID at our payment processor We want to use a single Payment Platform Integrator ID with one set of certificates (Merchant Identity + Payment Processing) The payment processor handles sub-merchant identification and settlement to the correct receiver via card network (Visa/Mastercard) sub-merchant fields Our question: Since all transactions happen on our single domain, is it mandatory to register each sub-merchant via the Apple Pay Web Merchant Registration API (/paymentservices/registerMerchant) and use their partnerInternalMerchantIdentifier in the payment session request? Or is it acceptable to use our Platform Integrator's own merchant identifier for all payment sessions, given that: Only one domain is involved Sub-merchant identification is handled at the payment processor / card network level Our domain verification file is already hosted and verified We would appreciate clarity on the correct approach before we proceed with our integration. Thank you.

Hey everyone, I’m looking for advice from anyone who’s been through something similar. My Apple Developer account was recently terminated due to what Apple described as “concept or feature switching.” After digging into it more, I believe this happened because I made updates to my app after it was approved without submitting a new version for review. Here’s what I changed: Added a new screen (friends list) that required navigation changes Updated parts of the UI (visual improvements) Added a feature (button that helps users structure a plan) Enabled Google sign-in I did not change payments, subscriptions, or the core purpose of the app. At the time, I didn’t fully understand that these kinds of changes (especially anything affecting navigation or features) need to go through a new App Store submission rather than being updated remotely. I now understand how Apple could see this as bypassing the review process. Since then, I’ve: Stopped all over-the-air/runtime updates Made sure the app matches the last reviewed version Put a plan in place to use proper versioning for all future changes I submitted an appeal, but it was denied and my account has now been terminated. Apple mentioned I can submit a petition for reinstatement. I’d really appreciate any guidance on: Has anyone successfully gotten their account reinstated after something like this? What helped your case? Anything I should emphasize (or avoid) in the reinstatement petition? I’m trying to fully align with the guidelines moving forward and just want to handle this the right way. Thanks in advance 🙏

Hello, My Apple Developer Program enrollment has been pending for almost one month. I have already contacted Apple Developer Support via email and also called support, but unfortunately I have not received any response or update so far. On the support page it says responses usually come within 2 days or less, but it has been much longer in my case. Could someone from Apple please help check the status of my enrollment or advise what I should do next? Thank you.

Hi App Review Team, I would like to raise a concern regarding the review process for our app update (Version 2.0.0), which has now been pending for over two weeks. We completely understand the importance of the review process, but the extended delay is starting to impact our business. This update is not a major change—the app already exists on the App Store, and Version 2.0.0 mainly includes UI improvements. The core functionality remains the same as the currently approved version. Additionally, the app has been rejected multiple times with the status “Information Needed.” We have been promptly providing all the requested information each time, but the repeated cycle is significantly extending the overall review timeline. We kindly request guidance on how to move forward more efficiently, or if there is anything specific we can provide upfront to avoid further delays. If possible, we would also appreciate support in expediting the review. Any help or clarification would be greatly appreciated, as this delay is leading to business loss. Thank you.

A friend of mine said he applied for enrollment for an Organization. But during the process he did not type the code received for verifying the email. On the next day trying for enrollment there was a message of max tries. Plus he received an email with the title "developer agreement signed" How can he verify the agreement started or what can he do? He wants to know if it was succesful and he must wait or...