Overview

Apple thought it was impossible. I made it possible. No server. Just an iPhone. LUMEN-JEV OS v3.0 — On-device OS using Pyto + iCloud Drive + Obsidian Architecture: Pyto runtime = server: Persistent loop, 922 tickers scanned, 502.6 ev/s, 12ms latency, sub-2ms cache iCloud Drive = bus: Writes JEV-BUS.md every 15s, shared working directory Obsidian = OS window manager: 00-JEV-DASHBOARD-main 48 nodes live Vault: 11/11 LOCKED, Factory Complete Anchor: 572b9df5e8e1f101365f8316ba7b34da4aa54ff89a2dcdb68ed20b126e8cabed Chain: REAL-EXCHANGE-PUBLIC-WS -> 8-MODULE-DEMO -> DEMO-TERMINATED -> NO EXECUTION Feed: real-public-readonly / public_ticker_only Modules (8-MODULE-v1px): WARREN-WATCHDOG, KEEPER-BOX, NODE-MODE-SYNC, VAULT-MULT, SCOUT-SCAN, SIREN-FILTER, FOCUS-SIGNAL-20K, ORACLE-PRICE-FEED, RELAY-ROUTER, AKE-ARBITRAGE, YIELD-BACK-4, MEDUSAs: 03 DYNAMIC OBSERVER-SPACE Context: Built in 33hrs over 11 nights, day job, single dad, solo dev, on iPhone only. Pyto working directory set to iCloud Drive. No Mac backend, no CloudKit function, no external server. Why this matters for iOS: Apple's sandbox says you can't run a persistent OS-like loop with live file sync on iOS. Pyto + iCloud Drive persistence proves you can. iPhone becomes the server. Proof: 48 NODES LIVE canvas PROOF CHAIN 11/11 FLAT VIEW VAULT LOCKED Jev.py V2.6 CLEAN BUS log (checked 50/100/150/200 -> 922/922 passes) Anchor hash matches zip JEV-OS-v3.0-572b9df5-40files.zip Requesting: Guidance on showcasing this as an iOS innovation + Ask Apple office hours. X proof pinned: @Activepython007

Hello Apple Developer Community and App Review Team, I am reaching out to request assistance regarding an unusually long review waiting period for our iOS application. Our current submission has remained in "Waiting for Review" since October 20, 2026, with no status changes or additional messages from the App Review team. This is our first App Store release. Our application has already gone through previous review rounds, during which we received requests from the App Review team to make corrections and provide additional information. We followed Apple's guidelines, completed the requested corrections, uploaded a new and updated build, and provided demonstration videos as requested by the App Review team. After completing these requirements, we resubmitted the application for review on October 20, 2026. Since then, there has been no visible progress. Additional actions we have taken: October 23: Submitted an expedited review request. October 27: Contacted Apple Developer Support. October 29: Submitted an additional support inquiry. Confirmed that all required agreements and business information in App Store Connect are active and up to date. Despite these efforts, our submission remains in "Waiting for Review." We would appreciate clarification from an Apple representative regarding the following: Is our submission still properly queued for review? Could there be a technical or account-related issue preventing the review from starting? Is any additional information or action required from our side? Should we continue waiting, or would canceling and resubmitting the application be advisable? We understand that some submissions may require additional review time, and we appreciate the work of the App Review team. However, after completing all requested requirements, submitting an updated build, and providing the additional materials requested, we would like to ensure that our submission is not being delayed by an issue requiring our attention. We would greatly appreciate a response from an Apple representative and any assistance in clarifying the status of our submission. Thank you for your time and support.

Title: App stuck in review for almost a month — is this normal? Hi everyone, Has anyone experienced extremely long App Store review times recently? Our app has been stuck in the review process for almost one month, and the situation is becoming increasingly frustrating. Here's the timeline: First submission: Waited approximately 2 weeks for review. Rejection: The app was eventually rejected, and we submitted an appeal message explaining to Apple Review team the reason that the feature is done by design New review: Another 2 weeks have passed, and we're still waiting for a response or resolution. That's almost 4 weeks in total, with no clear indication of when the process will be completed. We've already contacted Apple, but were ignored We've already submitted 3 times an expedite review - ignored too. I understand that reviews and appeals take time, but a month of waiting is seriously affecting our release schedule. Is anyone else experiencing similar delays? Is this the new normal for App Store reviews? Any advice on how to escalate this or get an actual status update from Apple would be appreciated. Pur app name: PauerOne Wallet Thanks!

