Overview

We are trying to upload the first Apple-hosted Managed Background Assets pack for our macOS app, but Transporter rejects the asset pack ID during upload. App details: App name: DistillApp Apple ID: 6760288806 Bundle ID: cn.rkbkosp.DistillApp Asset pack ID: distill.pipeline.zh-baseline Platform: macOS Transporter: 1.4 Xcode: 26.2 macOS: 26.3.1 What we see in Transporter: Apple ID: 6760288806 App Name: DistillApp App Bundle ID: cn.rkbkosp.DistillApp No background assets found. And when we try to upload the first asset pack, Transporter fails with: 获取 Apple ID “6760288806”的资源包列表失败。 (-19243) There is an error with a URL parameter (400) Found invalid values: distill.pipeline.zh-baseline What we have already confirmed locally: The app resolves correctly in Transporter, so the Apple ID and bundle ID appear to be correct. The app Info.plist includes: BAHasManagedAssetPacks = YES BAUsesAppleHosting = YES BAAppGroupID = 8U6DAJ62JT.group.cn.rkbkosp.DistillApp.assets The asset pack manifest uses: assetPackID = distill.pipeline.zh-baseline This is intended to be the first Apple-hosted background asset pack for the app. Our understanding is that No background assets found is expected before the first successful upload, so the actual problem seems to be that Transporter/App Store Connect refuses to accept the initial asset pack ID. Questions: Has anyone seen Transporter reject the first Apple-hosted background asset pack for an app with -19243 and 400 invalid values? Does the first Managed Background Assets upload require any additional App Store Connect state beyond having BAHasManagedAssetPacks and BAUsesAppleHosting in the app? Does the app need a newly processed build in App Store Connect after enabling those plist keys before the first asset pack upload will work? Is there any known issue in Transporter 1.4 or App Store Connect for first-time Apple-hosted MBA uploads on macOS apps? If useful, I can also share the exact asset pack manifest and a redacted upload log.

My iOS app “TaskCal: Task Manager” (version 1.2.8) has been stuck in “Waiting for Review” for more than 3 weeks, and I’m not sure what else I can do at this point. I’d like to know if there’s anything wrong with my submission, or if there’s any other way to get more clarity from App Review. Here are the key dates (GMT+8): Jan 30, 2026 – Version 1.2.3 was approved and marked “Ready for Distribution”. Jan 31 – Feb 8, 2026 – I submitted version 1.2.8 multiple times. Several submissions were later marked as “Removed” in App Store Connect. Feb 9, 2026, 12:39 AM – I submitted version 1.2.8 again. This submission has been in “Waiting for Review” ever since. Today is Mar 3, 2026 (Taipei time) – The status is still “Waiting for Review” with no change. Because of this, I contacted Apple Developer Support multiple times through Contact Support. I only received one reply, on Feb 21, 2026, which said: Hello Alan, Thank you for reaching out to Developer Support about your app, “TaskCal: Task Manager.” I understand that you’re concerned. After reviewing your app’s submission history, I can confirm that your app is still in the “Waiting for Review” status as of February 8th 2026. To address your concern about the duration of the review, I’ve contacted the review team to bring this to their attention. At this time, there’s no further action required from your end. If the review team needs any additional information to complete the review, they’ll reach out to you directly. We appreciate your patience during this process. Your case number is 20000107493507. Stephanie Developer Support Since then, there has been no visible progress and no follow‑up messages. The App Review page still shows: Version: iOS 1.2.8 Status: Waiting for Review Case ID: 20000107493507 I completely understand that review times can vary, but: My previous version (1.2.3) was reviewed and approved normally. This is a relatively small productivity app with no major policy changes. It’s been over 3 weeks in “Waiting for Review” for this specific submission, with multiple earlier submissions of the same version being “Removed” without clear explanation in the UI. My questions: Is there anything I may have done wrong in the submission process (for example, causing multiple “Removed” submissions) that could block or delay this review? Is there any other official channel I can use to get more clarity beyond contacting Developer Support (which only confirmed that it’s “Waiting for Review”)? Has anyone here experienced a similar long “Waiting for Review” state recently, and if so, how was it resolved? I’m worried that there might be some issue with this build or with my account that I’m not seeing in App Store Connect. At the same time, I don’t want to keep canceling and re‑submitting if that could make the situation worse. Any advice from Apple or other developers who have gone through something similar would be greatly appreciated. Thank you, Alan

