Overview

Hello, My app update has been in "Waiting for Review" for over 140 hours and has never moved to "In Review". There are no messages in the Resolution Center and no requests for additional information. Details: App: Suila — Video Editor Apple ID: 6781609534 Platform: iOS Version: 1.6.0 (update — 1.5.4 is live and was reviewed without issue) Build: 3 Submitted: July 27, 2026 Current status: Waiting for Review Developer Support case number: 20000125955478 This is an update to an existing, previously approved app. Agreements, Tax and Banking are all active, and all version metadata, export compliance and age rating information is complete. This is not a new developer account, and nothing has changed on my side since submission. Could someone confirm whether the submission is proceeding normally, or whether any action is required from me? Thank you and best regards, Hanpo

Hello everyone, I'm looking for advice because I'm in a very difficult situation. My Apple Developer account was suddenly closed due to an alleged fraud concern. I received only a generic email, with no specific explanation, no evidence, and no opportunity to clarify or resolve any misunderstanding before my account was disabled. We are a legitimate company that develops physical hardware devices, and our customers actively rely on our applications in their daily operations. Because of this sudden account closure, not only has our business been disrupted, but our customers are also being affected. We are fully prepared to provide any documentation Apple requires, including company registration documents, proof of business operations, product information, customer records, invoices, or any other evidence necessary to demonstrate that our business is legitimate. Has anyone experienced a similar situation and successfully had their account reinstated? If so, how long did the review process take, and is there any way to request that the case be escalated to the appropriate review team? Any advice or shared experiences would be greatly appreciated. Thank you.

So I was submitting an update for my app. It had already been approved and was on the App Store. I submit. Wait 7 days, stuck on Waiting for Review. After a week I decide to un submit and resubmit. Another 2 days. But then I got hit with a 5.6 rejection. I am told that my app was so terrible that they don’t want me to ever submit my app again or anything like it. It was so bland and useless that they considered terminating my account. But it wasn’t. This update was months in the making. I had tested it over 50 times, and enlisted the help of my friends through test flight. What‘s worse is that the support team didn’t mention anything wrong with the app itself. I have no idea what to even fix, or what triggered this severe of a response. And now I only have one week before my app is due. It’s been 13 days Apple. Upvote this if you can, and if you are a moderator or someone who can help figure out what’s going on, please help. Thank you.

Our app — a screen-time / focus app — has had no App Review activity for two weeks, and we believe the trigger was an automated Guideline 2.5.1 check that froze an otherwise actively progressing review. (This forum account is linked to the developer account in question; we can provide the App ID, bundle IDs, submission IDs, and support case numbers through any private channel on request.) Context: Jul 2–5: Our first submission (Version 1.0.0) was under active review. We went through several ordinary metadata / paywall-related iterations, and the reviewer responded within roughly 24 hours each time. Nothing related to Screen Time was raised in these human reviews of builds 9 and 10. Jul 8: After we submitted build 11 — which addressed the remaining human-review feedback — we received an automated Guideline 2.5.1 (Performance: Software Requirements) message stating that the app uses the Screen Time API but has not been submitted with the Family Controls entitlement, and that review of the submission cannot proceed. All reviewer activity stopped at that point, and there has been none since. What we verified: The Family Controls (Distribution) entitlement is granted to our account and assigned to all four bundle IDs (the main app plus its DeviceActivityMonitor, ShieldAction, and ShieldConfiguration extensions). We verified with codesign that com.apple.developer.family-controls = true is present in the code signature and embedded provisioning profile of every one of the four executables in the submitted IPA — so the entitlement named in the automated message is present in the flagged build. For context: builds 9 and 10, with an identical Screen Time API surface and identical entitlements (verified at the binary level with nm against the submitted artifacts), had been human-reviewed on Jul 2–5 with no Screen Time-related objection. We recognize those builds may simply not have reached the automated analysis stage before being superseded, so we do not draw firm conclusions from that. What we did anyway (build 12, submitted Jul 9): In case the automated check actually concerns the separate com.apple.developer.family-controls.app-and-website-usage entitlement (which we do not request and do not need), we removed every reference from our main app to the APIs associated with it: AuthorizationStatus.approvedWithDataAccess, ManagedSettings.Application.bundleIdentifier, ManagedSettings.Application.localizedDisplayName, ManagedSettings.ActivityCategory.localizedDisplayName, and ManagedSettings.WebDomain.domain. We verified with nm that none of the four executables in the build 12 IPA reference these APIs. The app does not use FamilyActivityData, DeviceActivityReport, app usage events, web usage events, or App and Website Usage data access. No automated message has appeared for build 12. What has happened since: Jul 9–14: No reviewer activity on build 12. We filed an expedited review request and opened two Developer Support cases (Jul 8 and Jul 14). No response to any of them. Around Jul 15: Hoping to clear the frozen state, we cancelled and resubmitted the same Version 1.0.0 / build 12. Around Jul 17: Filed a second expedited review request for the new submission. Jul 22 (today): The new submission has been in "Waiting for Review" since Jul 15, with no reviewer activity and no reply to either support case or either expedite request. What we are asking: Could someone check whether the Jul 8 automated flag is still attached to the app record and blocking reviewer assignment, and help get the current submission assigned to a reviewer? If the automated check flags build 12 again, could the message specify which entitlement and which binary / API references triggered it, so we can address it precisely? We can provide codesign output, entitlement plists, provisioning profile dumps, and nm symbol listings on request. Thank you.