Nasivo (Apple ID: 6786702332) – submitted Oct 12, Waiting for Review Ard & Talab (Apple ID: 6789511589) – first submitted Oct 13, resubmitted Oct 21, Waiting for Review Expedited review requested and support case opened ([Case ID]), no response yet. All agreements, banking and tax info are active. Will update this post once we hear back.

Hi, I’m building an app that counts push-ups with the phone on the floor. It currently uses ARKit and TrueDepth to measure the distance between the camera and the user’s face. I want to support iPhone Duo too, but I don’t have one. I only have an iPhone 17 Pro. I watched the camera presentation and saw that depth is supported when accessing the individual cameras. I’m trying to understand what that means for my app. Can either front camera provide continuous depth through AVCaptureDepthDataOutput, or is it only available when taking photos? Does it give actual distances in metres, or relative depth estimates? The face would usually be around 20 to 80 cm from the camera. Also, is there an equivalent camera mode on my iPhone 17 Pro that I could use to test the same approach, or would I need an actual Duo? It’s okay if counting is less accurate than with TrueDepth. I mainly need to detect the user moving down and back up reliably. Thank you!

I first put my app on review the 25th of September. After four days, I thought something was wrong so I resubmitted it 29th of September. I then learnt that was not the case. I sent a couple of emails to ask what was happening and after a long while 7 days maybe) I got a reply that my app was now expedited. On the 15th of October it had been reviewed with a rejection and a somewhat minor thing I needed to fix. I did that and resubmitted the 17th of October. It should still be expedited, as per the comms. I am now, the 29th of October still waiting. What is going on? this is the Apple ID: 6803645894

send to review 1 week ago and here is no any respond (its social app)

I’m looking for a supported way to programmatically install a specific build of an app distributed through TestFlight on a test device. My goal is to automate UI testing with XCUITest (via Appium): select a particular TestFlight build, install or update the app, and then run tests against that exact version. Is there an Apple-provided API, command-line tool, or recommended workflow for doing this? If not, is there a reliable way to automate the TestFlight app’s installation flow, including targeting a specific build? I also want to be able to automatically reinstall the app so I can isolate between multiple tests. I’m especially interested in whether this is supported on physical devices in CI and whether the answer differs for internal versus external TestFlight builds.

New organization account. Since accepting the Free Apps Agreement on Oct 27, 2026, TestFlight stopped working for all our apps: All builds are marked Expired within days of upload, without anyone expiring them. Internal testers get "The requested app is not available or doesn't exist" when installing. External submission returns HTTP 422 ENTITY_UNPROCESSABLE (no sub-code) from /iris/v1/betaAppReviewSubmissions. TestFlight worked on Oct 21–22 (builds installed by testers). Membership and agreements are active; app metadata, privacy and export compliance are complete. App Apple ID: 6825263720 Developer Support case: 103012517274 Feedback: FB25359930 Could someone from Apple check whether our team's TestFlight beta contract needs to be re-linked? Thank you.