Posting this wondering anyone from App Review may be able to help. I submitted two builds for External TestFlight builds. My iOS build got approved within a day, but my tvOS version is still stuck in "waiting for review" for four days now. Wondering if there's anything I can do, perhaps remove from review and re-upload a new build or will this effectively remove me from a queue? Many thanks in advance. I'm unable to find a submission ID for this as I assume they're not available for TestFlight reviews?

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

Environment iOS Version: 26.4 Beta (Build 17E5170d) Xcode Version: 26.4 Beta Framework: AccessoryNotifications, AccessoryTransportExtension Description When implementing AccessoryNotifications.NotificationsForwarding.AccessoryNotificationsHandler, I'm unable to retrieve the URL for sourceIcon from AccessoryNotification. The file.url property throws AccessoryError error 0 with the message "unable to get file URL". Code Sample func add( notification: AccessoryNotification, alertingContext: AlertingContext, alertCoordinator: any AlertCoordinating ) { Task { if let sourceIcon = notification.sourceIcon { do { let url = try await sourceIcon.url // Throws AccessoryError error 0 let data = try Data(contentsOf: url) // Process icon data... } catch { print("Failed to get sourceIcon URL: (error)") // Error: The operation couldn't be completed. // (AccessoryNotifications.AccessoryError error 0.) } } } } Observed Behavior The sourceIcon property is present and its type is correctly reported as public.image: │ sourceIcon : present │ type.identifier : public.image │ type.description : image │ url : (error: The operation couldn't be completed. (AccessoryNotifications.AccessoryError error 0.)) Error details: Error: customError(message: "unable to get file URL") Type: AccessoryError Code: 0 Expected Behavior The file.url property should return a valid URL that allows reading the source icon image data, or the documentation should clarify any limitations or prerequisites for accessing this resource. Questions Is this a known limitation in the current beta? Are there additional entitlements or permissions required to access sourceIcon.url? Is there an alternative API to retrieve the actual image data for sourceIcon? Additional Context The same error occurs when accessing url in both describeNotification (debug logging) and sendAttachment methods contextIcon is typically nil for the notifications tested (e.g., WeChat messages) The notification metadata (title, body, actions, etc.) is correctly received

Hi! We’ve had Live Caller ID Lookup in production for a while. We’re seeing backend RPS on our /queries endpoint much higher than our expected incoming call volume. While testing with Console.app during an incoming call, it looks like iOS may still hit our service even when the caller number is already in the user’s Contacts - but I’m not 100% sure from logs alone. Can you confirm: Does iOS invoke Live Caller ID Lookup (i.e. call /queries) for every incoming call, including calls from saved Contacts? If yes, is this simply expected framework behavior? Thanks!

I am a beta tester. I successfully tested an app this week. However, a different app, by a different developer is generating the “TestFlight is unavailable. Try again” error. I have force closed, and then deleted the TF app, and restarted A16 iPad running 26.3.1 iPadOS, then redownloaded to no effect. I have worked with an Apple Senior Support advisor, and found no network, Apple ID problems on my end after troubleshooting for nearly 2 hours. The developer tried emailing me the link - didn’t work. Now, update builds by developer are now showing the same error on other beta testers iPads, - however, one tester can download the app for beta testing on an iPad Pro M4. The app will download to my phone as well as others´ phones, running current update, but not my iPad. I changed my Apple ID password, reset my network, and nothing works.

Hi, I am trying to implement a PHBackgroundResourceUploadExtension to upload backup media files to an external cloud service based on these docs: https://developer.apple.com/documentation/PhotoKit/uploading-asset-resources-in-the-background#Acknowledge-completed-jobs Creating jobs and actual uploading is working as expected, but the problem I have is in the acknowledgeCompletedJobs() function. When in this function, I am trying to access a job's resource. The resource is nil and thus has empty assetLocalIdentifier and originalFilename. Did anybody successfully implement this extension or knows, why this would happen? Because the resource of an acknowledgable job is empty, I can not match it back to my processed assets.

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

