Overview

Last week I paid 99 USD for app developer account. Still not active. Today I paid again, hoping that it will be active. Payments were submitted. I tried to email Apple and I received emails stating they will reply in 2 days. No replies received. What is this hype about Apple if their customer care is hopeless. And why is it so difficult to contact someone from Apple even by email? Unless I have the developer account active I cannot proceed with my app

Hello, I am experiencing the same severe delays as many other developers on the forum recently. I have multiple apps ( 6759218500 and 6758253704)that have been completely stuck in the "Waiting for Review" status, with one sitting there since mid-February. I have already tried reaching out via the "Contact Us" form multiple times, but my open support case (Case ID: 102828235824) has received no follow-up or resolution. Could someone from the app review team please look into this, any assistance would be greatly appreciated, as the standard support channels seem to be unresponsive. Thank you.

Nao consigo confirmar que tenho mais de 18 anos. Nenhum cartão de crédito aceita, aparece tente mais tarde e a imagem da CNH também não é enviada aparece erro.

I am testing a consumable in-app purchase in the StoreKit sandbox and I am seeing behavior that does not seem correct on repeat purchase attempts. Product details Product ID: album.credit.v2 Type: Consumable Test environment: iOS device + StoreKit sandbox Purchase flow triggered from my Flutter app using Apple IAP What happens First purchase attempt works My backend receives the confirmation The album is granted correctly On the second purchase attempt of the same consumable, I do not get a normal new purchase flow Instead, StoreKit returns the product as restored My app then cancels the attempt because a restored transaction arrived during checkout Expected behavior Because this product is a consumable, each purchase attempt should behave like a new purchase and allow the user to buy it again. Actual behavior On the second attempt, the transaction update comes back as restored instead of a new successful consumable purchase. Relevant logs First successful purchase: [ProPurchasePage] ✅ Pay tapped. starting=false iap=true albumProd=album.credit.v2 proProd=pro.monthly [IAP] update: id=album.credit.v2 status=PurchaseStatus.restored pendingComplete=false err=null [IAP] expected=album.credit.v2 starting=true appleFlow=true [ProPurchasePage] album credit success status=PurchaseStatus.restored receiptLen=5334 [AppleIapService] Sending Apple IAP confirmation for albumId=ariie_west_pretty_girl_summer, buyerUid=PYjgu9TMCieCVDLIdTuawY5k4Ay2 [AppleIapService] appleIapConfirm response status: 200 [AppleIapService] appleIapConfirm applied for albumId=ariie_west_pretty_girl_summer buyerUid=PYjgu9TMCieCVDLIdTuawY5k4Ay2 After that, the purchase is written correctly on my side: "libraryAlbums": [ { "AlbumId": "ariie_west_pretty_girl_summer", "paid": true, "Quantity": 1 } ] Second and later attempts: [ProPurchasePage] ✅ Pay tapped. starting=false iap=true albumProd=album.credit.v2 proProd=pro.monthly [ProPurchasePage] buyConsumable (album.credit.v2) returned: true [IAP] update: id=album.credit.v2 status=PurchaseStatus.restored pendingComplete=false err=null [IAP] expected=album.credit.v2 starting=true appleFlow=true [IAP] restored arrived during album checkout — cancelling attempt Question Is this expected StoreKit sandbox behavior for a consumable, or does this suggest: a StoreKit sandbox issue, a problem with how the product is configured in App Store Connect, or a transaction-handling issue in the app/plugin layer? Also, is there any Apple-recommended handling for repeated consumable purchases when sandbox keeps surfacing a restored status?

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

Hello everyone, I’m facing an issue with my app where it's stuck at the paywall screen because my app has been approved but my subscriptions are still "Waiting for Review". This prevents me from fetching the subscription options needed to display behind the paywall. I've resubmitted my app multiple times and also created tickets and used Feedback Assistant to report this issue, but I haven't received a resolution yet. Has anyone encountered a similar situation or have any suggestions on how to resolve this? My app is live, but without approved subscriptions, users can't access its full functionality. Any advice or insights would be greatly appreciated. Thank you.