I can't find a way to create an event trigger with a presence-based predicate ideally for a particular user at home; or at least, for all users at home. Just for the record, the rationale: I need to keep the heating on in the user's private room when he is at home, off when he is not. The idea is to have a trigger based on a low temperature event (I can do that and works all right), which would then check whether the user is at home through the predicate; if so, it would open the radiator valve (the action also tested and also working all right); if not, it would do nothing. How to? Since I could find no API to create an HMPresenceEvent for a particular user, I've set it up in the Home application, and tried to use it this way (I happen to have only one such at the moment in Home, so there's no need to check the attributes): HMPresenceEvent *pevent; for (HMEventTrigger *t in home.triggers) if ([t isKindOfClass:HMEventTrigger.class]) for (HMPresenceEvent *e in t.events) if ([e isKindOfClass:HMPresenceEvent.class]) { pevent=[e copy]; break; } NSPredicate *p=[HMEventTrigger predicateForEvaluatingTriggerWithPresence:pevent]; HMEventTrigger *et=[[HMEventTrigger alloc] initWithName:@"TEST PRESENCE" events:... endEvents:nil recurrences:nil predicate:p];alas, this raises the “NSInvalidArgumentException: Invalid parameter; (user info absent)” exception. Looks like copy loses this information somehow?!? Without appropriate public APIs one can't say :( (Since I can set up these events in the Home application freely with any kinds of action, it seems to be patently absurd not to open these APIs for privacy reasons, but that's another question, not for this ticket.) Anyway, I've tried to resort to checking for “all users at home” through pevent=[[HMPresenceEvent alloc] initWithPresenceEventType:HMPresenceEventTypeAtHome presenceUserType:HMPresenceEventUserTypeHomeUsers];where HMPresenceEventUserTypeHomeUsers is documented as “Presence of all home users”. Nevertheless, when I log out the result, I get just “any user“: [Presence-Event: type: HMPresenceTypeAnyUserAtHome, mode: HMPresenceEventActivationGranularityHome]That's unusable for me. I need to check for presence of all users (if checking for a particular one is really forbidden for some inexplicable reason). Please help. How to properly set up a trigger predicate for (ideally) a given specific HMUser, or at the very least, for a presence of all registered home users. Thanks!

Hello, Our submission has been in "Waiting for Review" since 15 October 2026 with no status change. App name: Healy 3 Apple ID: 6776578116 Submitted for review: 15 October 2026 Scheduled pre-order release: 18 October 2026 (already passed) Expedited review requested: 21 October 2026 Developer Support case: 103005950459 (23 October 2026) Current status: Waiting for Review There is nothing in Resolution Center, and we have received no requests for further information or documentation. The App Review Information section includes a demo account and video walkthroughs, as the app requires a paired Bluetooth device to complete onboarding. This is a business app, so approval is time-critical for us — and we have a further submission to follow. Could someone confirm whether this submission is progressing normally or whether it is held in an error state? If anything further is needed from us, we will provide it immediately. Thank you.

I submitted my App Store Small Business Program enrollment on October 14, 2026 and received the automatic confirmation email ("We've received your request to join the App Store Small Business Program"). Since then I have had no approval or rejection. • Paid Apps Agreement: Active • No associated developer accounts • Proceeds well below the $1M threshold • Developer Support case: 103010816726 (no reply yet)My apps are already generating sales, so the standard 30% commission is directly affecting my small business. Could someone from Apple please check the status of my enrollment? Has anyone else had a similar delay recently? Thank you!

Hello, I submitted my first app (iOS 1.0, iPad) on October 11. It has stayed in "Waiting for Review" since then with no messages in App Store Connect. So far I've checked that all agreements, tax and banking are active, and I've contacted App Review by email with no response. App Apple ID: 6804408335 Submission date: October 11, 2026 Could someone from Apple check whether something is blocking this submission, or tell me what else I should do? Thank you.

We maintain a macOS product whose installer uses custom InstallerSection plugin bundles to show configuration panes during install. Starting with macOS 27 beta 6, all of our plugins stopped loading in Installer.app — the panes never appear and the install fails because our preinstall step depends on data the panes collect. The exact same .pkg works on macOS 26.6, and per thread 842811 the same bundles were fine on 27 betas 1–4(I have tested it from beta 6 onwards). While investigating we found what looks like the underlying cause, and it's reproducible by hand. THE FINDING During a failing install, look inside the extracted plugin bundle while the Installer window is still open: ls -la /private/tmp/com.apple.installer*/.bundle/Contents/ That layout fails code-signature validation. You can reproduce the failure manually, no Installer involved: codesign -vvv "/private/tmp/com.apple.installer"*/.bundle → .bundle: Too many levels of symbolic links WHAT THE SYSTEM LOGS SHOW amfid rejects the plugin executable: /private/tmp/com.apple.installerXXXXXX/.bundle/Contents/MacOS/ not valid: Error Domain=AppleMobileFileIntegrityError Code=-420 "The signature on the file is invalid" with repeated "UNIX error exception: 62" (errno 62 = ELOOP, too many levels of symbolic links) in backtraces through BundleDiskRep::component → SecStaticCode::component → validateNonResourceComponents → staticValidateCore, and "Code failed basic validity check (error: 100062)". For a Developer ID–signed plugin the kernel then treats it as fatal: AMFI: When validating /private/tmp/com.apple.installerXXXXXX/.bundle/Contents/MacOS/: The code contains a Team ID, but validating its signature failed. mac_vnode_check_signature: ... code signature validation failed fatally check_signature[pid: N]: error = 1 The plugin is never dlopen'd and the pane never appears. QUESTIONS Is there a way to get Installer to deploy the bundle with real files — or any other workaround? Note : I have Filed via Feedback Assistant as FB24601496; this overlaps FB24415432 / thread https://developer.apple.com/forums/thread/842811, which we've cross-referenced I have experienced this issue on latest Beta 8 build also -27.0 Beta (26A5425a)