After upgrading to iOS 27 Beta 3, iBeacon region monitoring no longer behaves as it did on previous iOS versions. Issue 1 – Never exits region After connecting to an iBeacon, I power off the beacon and move several kilometers away. The app never receives an Outside (didExitRegion) event. Even after force quitting the app, powering off the beacon, locking the screen, and turning the screen back on, iOS may relaunch the app as if it were still inside the beacon region. Is this an intentional change in iOS 27 or a bug? Issue 2 – Sometimes never enters region Occasionally, the app is not awakened when entering the iBeacon region. No Inside event is delivered. The only way to recover is to manually scan and reconnect to the beacon. Otherwise, the app is never awakened by the iBeacon again. This worked reliably on iOS versions before iOS 27.

Summary: In Sandbox, Product.products(for:) returns all 3 of my IAPs with correct JPY prices and Japanese localizations, but product.purchase() fails immediately — the payment sheet is never presented — with ASDServerErrorDomain Code=3504 (Product.PurchaseError.productUnavailable). All 3 products fail identically. Reproduction captured in the sysdiagnose attached to FB24067333: 2026-07-30 18:43:58 JST — in-app purchase() on app.negaiboshi.placement; 18:44:40 JST — OS-level test (Settings > Developer > Sandbox Apple Account > Manage > Start Transaction), same product ID. Server correlation keys from the device log: inAppBuy → AMSServerCorrelationKey HNB5UGLE72AXSMY5KY7G4NAXQY (failureType 3504); Start Transaction → FQN4Y4JOEHYBW2GIR7KPTYTB2A (AMSServerErrorCode 3766, "provided product ID or bundle ID is invalid"). Environment App: Negaiboshi — Apple ID 6794682125, Bundle ID app.negaiboshi, Team 778QPP83C4 App status: first submission in preparation (never reviewed); build 1.0 (1) on TestFlight IAPs (all "Ready to Submit" since 2026-07-27 JST, attached to the 1.0 submission): app.negaiboshi.pro.monthly (auto-renewable, ¥480, group 22264517), app.negaiboshi.placement (non-consumable, ¥720), app.negaiboshi.nightsky (non-consumable, ¥1,200) IAP base country: Japan (JPY); availability 145/175 countries Device: iPhone, iOS 26.5.2; development build from Xcode; StoreKit Configuration = None Sandbox Apple Account: (address in FB24067333), region Japan, no purchase history; signed in under Settings > Developer Storefront.current = JPN. No Screen Time restrictions. Actual error (verbatim): Error Domain=ASDServerErrorDomain Code=3504 "このアイテムは見つかりませんでした。" UserInfo={AMSServerErrorCode=3504, client-environment-type=Sandbox, storefront-country-code=JPN} TN3186 checklist fully verified, none apply (Paid Apps Agreement, banking, tax all active; bundle ID + IAP capability; signing; membership). Also tried: Sandbox sign-out/sign-in, device restart — no change. Consistent across all 3 products and relaunches. Reproduced with zero app code involved (decisive): Settings > Developer > Start Transaction with product ID app.negaiboshi.placement and bundle ID app.negaiboshi fails: "The provided product ID or bundle ID is invalid. [Environment: Sandbox]" — Apple's own OS-level tool, no third-party code. Calibration: a deliberately nonexistent ID (app.negaiboshi.zzz) yields the identical error — the backend treats my real product like a nonexistent one. A price change (¥720→¥700, "now", 2026-07-29) propagated to the sandbox metadata catalog within minutes (products(for:) returned "¥700") — purchase() still 3504. Reverted. A full base-country change (2026-07-30): Japan (¥720) → United States ($4.99) at 15:52 JST — this deletes and recreates the price schedule and is the exact operation that resolved the identical symptom in thread 839557. It propagated to the metadata catalog (auto-converted ¥800 shown in ~20 min), yet purchase() and Start Transaction still failed at 16:10 and 16:55 JST. Reverted to ¥720 at 16:59 JST. Every lever that rewrites the price schedule reaches the metadata catalog but never the commerce/purchase catalog. Timeline: the products reached Ready to Submit hours after the 2026-07-26 15:22–17:58 PDT In-App Purchases outage (Message ID 1000005803), and the failure still reproduces after the 2026-07-29 16:20–19:30 PDT emergency maintenance on In-App Purchases + Advanced Commerce API (messageId 1000005805). Peer reports with the same metadata-vs-commerce-catalog split in the same window: threads 839220, 839441, 839437, 839645, 839557. Questions: Why does purchase() fail server-side with 3504 ("item not found") while products(for:) succeeds for the same IDs in the same JPN storefront? Can someone check the sandbox commerce-catalog state of the 3 product IDs above (Apple ID 6794682125)? This looks like a server-side provisioning failure that no developer-side action can repair. Is any additional App Store Connect state required before sandbox purchases can complete for a never-yet-reviewed app?