We are launching a new app with a subscription in-app purchase (IAP). The Status of the IAP is "Waiting for Review". We want to submit the app to app for review, but the section to select an IAP with the app is not appearing. According to online sources, if we submit a new app for review, without selecting the IAP that goes with it, then the app may be released in the App Store without users being able to purchase the IAP. This actually happened to us years ago and I can't remember how we got around it, but it was painful. It seems strange that Apple would allow this problem to persist for years. Why not just hire an intern to fix it? Maybe because they are too busy running around in circles at the new spaceship headquarters. Regardless, our IAP has been sitting in "Waiting for Review" status for a while now and I'm concerned it may never be approved. Any advice would be appreciated.

In my multiplatform SwiftUI document app, where should I implement undo? In the Views with Forms and Lists, Bindings, data classes or somewhere else? I am now implementing undo in Bindings and Lists, but I'm wondering if that's the right way to do it.

Hello Apple Developer Community, I’m looking for advice regarding a prolonged App Store review that has been ongoing for some time now. Our mobile application was submitted to the App Store on Feb 19, 2026 at 7:06 AM, and since then the status has remained “Waiting for Review.” There has been no progress or change in status. Because review times are typically described as taking around 24–48 hours in many cases, the length of this delay has become concerning and somewhat unclear. At this point, I’m mainly trying to understand whether this is simply an unusually long queue or if there might be another issue affecting the review. We have not received any rejection, request for additional information, or communication related to the submission. App details: Apple ID: 6759366887 Summary of the situation: • Submission date: Feb 19, 2026 at 7:06 AM • Current status: Waiting for Review • No rejection or review notes received • No changes in status since submission I understand that review times can vary depending on workload and other factors. However, remaining in the queue for this length of time without any updates makes it difficult to understand whether everything in the submission is proceeding normally. If anyone in the community has experienced a similar situation or has insight into the current review queue, I would really appreciate any guidance, including: • Whether extended “Waiting for Review” times are common recently • If there are recommended steps to follow in cases like this • Whether contacting App Review or Developer Support again would be advisable Any advice or shared experience would be very helpful. Thank you in advance.

Subject: Technical Report: Float32 Precision Ceiling & Memory Fragmentation in JAX/Metal Workloads on M3 To: Metal Developer Relations Hello, I am reporting a repeatable numerical saturation point encountered during sustained recursive high-order differential workloads on the Apple M3 (16 GB unified memory) using the JAX Metal backend. Workload Characteristics: Large-scale vector projections across multi-dimensional industrial datasets Repeated high-order finite-difference calculations Heavy use of jax.grad and lax.cond inside long-running loops Observation: Under these conditions, the Metal/MPS backend consistently enters a terminal quantization lock where outputs saturate at a fixed scalar value (2.0000), followed by system-wide NaN propagation. This appears to be a precision-limited boundary in the JAX-Metal bridge when handling high-order operations with cubic time-scale denominators. have identified the specific threshold where recursive high-order tensor derivatives exceed the numerical resolution of 32-bit consumer architectures, necessitating a migration to a dedicated 64-bit industrial stack. I have prepared a minimal synthetic test script (randomized vectors only, no proprietary logic) that reliably reproduces the allocator fragmentation and saturation behavior. Let me know if your team would like the telemetry for XLA/MPS optimization purposes. Best regards, Alex Severson Architect, QuantumPulse AI

I’m working with Reality Composer and noticed that images added directly to a scene appear significantly darker when viewed in AR. This seems different from how other objects in the scene respond to lighting, especially under varying real-world light conditions. Is this expected behavior? Are images treated with a different lighting model in Reality Composer? Is there any recommended way to get more consistent light response for image-based artworks?