In my tabview i set a safeAreaBar topPanel, under i have contentview. That ignore safeArea.top so feed go under. What is the best Way to have a the first post in content appear under (under the bottom) if the safeareabar. I use list with foreach. Do we measure the height or is it some smart tips?

Hello, I recently paid for the Apple Developer Program membership, but I am still being prompted to complete payment as if my subscription has not been processed. I have already been charged, and the payment appears to have gone through on my end. However, my account still shows an unpaid or inactive status, and I continue to receive payment prompts. Could you please investigate this issue and confirm that my membership is active? If there is a duplicate charge or a processing error, I would appreciate your assistance in resolving it. Thank you for your help.

I am writing regarding a significant delay in the review process for my apps: Day Check: Day Counter, FastTask, Cookie Fortune, and LexiCrash. My submission for Day Check (v1.0) has been 'Pending Review' since February 9th. I provided the requested information in the Resolution Center over a month ago, but I have received no follow-up, and the red alert remains active. This is now causing a bottleneck for my entire developer account. Could you please verify if my response was received or if further action is required on my part to move these apps forward? References: Day Check: 6758218778 LexiCrash: 6758558703 FastTask: 6759599830 Cookie Fortune: 6758163442 Most concerningly, even simple updates for my existing apps, such as Cookie Fortune, have been completely ignored and have not been reviewed or accepted for over a month

I started the process of migrating my developer account from Individual to Organisation back in December. I've signed all the required agreements and provided everything that was asked of me. The account is now stuck mid-migration and I can't do anything with it in the meantime. On 20th February I was told my request had been escalated to a senior advisor. That was three weeks ago. I've heard nothing since. I'm paying for a developer membership that I currently can't use. I can't ship, I can't manage my account, I can't do anything, I'm just waiting on a process that seems to have stalled completely with no visibility on when or if it'll move. I'm not posting here to vent. I'm posting because I don't know what else to do. The escalation path I was given has gone quiet, and there's no way for me to chase it or get a status update. Is there anyone at Apple who can look into this, or at least confirm the request is still active? A case number, a timeline, anything. I just need to know it hasn't fallen through the cracks.

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?

Hello, I’m experiencing a situation with my app Waspp that I’m trying to understand. The app was approved by App Review on Feb 24, 2026 and is currently available on the App Store in the United States. However, distribution in the European Union (Belgium and France) is blocked due to the Digital Services Act (DSA) trader verification, which still shows “In Review” in App Store Connect. Some details: App Review completed: Feb 24 DSA compliance submitted: Feb 25 Status: Still “In Review” after more than two weeks Documents requested by Apple Support have already been uploaded via their secure link App availability shows “Cannot Sell” for Belgium and France The app is live and downloadable in the US Because of this, the launch of the app in the EU is currently blocked even though the app itself has been approved. My questions: Is it normal for the DSA trader verification to take this long? Has anyone experienced a similar delay with EU distribution? Is there anything else that can be done from the developer side to unblock the verification? Any feedback or similar experiences would be greatly appreciated. Thanks!