I sent it for testing from the Choicely app. I have entered the downloaded key, opened it in Notepad, and pasted the long key; my team and distributor are right. But it seems like Apple always mentions build 1.0.2 (7) when I am actually sending (8). It'll say failed, then suddenly say ready to submit for review. So I will, and I'm waiting for review... then I get a red failed sometime later saying either certificates are not included ( I don't get all that... I'm using Windows, so I can't make them like they say I need to, and sometimes it says invalid binary...although if I look at app info and details... it says binary validated. It will make it to just before TestFlight sometimes, and sometimes it passes TestFlight... also it will say app synced successfully but failed to collect metadata. So many oddities... I don't know what to do!!

I am unable to link my new non-consumable In-App Purchase (idea_think_pro) to my draft update page (iOS 2.0.0).The product is fully configured with required screenshots and metadata, and displays the blue "Add for Review" button. However, clicking it shows the hard validation block: "Your first non-consumable in-app purchase must be submitted with a new app version."Simultaneously, the "In-App Purchases and Subscriptions" section is completely missing from my iOS 2.0.0 version page, even when no app build is attached. I have cleared all active submissions and browser caches. Please manually link Product ID idea_think_pro to App Version 2.0.0 on your database or reset my version layout cache.

My Apple Developer Program membership was terminated on July 28, 2026 under Section 3.2(f), citing “documented indications of fraudulent conduct associated with your account.” No specific action, date, app or transaction was named. I’m a solo developer with one account and two small apps. There has never been a single in-app purchase, refund or payout on the account, and I’ve never used any paid install, review or ranking service. So I genuinely don’t know what behaviour is being referred to. I replied to the termination email over a week ago and haven’t received anything back. My question is procedural rather than about my specific case: is there a channel where a terminated developer can actually get the basis for the decision, or request review? Is the appeal handled through Developer Program Support by phone, through the Contact Us link in the termination letter, or somewhere else? If anyone has been through this, I’d appreciate knowing which route produced a response. Happy to move this to the correct channel if the forums aren’t the right place — I just haven’t been able to find one that responds.

My app has now been waiting for review for 6 days, even though the submission email stated that the review would typically take up to 2 business days. App ID: 6793848581 I completely understand that App Review needs to be thorough, especially for submissions from individual developers or newly created accounts. User safety should always come first. However, our app is being submitted by a U.S. incorporated company with a team behind it. We have employees whose work depends on this launch, and every additional day of delay has a real financial impact. It makes me wonder whether there is any prioritization in the review process based on developer history or company status. Our application is ready to launch, but until it is approved we cannot publish it or generate any revenue. Meanwhile, the costs continue every day: server infrastructure, developer salaries, marketing campaigns that have to be postponed, and other operating expenses. We continue paying these expenses while having no opportunity to launch the product. I know the App Review team is busy, and I appreciate the work they do. But the growing number of developers reporting review times of several weeks is becoming very concerning. If someone from the Apple App Review team is reading this, I would sincerely appreciate it if you could review App ID 6793848581 as soon as possible. Thank you for your time and consideration.

I’m looking for about 15 additional iPhone/iWatch users to test SomataQuest, an early-stage fitness app that uses Apple Health data to help users understand their recent training, recovery, and readiness for today’s activity. Learn more: https://www.nexuspointinnovations.com/somataquest TestFlight: https://testflight.apple.com/join/BjXUh9bj I’d especially appreciate testers trying the following: Connect Apple Health and complete the initial setup Check whether the readiness score and its explanation make sense Review whether the app represents your recent workouts and activity accurately Evaluate whether the suggested training intensity feels reasonable Report anything confusing, incorrect, slow, or broken The app currently works best for people who regularly record workouts, sleep, heart-rate, or activity data in Apple Health. Feedback can be submitted through TestFlight or posted in this thread. This is an early beta, so candid feedback—especially about what is unclear or not useful—is very welcome.

Hello, I submitted my enrollment application and submitted all required documents and still haven't received any updates in days. Filed multiple support tickets and didn't receive a response to any one of them. Please take a look at this urgently as my project deadlines are stuck because of this and they have to move forward. Enrollment ID: VKXK69CKRR. Please look into it and give an update as soon as possible. Thanks

Our iOS app uploads successfully to App Store Connect and appears in TestFlight, but it crashes immediately on launch. App name: Axioma Pay Bundle ID: uk.co.axiomapay.app Distribution: TestFlight Framework: Expo / React Native Device tested: iPad via TestFlight The app installs, the icon appears, but tapping Open causes an immediate crash. One earlier build displayed this runtime message: Cannot read property 'ErrorBoundary' of undefined Crash logs show the app aborting on the React Native ExceptionsManagerQueue with SIGABRT / EXC_CRASH. We do not currently have a focused minimal Xcode sample project because this is an Expo/EAS React Native production build. We can provide .ips crash logs and App Store Connect/TestFlight build details. Can Apple help confirm whether this crash appears to be caused by: App Store/TestFlight processing, provisioning/signing/entitlements, an iOS runtime issue, or an app-side React Native JavaScript startup exception? Latest TestFlight build crashes immediately after launch.

FB24108671 I have multiple animation files and characters that all share the same skeleton definition. This is required in order for the animations to be visible in the animation library. However, you can accidentally delete the import that contains the skeleton definition, this will break every animation that depends on that shared skeleton. This is silent until you attempt to play or inspect one of the remaining animations. To my knowledge, there is no indication as to which Import contains a skeleton definition nor is there a way to lock the file so that I cannot delete it. Repro Steps: Create a new RCP3 project and save the project. Import a USD file that contains a skeletal animation. Import one or more additional USD files that contains also contain skeletal animations. Note: The skeletons must match exactly between the imported USD files or they will not be available in RCP3. Verify that all imported animations have a valid target Skeleton. This is visible by clicking on an Import and expanding the Animation Settings section in the inspector. Select the skeletal animation and view the Target Skeleton field. Optional: Import a USD file that contains a character with a matching and valid skeleton. Create a new entity and reference the imported character. Add a new Animation Library and confirm that the skeletal animations appear in the list of available animations. Select one of the animations to auto play and hit the play button to simulate the animation. The animation should play. Open terminal and navigate to your saved RCP3 project. In the root of the project run the find command to locate the skeletal definition NullTruthDeletedAnimation.realitycomposerpro % find . -name '*.tm_skeleton_definition' ./animations/Running_B.import/skeletons/root_skeldef.tm_skeleton_definition Back in RCP3 delete the Import that contains the skeleton definition. In the above case, this would mean deleting RunningB.import. Save the RCP3 project. All animations that were assigned to the same Target Skeleton will now have an empty entry in the Animation Settings section of the inspector. If you created an entity earlier that referenced the animations then none of the animations that referenced the delete skeleton will play. In the console you will see an error reporting a missing timeline. ❌ GEN RESOURCE: tm_timeline_skeletal_clip object id: 00002dab0000024c - Resource generation failed. Error: Animation Timeline is missing a target skeleton If you assigned the deleted animation to this entity then it will still have an entry in the animation library but its value will be empty. After saving the project, close and reopen the RCP project. If you created an entity earlier, then open the created entity and simulate the scene. You may see the following errors. ❌ GEN RESOURCE: tm_timeline_skeletal_clip object id: 00002dab0000024c - Resource generation failed. Error: Animation Timeline is missing a target skeleton (2) ❌ error: Trying to lookup property of NULL truth object ❌ GEN RESOURCE: tm_timeline object id: 000023a700000248 - Resource generation failed. Error: Sampled USD anim - missing TM_TT_TYPE__ANIMATION dependency The GEN RESOURCE: tm_timeline_skeletal_clip object id error appears to be due to the broken animation library entry for the deleted animation. The error: Trying to lookup property of NULL truth object error appears to be the animation referencing the deleted skeleton. If you did not create an entity then you can see the errors by doing the following: Select one of the imported animations that referenced the now deleted skeleton. In the Inspector, expand the Animation Settings section. Select the skeletal animation, you will now see the following error repeating in the console. ❌ error: Trying to lookup property of NULL truth object ❌ (previous error repeated 59 times) ❌ error: Trying to lookup property of NULL truth object ❌ (previous error repeated 53 times) ❌ error: Trying to lookup property of NULL truth object ❌ (previous error repeated 59 times) You can fix this by importing a new animation with a valid and matching skeleton or reimporting the deleted animation. However, you MUST manually assign the Target Skeleton on each broken skeletal animation. You will also need to manually remove any animation library entries for deleted animations.

I've been an Apple developer since the App Store opened. I don't develop for a living, I do this because I love it. That's it. That has always been enough. And right now, for the first time, it isn't. Waiting more than a month for a review, with no communication and no working way to reach anyone, does something to you. You stop wanting to open Xcode. You stop having ideas, because what's the point of an idea that sits in a queue for six weeks? The whole loop that makes this fun — build it, ship it, hear from users — is broken in the middle. So: thanks to the App Review team for that. You've taken the one thing that kept me building for this platform and made it feel like a waste of time. I know Apple sees review delays as a throughput problem. It isn't only that. It's a passion problem. The developers who stay through every policy change and every SDK rewrite are the ones who stay for love of the craft — and love is exactly the thing this process is grinding down. I hope someone at Apple reads this and understands what they're losing.

I am testing SFSpeechRecognizer using the en_US locale. When the iPhone Simulator’s system language is set to Japanese, SFSpeechRecognizer.isAvailable returns false for en_US, so speech recognition is unavailable. As far as I have tested, this issue does not occur on iOS Simulator 26.2 or earlier. Is this a Simulator-specific issue, or is it a behavior change that could also occur on physical devices? Has any additional setup become necessary to use speech recognition in Simulator? I then changed the iPhone Simulator’s system language to English. After doing so, SFSpeechRecognizer.isAvailable returned true for en_US. However, starting a recognition task still failed immediately with kLSRErrorDomain Code=300, “Failed to initialize recognizer.” The following error was returned: Error Domain=kLSRErrorDomain Code=300 "Failed to initialize recognizer" UserInfo={ NSLocalizedDescription=Failed to initialize recognizer, NSUnderlyingError={ Error Domain=kLSRErrorDomain Code=300 "Failed to create recognizer from=/Users/<USERNAME>/Library/Developer/CoreSimulator/Devices/<DEVICE-UUID>/data/private/var/MobileAsset/AssetsV2/com_apple_MobileAsset_UAF_Siri_Understanding/purpose_auto/ c079bfa6b8856202dc8cb2135fef3b06229ced6e.asset/AssetData/mini.json" UserInfo={ NSLocalizedDescription=Failed to create recognizer from=/Users/<USERNAME>/Library/Developer/CoreSimulator/Devices/<DEVICE-UUID>/data/private/var/MobileAsset/AssetsV2/com_apple_MobileAsset_UAF_Siri_Understanding/purpose_auto/ c079bfa6b8856202dc8cb2135fef3b06229ced6e.asset/AssetData/mini.json } } } I have not observed either of these issues on iOS Simulator 26.2 or earlier: With the Simulator language set to Japanese, the en_US recognizer does not become unavailable. When SFSpeechRecognizer.isAvailable is true, recognition does not fail with kLSRErrorDomain Code=300. Environment Xcode: 26.6 (17F113) iOS Simulator 26.5 (23F77), iPhone 17 (A3258J/A) iOS Simulator 26.4 (23E244), iPhone 17 (A3258J/A)

still no sign of the new siri no app no nothing im on the ios 27 beta 2 and iphone 15 pro max what is this apple

I had a company in the past and created a developer account for an organization. Can I switch it back to individual? Or should I create a new one and enroll again?

Dear Review Team and fellow developers Our app has not been reviewed for more than 7 days despite requesting an expedite Is this normal? Has this happened to us too? I would like to ask the review team to help us with this. Best regards

I am currently on Apple's Dev Beta V4 for iOS 27. The first version I installed was the Dev Beta V2, I am desperate to try out the new Siri AI Beta, but it's just not installing for me. I have the ability to "turn siri off" then "on again" and find I get the 2024 Apple Intelligence version fine. But if I choose to try out the new AI Beta, I'm left with "Adding support for Siri is in progress. Siri will be unavailable until the update is complete." It's been in that state for over 48 hours in Beta 4 and I'm left with the OLD OLD Siri globe from pre-Apple intelligence. Am I being too keen and just not leaving it long enough? Or is there a genuine issue at Apple's end, in regard to getting the new Siri to actually fully install?