Hello everyone. I want to do navigationTitle (located on the top side on MacOS system) in LiquidGlass style. now my solution look like: just black rectangle. But i want like this: opacity and LiquidGlass. Like in Photo app in MacOS. Please help me, thank you in advance. My code: struct RootView: View { @Environment(\.horizontalSizeClass) var hSize var body: some View { if hSize == .regular { DesktopLayout() .navigationTitle("title") .toolbarBackground(.ultraThinMaterial, for: .automatic) } else { MobileLayout() } } }

Looking for help with or to help with, due to the pending document enhancement, the Vibe Coders edition of cml editor. Also for more information on how to use the .mlkey whether or not my model is suppose to say IOs18 when I am planning to use it on Mac Apple Intelligence seems to think coreML is for iOS but are the capabilities extended when running NPU on the book? How to use this graph. coming in hot sorry. btw. there are 100s of feedback and crash reports sent in form me for additional info? I attached a image that might help with updating Tags

After reviewing the following Apple Technote, I have confirmed the statement below: https://developer.apple.com/documentation/technotes/tn3187-migrating-to-the-uikit-scene-based-life-cycle In the next major release following iOS 26, UIScene lifecycle will be required when building with the latest SDK; otherwise, your app won’t launch. While supporting multiple scenes is encouraged, only adoption of scene life-cycle is required. Based on the above, I would appreciate it if you could confirm the following points: Is my understanding correct that the term “latest SDK” refers to Xcode 27? Is it correct that an app built with the latest SDK (Xcode 27, assuming the above understanding is correct) will not launch without adopting the UIScene lifecycle, with no exceptions? Is it correct that an app built with Xcode 26 without UIScene lifecycle support will still launch without issues on an iPhone updated to iOS 27?

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 ?

I am trying to upload an App Preview to App Store Connect for a iphone app,I created the preview as an "App Preview". When I try to upload the app preview I get the message " your app preview is too big". The preview is 30 sec. It is 6 MB in size. MP4 format. Who know how to change my app preview

My app has been stuck on "Waiting for Review" for a long time now and there has been absolutely no progress. It’s pretty frustrating considering the review time that’s usually mentioned is around 24–48 hours. SKU: com.igos.simonchace Apple ID: 6759446309

I managed to publish the first version of my app at the beginning of February. I was lucky, I guess. On 11th of February, I added a new version which contains in app purchases. The app went "in review" a few hours later and since then ... nothing. After a week or so I sent a first email support. They claim responding in 2 working days: no response. Then I sent another one. 2 days later another one. Tried expedite review several times: nothing. Last week I finally got an answer to my first email: they apologize, blah blah. But still nothing. This is very very annoying. I longtime hesitated to purchase the Apple developer program and finally did it. Now I regret doing so. They seem they don't care about. We buy expensive Apple gear. We develop applications we cannot even install on our devices without Apple developer subscription! And they treat us like this. What is going on, Apple? Are you still there?

Hey everyone, I need to vent and also ask for some advice because I’m starting to lose my mind here. I submitted a new build for my app 10 days ago, and it has been stuck in "Waiting for Review" ever since. Not "In Review," just waiting in the queue. The App ID is 6759559007 I get that Apple has millions of apps to sift through, but come on. The App Store is a core part of the iPhone experience, and having a review team that moves this slowly feels like a bottleneck that shouldn't exist in 2026. It’s especially frustrating because: There are no rejection messages, so I know it’s not a guideline issue. I have a planned marketing push that is now completely out of sync. There is zero transparency. The status just sits there mocking me. Any advice on how to actually get a human to look at this? Should I reject the binary and resubmit to "bump" it, or is that just sending me to the back of the line? Feeling pretty hopeless here. Any insights would be hugely appreciated. Thanks

One app submitted Feb 14th, one app submitted Feb 25th. Both apps are showing "Waiting for review". Neither has been rejected, not have any action taken place. I have one previous app published (Submitted June 30th, approved 1 July), but this is the first try for both of these apps. I put in a support ticket asking status of the first app but no response. Ca n anyone here confirm that I've done the submission right and am just waiting on Apple based on the screen shot attached? For anyone from apple that wants to look into it, the app is: SKU: EX1749925971937 Apple ID: 6747297536