描述：低等级会员在 7 天免费期内订阅了高级会员 预期：低级会员的 7 天免费试用结束，高级会员直接扣费生效，苹果的升级通知如下： { "extra_info": { "quantity": 1, "expiresDate": 1754627893000, "purchaseDate": 1754623693000, "transactionId": "2000000979349440", "offerDiscountType": null, "originalTransactionId": "2000000979347229", // 升级前后没有变化 "subscriptionGroupIdentifier": "21729756" }, "decodedPayload": {}, "orgin_sku_name": "unlimited.minutes.per.year.v3", "payment_platform": "app_store", "decodedPayload_Renew": { "productId": "unlimited.minutes.per.year.v3", "autoRenewStatus": 1, "originalTransactionId": "2000000979347229" }, "decodedPayload_Trans": { "type": "Auto-Renewable Subscription", "price": 228000, "bundleId": "ai.plaud.ios.plaudzh", "currency": "CNY", "quantity": 1, "productId": "unlimited.minutes.per.year.v3", "signedDate": 1754623696459, "storefront": "CHN", "environment": "Sandbox", "expiresDate": 1754627293000, "purchaseDate": 1754623693000, "storefrontId": "143465", "transactionId": "2000000979349440", "appTransactionId": "704742096472000913", "transactionReason": "PURCHASE", "inAppOwnershipType": "PURCHASED", "webOrderLineItemId": "2000000107917134", "originalPurchaseDate": 1754623472000, "originalTransactionId": "2000000979347229", "subscriptionGroupIdentifier": "21729756" } } 异常 case：苹果通知升级到高级会员且继续剩余试用时间，例如：低等级会员7 天免费试用期剩余 4 天，升级到 4 天的高等级会员的免费试用，收到的通知消息如下： "extra_info": { "quantity": 1, "expiresDate": 1773109207000, "purchaseDate": 1772708455000, "transactionId": "550002836609836", "offerDiscountType": "FREE_TRIAL", "originalTransactionId": "550002832625469", //升级前后没有变化 "subscriptionGroupIdentifier": "21729756" }, "purchase_type": "upgrade", "decodedPayload": { "signedTransactionInfo": {}, "orgin_sku_name": "unlimited.minutes.per.year.v3", "payment_platform": "app_store", "decodedPayload_Renew": { "productId": "unlimited.minutes.per.year.v3", "autoRenewStatus": 1, "originalTransactionId": "550002832625469" }, "decodedPayload_Trans": { "type": "Auto-Renewable Subscription", "price": 0, "bundleId": "ai.plaud.ios.plaudzh", "currency": "CNY", "quantity": 1, "offerType": 1, "productId": "unlimited.minutes.per.year.v3", "signedDate": 1772708460325, "storefront": "CHN", "environment": "Production", "expiresDate": 1773108607000, "offerPeriod": "P7D", "purchaseDate": 1772708455000, "storefrontId": "143465", "transactionId": "550002836609836", "appTransactionId": "705330723507531368", "offerDiscountType": "FREE_TRIAL", "transactionReason": "PURCHASE", "inAppOwnershipType": "PURCHASED", "webOrderLineItemId": "550001244481732", "originalPurchaseDate": 1772507407000, "originalTransactionId": "550002832625469", "subscriptionGroupIdentifier": "21729756" } } 请问是苹果的会员试用的策略发生了变化吗

I am working on an e-commerce app (retail/marketplace) that allows users to place orders for both free and paid products. After receiving a DeclaredAgeRange API response — retrieved via the Family Controls / Screen Time framework — indicating that a user is a minor, I want to understand the recommended approach for handling payment flows. Specifically, is it necessary to block payments for users identified as minors via DeclaredAgeRange, even though our app uses server-side encrypted card processing rather than Apple In-App Purchases (StoreKit)? Any guidance on best practices or App Store policy requirements for this scenario would be greatly appreciated.

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

Hi, I am currently implementing a recurring payment feature using the Apple Pay JS API. Based on the official demo (https://applepaydemo.apple.com/apple-pay-js-api), it appears that the recurringPaymentRequest object only supports a maximum of two stages: trialBilling and regularBilling. However, our service requires a multi-stage billing model with three or more different cycles/amounts as shown below: Example Schedule: Stage 1: 2,000 JPY (2026-03-01 to 2026-04-01) Stage 2: 1,500 JPY (2026-04-01 to 2026-10-01) Stage 3: 1,000 JPY (2026-10-01 to 2027-10-01) Stage 4: 500 JPY (Thereafter) Questions: Is there any way to directly define and display three or more different billing cycles/amounts on the Apple Pay payment sheet? If the API is strictly limited to two stages, what is the Apple-recommended way to provide transparency for such complex schedules while remaining compliant with the guidelines? For instance, is it acceptable to set the final amount in regularBilling and explain the preceding stages in the billingAgreement or paymentDescription fields? I would appreciate any insights or official guidance on this. Best regards,

Hi, I have an update on my app (904057429) that has been waiting for review for over a month. I have requested an expedited review and got the message that it was approved but that was over 2 weeks ago and it's been radio silence since. I have also tried contacting support twice and received generic responses both times. I have seen other developers have app updates reviewed within 24 hours which seems to suggest there is no queue system in place so I'm not sure how this situation will be resolved. Does anyone have any suggestions for what I can do? Thanks