Overview

Hi everyone In SwiftUI, are there any good solutions to achieve a layout similar to Android's StaggeredGridLayoutManager for displaying a large amount of data?

Hello everyone, I'm hoping someone from the Apple Developer Support team or the community can help shed some light on my situation, as I seem to be stuck in a verification loop and unable to move my organization's enrollment forward. We are enrolling as an organization (LLC). I received an email from Apple stating they could not verify my identity and association with the enrolling entity, and they requested several specific documents: Applicant's government-issued photo ID Applicant's employment verification Excerpt from the entrepreneurial registry for LLC I successfully submitted all of these documents in English via the secure file-upload portal (https://developer.apple.com/contact/file-upload/) exactly as requested. However, we have not received any response, status update, or further instructions since the upload. The status remains pending. Here are the details for my enrollment: Enrollment ID: 6X23Y99AX3 Country: Georgia Additionally, because we are located in Georgia, the "Call Me" phone support option is not available for our region in the contact portal, which makes it incredibly difficult to get real-time assistance or escalate the issue. I have submitted an email ticket, but given the critical nature of this developer account for our business timelines, being stuck in this silent waiting period is very concerning.

We are implementing In-App Provisioning functionality for our Bank but there is always 500 Internal Server Error respond by Apple server once we tried to add card to apple wallet. Our code let request = PKAddPaymentPassRequest() request.activationData = try decodeBase64(payload.activationDataText, field: "activationDataText") request.encryptedPassData = try decodeBase64(payload.encryptedDataText, field: "encryptedDataText") request.ephemeralPublicKey = try decodeBase64(payload.ephemeralPublicKeyText, field: "ephemeralPublicKeyText") return request Because of fPanId is not required so we are not pass it to Apple server and that field generated once the card already added to wallet. Please help us investigate the issue, thanks! FeedbackId 24065847 (In-App Provisioning 500 Internel Error)

Hello everyone, I'm looking for advice regarding my Apple Developer account. My account was suddenly terminated by Apple, even though I have never knowingly violated any Apple Developer Program policies. None of my apps had been rejected for fraud or policy violations, and I never received any prior warning or notice about suspicious activity. The only explanation I received from Apple was: "Apple has good reason to believe that you violated Section 3.2(f) due to documented indications of fraudulent conduct associated with your account." However, Apple did not explain what specific activity or evidence led to this conclusion. Has anyone experienced a similar situation? Is there any realistic chance of getting a terminated developer account reinstated after an appeal? Also, does Apple ever provide more detailed information about the reason for termination, or do they usually keep the explanation general? I would appreciate any advice or shared experiences. Thank you.

We are implementing In-App Provisioning functionality for our Bank but there is always 500 Internal Server Error respond by Apple server once we tried to add card to apple wallet. Our code let request = PKAddPaymentPassRequest() request.activationData = try decodeBase64(payload.activationDataText, field: "activationDataText") request.encryptedPassData = try decodeBase64(payload.encryptedDataText, field: "encryptedDataText") request.ephemeralPublicKey = try decodeBase64(payload.ephemeralPublicKeyText, field: "ephemeralPublicKeyText") return request Because of fPanId is not required so we are not pass it to Apple server and that field generated once the card already added to wallet. Please help us investigate the issue, thanks! FeedbackId 24065847 (In-App Provisioning 500 Internel Error)

Hello everyone, I'm hoping someone from the Apple Developer Support team or the community can help shed some light on my situation, as I seem to be stuck in a verification loop and unable to move my organization's enrollment forward. We are enrolling as an organization (LLC). I received an email from Apple stating they could not verify my identity and association with the enrolling entity, and they requested several specific documents: Applicant's government-issued photo ID Applicant's employment verification Excerpt from the entrepreneurial registry for LLC I successfully submitted all of these documents in English via the secure file-upload portal (https://developer.apple.com/contact/file-upload/) exactly as requested. However, we have not received any response, status update, or further instructions since the upload. The status remains pending. Here are the details for my enrollment: Enrollment ID: 6X23Y99AX3 Country: Georgia Additionally, because we are located in Georgia, the "Call Me" phone support option is not available for our region in the contact portal, which makes it incredibly difficult to get real-time assistance or escalate the issue. I have submitted an email ticket, but given the critical nature of this developer account for our business timelines, being stuck in this silent waiting period is very concerning.

Hi everyone, My app has been sitting in "Waiting for Review" since July 16 — 18 days now, and it has never moved to "In Review". • App name: Tepa: Remote Reader • Apple ID: 6770857002 • Submission ID: 290281f3-f98c-4bc1-a6d0-07efe16eda39 • Type: new app There's nothing on my end to act on: Resolution Center is empty, no rejection, no requests for more info. I emailed App Review support 5 days ago (case 20000120461790) and haven't heard back. I'd rather not push with expedited review requests - I know the team is swamped and I don't think my case is more urgent than anyone else's here. But we have two large trade shows in September where we planned to present the app, and what worries me isn't approval itself so much as the time after it. If the review comes back with issues, I want enough runway to fix them properly and go through another round, rather than scrambling days before the events. Thanks.

Hi everyone, I'm investigating an issue related to StoreKit 1 receipt validation and would appreciate any insight from Apple engineers or developers who have encountered this before. Environment StoreKit 1 Consumable In-App Purchase iOS 16 / iOS 17 / iOS 18 (observed on multiple versions) Receipt validation performed on our server Receipt is read from the app bundle after the transaction completes Issue Occasionally, after a purchase succeeds and the transaction reaches the SKPaymentTransactionStatePurchased state, the App Receipt exists and can be decoded successfully, but the receipt contains: { "receipt": { ... "in_app": [] } } The in_app array is completely empty. As a result, our server cannot find the purchased product in the receipt and cannot complete receipt validation. Questions I'd like to understand under what circumstances Apple may return an App Receipt where receipt.in_app is empty. Specifically: Is it expected behavior that receipt.in_app can be empty after a successful consumable purchase? Could this happen if the app reads the receipt before the receipt has been updated? Is there any possibility that calling finishTransaction: before reading the receipt could cause the purchase record not to appear in receipt.in_app? If receipt synchronization is delayed, what is Apple's recommended approach? Wait and retry? Issue an SKReceiptRefreshRequest? Or validate using another mechanism? Are there any documented scenarios where Apple intentionally returns an empty in_app array? Additional Information The transaction state is Purchased. The purchase callback is received successfully. We have confirmed that the receipt file exists. The issue occurs only occasionally and cannot be reproduced consistently. Most purchases contain the expected in_app entry. Any clarification about the expected behavior of the App Receipt or recommended best practices would be greatly appreciated. Thank you!

Hello, I’m transferring an app from my individual account to my corporate developer account. I’m the primary owner of both accounts. I’m trying to transfer the users that used Sign In with Apple and this is what I did: I generated the transfer identifier for all the users that used Sign In with Apple from the database (50.000 users → 100% success rate) I’m using the transfer identifier previously generated to create the new Apple ID and private email address of the user. (40% success rate) I successfully generated new Apple ID and private email address for 20.000 users but for the other 30.000 users I cannot generate it because I get { error: 'invalid_request’ } on the migration endpoint (/auth/usermigrationinfo), even though I'm using the same request parameters as the ones that are working. I couldn’t find any difference between users that could be migrated and the users that couldn’t. It doesn’t matter if they are old users or new users. What I found is that I can generate the new Apple ID and private email address if the user signs in with Apple for the first time after the app transfer. Then I can use the “transfer_sub” that I have stored for the user to generate the new user details. The same process worked fine for another app that I transferred. Something seems to be broken only for this app on 60% of the users that used Sign In with Apple. Please let me know if you need further information Best, Cosmin

Subject: Clarification Request – Private Relay and Silent Network Verification (SNV) Hello, Context: our app uses Silent Network Verification (SNV), the standard carrier method where the network recognizes a subscriber's connection to verify their identity without needing an SMS code. When a user has iCloud Private Relay enabled, the request path changes in a way that breaks this recognition, and the user falls back to OTP instead. We're evaluating an approach where the app would handle DNS resolution itself for this specific verification request, so the request stays on a path our network can recognize — without the user having to turn Private Relay off. Before we go further with this, we'd like clarity on two things: Would this kind of app-level DNS handling, used only for this verification step, be acceptable under the App Store Review Guidelines — or would it likely be treated as working around a user's privacy setting (for example under 2.5.1, 2.5.9, or 5.1.1)? If we added an explicit, transparent consent step in the app — telling the user we're bypassing Private Relay for this one request so they can be verified without an SMS code — would that change how this is viewed? We'd rather get this in writing from Apple than build against an assumption, and we'll need to share your response with our internal IT and compliance team, so a written reply would be genuinely helpful. Happy to provide more technical detail if useful. Thank you,

so i just had 2 convo closed because somehow the message i made was unrelated

I have the typical StoreKit 2 manager class, where I check currentEntitlements for subscription. I have filed a feedback (FB22349195), I hope someone can take a look at it. func updateCustomerProductStatus() async { var activeSubscription: String? = nil // BUG: In some cases the currentEntitlements does not emit a transaction until the device is reboot for await result in Transaction.currentEntitlements { print("Found transaction: \(result)") // This print does not appear until a restart! do { let transaction = try checkVerified(result) // Skip revoked transactions if transaction.revocationDate != nil { print("Skipping revoked transaction for \(transaction.productID)") continue } // Skip expired subscriptions if let expirationDate = transaction.expirationDate, expirationDate < Date() { print("Skipping expired subscription for \(transaction.productID)") continue } // Check product type switch transaction.productType { case .autoRenewable: activeSubscription = transaction.productID default: break } } catch { print("Unable to verify transaction: \(error)") } } // Update state once after processing all entitlements self.activeSubscription = activeSubscription print("updateCustomerProductStatus() activeSubscription: \(activeSubscription ?? "nil")") } There is some unexpected behavior where the currentEntitlements does not emit a result until the iPhone device is reboot. This bug appeared in iOS 26.4 (and in the betas).

Hello Apple Developer Forum, We have implemented the Declared Age Range API exactly as described in Apple's documentation. Our implementation checks isEligibleForAgeFeatures before calling requestAgeRange, as recommended. We have been testing with different users located in Texas (US) and Brazil. However, for all users, isEligibleForAgeFeatures consistently returns false, so the Declared Age Range prompt is never displayed. We would appreciate some clarification on the following: Under what conditions does isEligibleForAgeFeatures return true? When is the Declared Age Range prompt expected to be shown? Besides the user's region, are there any additional eligibility requirements, such as whether the Apple ID has a verified payment method (credit/debit card), verified identity or address, account age or a phased rollout? Since all of our test users are in supported regions (Texas and Brazil), we expected at least some users to be eligible. However, all four test accounts consistently return false. Could you please clarify how Apple determines eligibility for the Declared Age Range feature and when developers should expect the prompt to appear? Thank you for your guidance.

Hi all, The live version of my game shipped with a broken ad unit ID: ads have been served to thousands of users for a week now without earning a single cent. Version 1.1.0 fixes it — no new features, just the corrected ad configuration — and it's been sitting in review; lately my reviews have been taking 100+ hours, and every extra day costs me around $40 as a solo indie dev. I've already submitted the "Request an Expedited App Review" form citing a critical bug fix with financial impact. Just want to make sure: is that still the right (and only) channel, or is there anything else I should do to avoid losing more days? Review ID: f59f7b94-fd9e-46f0-b2b6-627a8f0b2365 Thanks!

I paid the $99 annual Apple Developer Program membership fee and submitted my first iOS game, Pippin Plaza, for App Store review on July 21, 2026 at 9:54 PM. Apple publicly states that most app submissions are reviewed within approximately 24 to 48 hours. It has now been nearly 12 days, and my submission is still sitting in “Waiting for Review.” It has never entered “In Review.” There has been no request for additional information, no message from App Review, no explanation for the delay, and no indication that anyone has looked at the submission. I understand that review times can vary and that a first release may sometimes require additional time. However, nearly 12 days without even entering review is far beyond Apple’s publicly stated review timeframe and does not appear to be a normal delay. I contacted Apple Developer Support on July 29, 2026 through the App Review Status support category. Case ID: 20000122288868 Despite contacting support, I have still received no reply, no explanation, and no update regarding the submission. Developers are required to pay Apple $99 annually before they are allowed to distribute apps through the App Store. It is therefore reasonable to expect that a completed submission will at least enter the review process within a reasonable period, or that Apple will communicate when there is a significant delay. Is this currently considered normal for first-time app submissions? At what point should a developer conclude that a submission is stuck rather than merely delayed? Why has there been no response from Apple Developer Support since July 29, despite the submission already being delayed far beyond the stated review timeframe? I am not asking for special treatment, guaranteed approval, or an expedited review. I am asking for my completed submission to enter the review process, or for Apple to explain why it has remained untouched for nearly 12 days.

Hi everyone, My app has been stuck in "Waiting for Review" since July 22, 2026 (more than 11 days). The app is in the Productivity/Lifestyle category and only uses Sign in with Apple for authentication. It does not contain any sensitive content or unusual functionality. I have already contacted the App Review team twice and also reached out to Apple Developer Support, but I haven't received any response yet. Has anyone experienced such a long "Waiting for Review" period for a first submission? Is there anything else I can do besides waiting? Thank you!

After I found out what OpenAI did to Apple, I realized I was right—especially since Codex Relay was based on the idea of ONEWEB, an application I created to update websites initially. I have all the files and can prove it. Check Video in the link below https://x.com/xneo111/status/2080844825331482786?s=20

Hello, All of my submissions across my account have been stuck in review for many weeks, which is well outside my normal turnaround. These are apps that have historically been approved within 24 hours or 2-3 days. Those updates are time critical. Singapore MRT just updated on 12 July. We are losing installs and impressions largely because of this, especially no reason is given. App: Singapore MRT Map Route Apple ID: 536957287 / Version: 3.0.1 App: Singapore MRT Map Route(Pro) Apple ID: 475976737 / Version: 3.0.0 App: Epic Cards Battle Apple ID: 1003611640/ Version: 2.6.3 On my side everything appears complete: metadata, build, review notes, demo account credentials, and all agreements in Agreements, Tax, and Banking are accepted. There are no messages in Resolution Center and App Store Connect shows no action required from me. I have contacted Developer Support but have not received a actual response. Could someone please confirm whether these submissions are correctly queued, or whether something is blocking them that requires action on my side? Thank you.

Hello everyone, I hope you're doing well. I'm looking for some guidance regarding the Apple Developer account conversion process. Nearly one month ago, we submitted a request to convert our Apple Developer account from Individual to Organization. We also contacted Apple Support and provided the required information. Since then, we have been patiently waiting, but we have not received any updates or feedback via email or through the support process. A few weeks ago, we also created a post here on the Apple Developer Forums hoping to receive some guidance, but unfortunately, we have not received any response there either. At this point, we would simply like to know: Is it normal for the conversion process to take this long? Has anyone experienced a similar delay? Is there anything else we should do, or should we continue waiting for Apple's response? We understand that these requests may require additional review, and we truly appreciate the work of the Apple team. We would just be grateful for any update or advice from the community or Apple staff. Thank you in advance for your time and assistance. Any suggestions or shared experiences would be greatly appreciated. Best regards.

Hello, I'm reaching out because I haven't received any response from App Review for about a week, and I'm hoping someone can help me check on the status of my submission. App: Apple ID 6782845619, version 1.2 Submission ID: 2722eda8-9429-44d2-9971-092f4ed28ffb Rejection: Guideline 4.3(a) — Design (Spam) I have already taken the corrective steps suggested in the rejection message (I withdrew the duplicate prototype app from review and removed it from all 175 storefronts, so there is no overlap anymore), and I replied to App Review in App Store Connect with this information. However, it has now been about a week with no reply. I understand the review team is very busy, and I truly appreciate their time. I'm not trying to dispute the review process itself — I would simply be grateful if someone could check whether my reply has been received and is being looked at, or advise me on the best way to get a status update. Thank you very much for your help.