Overview

I'm building a planner app (React inside a Capacitor WKWebView shell). People handwrite and draw with the Pencil, and they also type longer notes on the keyboard. We want Scribble on, and we don't want to be forced into the small floating keyboard that comes with it. Ideally the user picks which keyboard they get. What I'm seeing on an iPad MU162LL, iPadOS 26.7, Apple Pencil 1: Tap a text field with the Pencil. A stray "." or "," gets typed, which looks like Scribble reading the tap as handwriting. Only the small Pencil toolbar shows up (Scribble tool, up/down chevrons, mic, return). Its menu has Pencil Settings, Minimize, Show Keyboard and Show Emoji. Show Keyboard brings up only the small floating keyboard. Pinching it open or dragging it to the bottom doesn't dock it. The menu on the keyboard's key only offers Hide Keyboard and Pencil Settings, with no Dock or Full. It stays that way until I force quit the app. After a relaunch, a finger tap gives the normal docked keyboard, until I use the Pencil in a field again. Sometimes, not every time, a finger tap after that also gets the floating keyboard. I haven't found a pattern. It isn't specific to my app. It happens in Safari on google.com's search box, on an old build of my app from before any Pencil related code, and on another person's iPad. In Notes, the keyboard docks normally after Pencil use. On the app side I've ruled out the Capacitor keyboard plugin's accessory bar handling, toggling inputmode="none", blurring and refocusing from JS, and the scene and Info.plist settings. No hardware keyboard is involved. Most threads I found end at turning Scribble off. I tried that: with Scribble off, I force quit the app and reopened it, and the state was gone. Turning it off doesn't help us, since handwriting is the point. What I've looked at so far: WebKit's WKContentView installs its own UIIndirectScribbleInteraction and is its own delegate, so I don't see a hook there. UIScribbleInteraction shouldBeginAt would suppress Scribble, but it also kills handwriting in the field. I haven't tried it on the web view yet, and I don't know whether an interaction on the WKWebView or its content view would be consulted for web content. UIScribbleInteraction.isPencilInputExpected and UITextInputContext look read only. I can detect the state but not change it. UIKeyboardLayoutGuide.followsUndockedKeyboard only helps layout. Questions: Is there a supported way for an app, or a web page in WKWebView, to ask for the docked keyboard, or to leave the Pencil input state, while keeping Scribble available? Is it intended that the state lasts for the whole app session, and that a finger tap can also get the floating keyboard afterwards? If there's no such API, is UIScribbleInteraction on the web view the intended way to opt a field out, and does it apply to web content? Feedback Assistant: [I'll file one and add the number here].

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.

I’m developing a macOS app that reads a wired controller and publishes a generic BLE HID gamepad for an iPhone. BLE communication works, but iOS does not expose the device through GameController. I’m looking for guidance on supported device-identity publication and controller-admission requirements. Environment Apple Silicon MacBookPro17,1: macOS 27.0, build 26A428 iPhone 15 Pro Max: iOS 27.0, build 24A437 Xcode 27 Peripheral implemented using CBPeripheralManager What works The iPhone can connect, perform dynamic characteristic reads, and read encryption-required characteristics using the retained pairing. It discovers the application’s HID service and reads its Report Map, HID Information, Report Reference, and Input Report. The descriptor in the iPhone’s system HID record matches the application’s remotely read report map byte-for-byte. The peripheral also receives an input subscription, although I cannot independently identify the subscribing consumer. What fails An independent GCController.controllers() observer remains empty. During the recorded HID initialization, the iPhone logs: Un-authenticated game controller device attached Start failed: 0xe00002bc IOHIDEventDriver start failed. For the same registry device, gamecontrollerd records: vendorID = 0 productID = 0 version = 0 manufacturer = 'Apple Inc.' product = '[Mac device name]' transport = 'BluetoothLowEnergy' I am not assuming that “Un-authenticated” identifies a specific authentication requirement. I would like to understand which supported admission requirement is unmet. Device Information observations The iPhone’s CoreBluetooth discovery exposes two distinct Device Information service instances: System service Observed UUID: 180A Manufacturer: Apple Inc. Model: MacBookPro17,1 No PnP characteristic exposed by successful all-characteristic discovery Application service Observed UUID: 0000180A-0000-1000-8000-00805F9B34FB Manufacturer: PS3 Bridge Model: BLE Gamepad Prototype PnP bytes: 02 00 00 01 00 00 01 The application publishes expanded Bluetooth-base UUIDs. I understand these represent the same assigned UUIDs; I am preserving the observed representations because I have not established whether every host component handles them identically. The application PnP value represents vendor-ID source 2, vendor 0, product 1, and version 0x0100. The system HID record therefore does not simply reflect that value unchanged. The duplicate-DIS layout also appears inconsistent with the unique primary DIS expected by HOGP. I have not established that this causes the driver rejection. Questions Is there a supported macOS API or architecture for publishing a coherent BLE HID device identity when macOS already exposes its own Device Information service? How does iOS select DIS/PnP information when constructing a system HID device in this arrangement? Is a generic BLE HID gamepad published through macOS CoreBluetooth a supported path to iOS GameController recognition? If so, what additional profile, identity, or authentication requirements apply? What supported diagnostics would distinguish an identity-selection problem from a separate controller-admission requirement? Available evidence I have diagnostic source, corrected per-service-instance inventories, and redacted phone logs available. I also have a small standalone CoreBluetooth publication reproducer. It is reduced and has not been validated as independently reproducing the full bridge’s controller rejection. A later connection-only observation reused an existing shared Bluetooth link and still showed zero controllers. I am not treating that as a fresh HID initialization or admission attempt. I’m seeking a supported implementation path without private APIs, Bluetooth daemon modifications, or changes to system security.

This is the third time I've posted about our app, so apologies to anyone who's seen the other two threads (links at the bottom). I honestly don't know where else to ask. Our app is NotBetting (app ID 6737483983). Since August, every review has taken about eight days: August 14 to 22, September 4 to 12, and September 12 to 20. We've got used to that. What's getting to me is what happened after the last one. On September 20 we were rejected for two things. One was 3.1.1, because they thought a "Promo code" field at sign-up unlocked subscriptions. It doesn't. It's an affiliate referral code, it's only used for attribution, and it never unlocks or discounts anything. The label was confusing, I'll give them that. The other was 5.1.1(v): they said we make people register before buying In-App Purchases that "are not account based". We explained both in detail. We also asked one simple question: which of our products do you consider not account based? The account isn't a formality for us. People post content, report and block each other, and there's a public ranking, all tied to a member's identity. Apple got back to us within a day, which I really appreciated. They said, word for word, "The 3.1.1 rejection has currently been resolved", but that they "continued to find that the app requires users to register before purchasing In-App Purchases that are not account based." They didn't say which product. We asked again. The next reply, on September 22, was just: "We appreciate your efforts to comply with the App Review Guidelines. Please resubmit the app for review in App Store Connect once any necessary adjustments have been made." That was it. No guideline repeated, no answer to our question, nothing specific to fix. So we changed what we could guess at (full name is now optional on iOS, for example) and submitted a new version, 3.3.7, on September 23. Resubmitting closes the previous thread, and everything we'd explained goes with it. It's now been waiting for four days. If it follows the usual pattern, nobody will open it for another four. A couple of things that happened in the meantime make it harder to take: The TestFlight build of the same binary was rejected under 3.1.1 on the same day, with the generic text and no feature named. We asked which feature they meant. The next day it was approved, with no explanation either way. The same version was approved and live on Google Play within hours of us submitting it to Apple. And the version our iOS users can download from the App Store is still the one from late June. I'm not complaining about being rejected. If something's wrong, tell us and we'll fix it, usually the same day. What wears you down is the loop: one issue confirmed as resolved, another with no details, a "please resubmit" that doesn't say what to change, and the only way forward is another week in the queue. If anyone from Apple sees this, I'd really like to know three things. When a thread ends with "resubmit once any necessary adjustments have been made" and no issue is named, does that mean there's no remaining objection? How are we supposed to find out which product is "not account based" if asking in the Resolution Center doesn't get an answer? And is there any way to talk to someone before resubmitting, instead of after another week of waiting? Our request for an App Review appointment back in August was declined. If anyone else has been through this and found something that actually helped, I'd love to hear it. NotBetting, app ID 6737483983, version 3.3.7 (195), submitted September 23. Earlier threads: https://developer.apple.com/forums/thread/843019 https://developer.apple.com/forums/thread/845024

Boa tarde desde já solicito a ajuda de vocês com a seguinte questão, eu solicitei a inscrição na Apple developer a inscrição foi aceita pela mesma, logo aceitei os termos o contrato conforme solicitado, então coloquei a forma de pagamento, mais deram um prazo de até 48 horas para análise e até o seguinte momento já se passaram mais de 72 horas e nada ainda. Gostaria de uma resolução.

struct ContentView: View { @State var searchText: String = "" var body: some View { TabView { Tab { NavigationStack { List { Text("Hello!") Text("Hello!") Text("Hello!") Text("Hello!") Text("Hello!") Text("Hello!") } .navigationTitle("Have a title") .searchable(text: $searchText, placement: .toolbar) .searchToolbarBehavior(.minimize) .toolbar { DefaultToolbarItem(kind: .search, placement: .topBarTrailing) } } } } } } In iOS 26, this worked no problem. In iOS 27, this leaves the search bar either unable to collapse (when pressing the close button) or in a broken state where it cannot be opened again.

Hello, My app 岩片 (YanPian, Apple ID 6800534375, bundle ID com.ajin.heartrate) was rejected on September 19, 2026 under Guideline 4.3(a) - Design - Spam. Submission ID: 69a97b70-0219-42fe-861f-ce737bc19b38, version 1.0 (202609061946). The app is original. I wrote it myself, it is the only app on my account, I have not submitted similar apps on any other account, and I have never used or bought an app template. It is a tool for lead climbers who film their climbs from a tripod far below the wall: Heart-rate overlay: pick a climbing video from Photos. Heart-rate samples recorded by Apple Watch are read from HealthKit (read-only), matched to the video by capture time, and drawn on the video with a heart-rate graph. Zoom and follow: the climber is tiny in a wide shot, so the app crops in and follows them with editable keyframes (on-device person detection). Live capture, with an optional Zhiyun CQ5 gimbal that moves only when the climber is about to leave the frame, and an optional Apple Watch companion. Everything runs on device. No account, no backend. What I have done so far: September 20: replied in App Store Connect with the explanation above. No response yet. September 29: submitted an appeal to the App Review Board. An earlier appeal got no confirmation, and I cannot find any record of it. The review was done on an iPad Air. The app is iPhone-only. Without a climbing video in Photos, the home screen only shows "New project" and "Live capture", so I understand it may look like a generic camera app. A screen recording of the full flow is attached to the submission in App Store Connect. If a specific app looks similar, I would be glad to know which part so I can change it. Could someone from App Review take a look? Thank you.

Hello Apple Developer Community, I’m experiencing a serious delay with the App Review process for my app and would appreciate any guidance from Apple or other developers who may have experienced something similar. App: İSGCEP - İş Güvenliği Asistanı Current version: 1.7.0 We have been waiting for the App Review process to be resolved for approximately 25–27 days in total. During this period, previous submissions remained in “In Review” for an unusually long time without receiving a review decision, a message, or a request for additional information. We had also previously requested an expedited review for this app, and Apple confirmed: “We’ll expedite review for İSGCEP - İş Güvenliği Asistanı. If your submission is rejected during this review, you don’t need to request another expedited review when you resubmit. Your resubmission will be automatically returned to the expedited queue.” However, the review did not progress as expected. Because the previous submissions remained stuck for such a long time, I eventually cancelled them and created a new submission for version 1.7.0. The new submission has now been submitted again. I understand that this new submission itself has not been waiting for 25–27 days; rather, the overall review process for this app has been unresolved for approximately 25–27 days due to the previous submissions becoming stuck in “In Review”. There are currently no messages in the Resolution Center and no request for additional information from App Review. Could someone from the App Review team please check whether there is anything unusual with our submission, App Store Connect account, or review queue that could be preventing the app from progressing through review? I’m not asking for approval or a guaranteed review time. I would simply like to make sure that there is no technical or queue-related issue affecting our submission. This delay is particularly concerning because we were previously informed that the app would receive expedited review and that a resubmission would automatically return to the expedited queue. Any guidance from Apple or developers who have experienced a similar situation would be greatly appreciated. Thank you.

I am testing a native Swift iPhone app that adds synthesized speech to an existing cellular call using: AVAudioApplication microphone injection permission AVAudioSession.setPreferredMicrophoneInjectionMode(.spokenAudio) AVSpeechSynthesizer CXCallObserver The audio background mode Device: iPhone 16 Pro Carrier: Vodafone Romania iOS version: [enter exact version] Both the system “Add Audio in Calls” setting and the app permission are enabled. Confirmed behavior: With the app in the foreground, the iPhone’s accessibility Auto-Answer Calls feature answers the call, and the remote caller hears the synthesized greeting. Problem: With the iPhone locked, the phone answers automatically, but the greeting does not start. Logs show ringing, connected, and ended events being processed together when the app returns to the foreground. This suggests the app was suspended. The app does not record the call or play continuous audio while waiting. Questions: Is there a supported public API that lets this app wake or execute when a cellular call connects while the iPhone is locked? Can microphone injection support this use case without keeping the app in the foreground? If supported, what audio-session configuration and background execution mechanism should be used? If unsupported, can you confirm this limitation? I can provide a minimal sample project and diagnostic logs.

Hello App Review team, Our submission has been "In Review" since September 19, 2026 (JST). The status hasn't changed and there are no messages in App Store Connect. Submission ID: 292556f9-a3ec-4c70-82aa-4e50aa71c9e9 Submitted: September 18, 2026 / In Review since: September 19, 2026 A separate Product Page Optimization submission for the same app has also been "Waiting for Review" since September 24: Submission ID: be24f6da-d8ad-4eb1-94b0-6832a7b6529c What we have done so far: Requested an expedited review on September 22 Emailed Developer Support. The reply said the review is in progress. Called Developer Support (case 102978078505) and asked them to pass a message to App Review This delay is blocking our release. If anything is needed from us, such as more information or a change to a specific item, please let us know in App Store Connect and we will respond right away. Thank you.

Hi, is there any possibility of developers being able to keep compatibility mode for a particular device model? I know it is possible for the iPad because it is regarded as a different device family from the iPhone. We wonder if it is possible for us to target just a particular model. Say for example, the iPhone Duo.

Hello App Review Team, Our iOS app has been in “Waiting for Review” since September 14, 2026, and the submission has not moved to “In Review”. App: 4ID Apple ID: 6808602401 Version: 1.0.0 Build: 21 Submission ID: e500f4b6-98e8-4381-aa8d-24b5ad39f06d Submitted: September 14, 2026 Current status: Waiting for Review App Review previously requested additional information. We provided the requested information, review access details, and all required notes, and then resubmitted the app. We also submitted an expedited review request on September 21, 2026, but as of September 23 there has been no status change and no additional communication from App Review. Our planned launch date was September 19, 2026. The submission has remained in “Waiting for Review” beyond that date, and the delay is now affecting our planned rollout and commitments to the client. There are currently no new messages or requests for information in App Store Connect, and we are not aware of any action pending on our side. Could someone from the App Review team please check whether this submission is correctly queued for review or whether it may be affected by an internal hold or routing issue? If any additional information or action is required from our side, we can provide it immediately. Thank you.

Hey guys, I am seeking advice or visibility from a DTS engineer regarding a permanent backend account block. Our corporate Apple Developer account is active and in good standing, but every macOS Developer ID notarization request fails after a 24-hour timeout with the following error: "notarization not enabled for this account" (StatusCode 7000) We have had a formal support ticket open for exactly 31 days (opened on August 27th). Every update from standard support states that it is "reviewing with engineering," but no progress has been made, and our US commercial distribution is completely blocked. DTS or Forum Monitors: Since this is an account provisioning/database issue on Apple's servers rather than a technical binary signing issue, could someone please advise on how to escalate this to the team responsible for Notary Service team provisioning? And it's always the same guy "Junghun" Answering with the same generic wait answer. A friend asked me to open a forum ticket and tag Quinn 'The Eskimo!'. I am happy to securely share our Team ID or Request UUID if an Apple employee can reach out. Thank you.

Hello, As far as I understand, RealityKit now supports 3D Gaussian Splatting through GaussianSplatComponent. I would like to ask whether there is currently a way to use 3D Gaussian Splatting data directly in Reality Composer Pro, for example by importing a .ply file containing Gaussian splats. More specifically: Can Reality Composer Pro import a 3D Gaussian Splatting .ply file? Is there a way to create or assign a GaussianSplatComponent to an entity directly within Reality Composer Pro? If this is not currently supported, is there any recommended workflow for creating a .usdz containing Gaussian Splatting data that can be opened in the Preview app on iPhone/iPad and displayed as an AR object? I tried opening the sample plant.usdz on an iPhone using the Preview app. However, the AR preview appears to be empty, so it seems that the Preview app may not currently support rendering the Gaussian Splatting content contained in that USDZ. My desired workflow would be: Gaussian Splatting .ply → Reality Composer Pro / USDZ → iPhone Preview → AR Is this workflow currently possible? If not, is there an official or recommended way to package a GaussianSplatComponent and its associated Gaussian splat data into a USD/USDZ file for AR preview on iOS? If the above functionality is not currently supported, does the development team have any plans to add or improve support for these features in future versions of Reality Composer Pro or the Preview app? Any clarification regarding the current capabilities, limitations, or future plans would be greatly appreciated. Thank you!

Hello, I'm building an iOS music quiz game. Players hear a song and answer a question about it, so the song itself is the content of the question, never background music. Each answer screen names the song and links to it on Apple Music. Non-subscribers would hear the catalog 30-second previews, and Apple Music subscribers the full songs through MusicKit (ApplicationMusicPlayer, with standard playback controls). Guideline 5.2.5 says previews "may not be used for their entertainment value (e.g. as the soundtrack to a game)", and the MusicKit terms say not to monetize access to Apple Music. Two questions: Is a preview that is the subject of a quiz question (not a soundtrack) an acceptable use for non-subscribers? Can such a game be a paid app or offer In-App Purchases, as long as the music is only previews or the player's own subscription? Any pointer to the right documentation or team would be appreciated. Thank you!

Hi, I uploaded my app to TestFlight successfully, and the build shows as Validated and Testing. The tester invitation is also accepted. However, when I try to install it from TestFlight on my iPhone, I get: “Your app could not be installed. The requested application is unavailable or does not exist.” The app is version 1.0.0 (39), with a minimum iOS version of 15.0. The app is signed with an Apple Distribution certificate and an App Store provisioning profile. Has anyone experienced this issue or knows what might cause it?

Hi, I uploaded my app to TestFlight successfully, and the build shows as Validated and Testing. The tester invitation is also accepted. However, when I try to install it from TestFlight on my iPhone, I get: “App could not be installed. The requested application is unavailable or does not exist.” The app is version 1.0.0 (39), with a minimum iOS version of 15.0. The app is signed with an Apple Distribution certificate and an App Store provisioning profile. Has anyone experienced this issue or knows what might cause it?

Hi, I’m seeing a CloudKit Production sync failure in an iOS app using SwiftData/Core Data with private CloudKit mirroring. Sync worked correctly after release, then stopped working without any new app build being released. Device logs show: CKInternalErrorDomain Code=1011 and Core Data reports that CloudKit mirroring was never successfully initialized. CloudKit Production logs also show a native PRIVATE database request failing with: USER_ERROR / BAD_REQUEST involving the internal record type: _pcs_data The Production schema, private zone, and subscription are still present. I have not reset Production or deleted any zones/subscriptions. I have already filed a Feedback Assistant report with diagnostics. Has anyone seen this pattern before? Is there a safe developer-side remediation, or is this typically an Apple-side CloudKit/PCS issue? I want to avoid any destructive action that could risk existing user data.

App Store Server API: Sandbox returns 200, Production returns 401 with the same JWT We are seeing a reproducible authentication issue with the App Store Server API for our app FYRT. Bundle ID: com.fyrt.Fyrt We performed a fresh read-only test on September 29, 2026 using our In-App Purchase key BJ5HR5GSY6. Both requests used: the same In-App Purchase key the same Issuer ID the same Bundle ID ES256 the same JWT structure 300-second token lifetime correct system time with no relevant clock skew Only the environment changed. Sandbox: HTTP 200 Apple Request ID: 458b3b32-8e0d-1404-19fe-6c92ba2ccd27 Production: HTTP 401 Apple Request ID: 193406ac-80d2-d135-8cc8-34e4ebe76fc5 The Production response does not include an additional Apple error code. The request is read-only and requests notification history. No purchase is triggered and no Production data is changed. We verified: correct Key ID correct Issuer ID correct Bundle ID ES256 signing current iat valid exp correct Sandbox and Production endpoints no environment mixing fresh JWT generation for each request no clock skew The same behavior was already reproduced on September 11, 2026. Our existing Apple Support case is: 102960057430 Has anyone seen Sandbox accept the same authentication while Production returns 401? Could this be related to Production-side provisioning, app status, team/account authorization, or the fact that the app has not yet had a version released on the App Store? Any guidance from Apple engineers would be greatly appreciated.

We are a new start up gm6.com and we are trying to get a developer account opened for our IOS app. We have been contacting support for almost two months. Does anybody have any ideas on how to get help in getting our developer account set up.