hello, what is going on with the App review? No one has answered any of my inquiries and you guys do not respond to any problems. I submitted my app on October 13 and it has been saying waiting in review since.??? Submission ID: 2de3e8b9-de0c-453a-a225-d2ceae0927ec app: Simply Help Mobile

I'm seeing a problem with custom Installer plugins on macOS 27 beta 5 and beta 6. I have a .pkg containing a custom Installer plugin. The plugin is properly signed, and if I check it manually from Terminal, codesign is happy with it and doesn't report any errors. However, when I install the package by double-clicking the .pkg in Finder, the plugin is not loaded. I see this in the logs: amfid: /private/tmp/com.apple.installer.../KLNagentInstallPlugin.bundle/Contents/MacOS/KLNagentInstallPlugin not valid: Error Domain=AppleMobileFileIntegrityError Code=-420 "The signature on the file is invalid" So apparently the plugin fails signature validation after Installer extracts it into /private/tmp, even though the same plugin passes codesign validation. This package/plugin worked on earlier macOS versions. So far, I've reproduced the issue on macOS 27 beta 5 and beta 6. Has anyone else run into this? Did anything change in macOS 27 regarding signing or validation of custom Installer plugins? I've also filed this via Feedback Assistant - FB24415432.

Hello Apple Developer Support, We need assistance with migrating Sign in with Apple users after completing an app transfer between two Apple Developer Teams. Current situation The app transfer has been completed and accepted by the recipient team. The recipient team has not yet released a new version on the App Store. Our production server, database, API domain, Bundle ID, and existing application user accounts remain unchanged. Before the transfer, we had never created a Sign in with Apple private key under the transferor team. Therefore, we do not have a previously generated .p8 private key for this app. This is not a case of a lost or revoked key. After the transfer, the app’s identifier is no longer listed under the transferor team’s Certificates, Identifiers & Profiles. When attempting to create a Sign in with Apple key under that team, we cannot select the transferred App ID as the primary App ID. Migration blocker According to Apple’s migration documentation, the transferor team must use its own client_secret to obtain a migration access token and generate a transfer_sub for each existing user. We are unsure how to obtain valid transferor-team credentials now that the App ID has moved to the recipient team and no private key was created before the transfer. Questions What is the supported procedure for obtaining valid transferor-team migration credentials in this situation? Can the transferor team create or configure a new Sign in with Apple private key for the transferred App ID after the transfer has been completed? If this cannot be done through the developer portal, can Apple Developer Support assist, or is there another supported migration method? Is transferring the app back to the original team, preparing the migration credentials and user transfer identifiers, and then transferring it again necessary in this situation? We would like to confirm whether this is required before making any further changes to the app’s ownership. We understand that the user migration process has a 60-day transfer window. We would appreciate guidance on resolving this credential issue promptly so that existing users can continue signing in to their original application accounts. Thank you for your assistance.

Hello Apple Developer Support, We need assistance with migrating Sign in with Apple users after completing an app transfer between two Apple Developer Teams. Current situation The app transfer has been completed and accepted by the recipient team. The recipient team has not yet released a new version on the App Store. Our production server, database, API domain, Bundle ID, and existing application user accounts remain unchanged. Before the transfer, we had never created a Sign in with Apple private key under the transferor team. Therefore, we do not have a previously generated .p8 private key for this app. This is not a case of a lost or revoked key. After the transfer, the app’s identifier is no longer listed under the transferor team’s Certificates, Identifiers & Profiles. When attempting to create a Sign in with Apple key under that team, we cannot select the transferred App ID as the primary App ID. Migration blocker According to Apple’s migration documentation, the transferor team must use its own client_secret to obtain a migration access token and generate a transfer_sub for each existing user. We are unsure how to obtain valid transferor-team credentials now that the App ID has moved to the recipient team and no private key was created before the transfer. Questions What is the supported procedure for obtaining valid transferor-team migration credentials in this situation? Can the transferor team create or configure a new Sign in with Apple private key for the transferred App ID after the transfer has been completed? If this cannot be done through the developer portal, can Apple Developer Support assist, or is there another supported migration method? Is transferring the app back to the original team, preparing the migration credentials and user transfer identifiers, and then transferring it again necessary in this situation? We would like to confirm whether this is required before making any further changes to the app’s ownership. We understand that the user migration process has a 60-day transfer window. We would appreciate guidance on resolving this credential issue promptly so that existing users can continue signing in to their original application accounts. Thank you for your assistance.

For an application supporting iOS 16 and later, is there a supported public API that exposes a monotonic timestamp for the original determination of a CLLocation, rather than the time it is delivered to CLLocationManagerDelegate? The requirement is to reject observations whose original acquisition age exceeds 10,000,000,000 ns at the final native transport-dispatch check. Exactly 10 seconds is allowed; 10 seconds plus 1 ns is rejected before conversion to milliseconds. This is an arithmetic boundary requirement, not an assumption that location measurements have nanosecond physical accuracy. CLLocation.timestamp is a Date for when the location was determined. Sampling a continuous monotonic clock in didUpdateLocations instead measures callback receipt. Cached observations, batched updates and delayed background delivery can separate those events. Does a public API provide either: A monotonic acquisition/determination timestamp associated with that same CLLocation; or A documented finite uncertainty bound and supported method for relating its Date timestamp to a sleep-inclusive monotonic clock at dispatch? How do the documented guarantees handle wall-clock adjustments between determination and delivery, device sleep, suspension, queued updates and process restarts? If a newer API supplies stronger evidence, what is its minimum supported iOS version? If neither mechanism is available, is there a supported request or delivery mode that establishes a documented lower bound on the original determination time and can reliably reject older cached observations? A recent callback or request by itself would not establish that relationship. I would appreciate documentation describing the guarantees, limitations or supported alternatives. I have not established that such a mechanism is impossible; this is a capability clarification, not a claim of a reproduced operating-system defect.

Hello! I have a new organization-level Apple Developer account and I'm stuck on the Tax Forms step in App Store Connect (https://appstoreconnect.apple.com/business). The system is showing me U.S. Form W-9 as the only option, but in my case filling out a W-9 would be incorrect — and I'd appreciate guidance from anyone who has resolved this. My setup: I am a non-US individual (not a US citizen, not a US resident, never lived in the US). I am the sole owner of a single-member LLC registered in the US (set up via Firstbase specifically to distribute a mobile app). For US federal tax purposes, this LLC is a disregarded entity — it's not treated as a separate taxpayer from its owner. Why W-9 is not the correct form in my case: The IRS instructions for Form W-9 explicitly state: "If the owner of the disregarded entity is a foreign person, the owner must complete an appropriate Form W-8 instead of a Form W-9. This is the case even if the foreign person has a U.S. TIN." Form W-9 also requires me to certify, under penalty of perjury, that I am a US person — which I am not. The LLC itself doesn't certify anything on a W-9 because it's disregarded; the IRS looks through to the beneficial owner, who in my case is a foreign individual. The correct form for me should be W-8BEN (Certificate of Foreign Status of Beneficial Owner — Individuals). What I've already tried: I opened two support cases 4 days ago and have not received a substantive response yet: Apple Developer Support — Case ID: 20000112974233 Ack Tax / Tax category settings — Team ID: 7YYWN3MYCY, Case ID: 19944616 My questions: Has anyone in the same situation (non-US individual, sole owner of a US single-member LLC) successfully switched the tax form from W-9 to W-8BEN inside App Store Connect? If so, how? Is there a specific path in the Business / Tax Forms section to declare the beneficial owner as a foreign individual that I might be missing? Is there an escalation channel beyond the standard support cases for tax-form issues that are blocking onboarding? Thanks in advance for any pointers.