Overview

This is my first time submitting an app for notarization. Both submissions have been stuck "In Progress" with no logs available. Body: This is my first time submitting an app for notarization. Both submissions have been stuck "In Progress" with no logs available. Submission 1: ID: 43ea68c1-5291-42c6-b0e1-3cacab4ca01a Submitted: 2026-04-09T02:05:34Z Status: In Progress (15+ hours) Submission 2: ID: 12ea49a0-64cf-495e-af7e-9aad5aabe30f Submitted: 2026-04-09T17:06:51Z Status: In Progress (1+ hour) Details: Team ID: PWTWN9N25D App: Native macOS SwiftUI app (arm64), ~84 MB zipped Signed with Developer ID Application certificate, Hardened Runtime enabled All embedded helper binaries individually codesigned with Hardened Runtime codesign --verify --deep --strict passes Submitted via xcrun notarytool submit with --keychain-profile notarytool log returns "not yet available" for both Apple System Status shows all services available

When running top-level async code in Swift Playgrounds, the LLDB RPC server crashes. For example, when running the following code from Concurrency section of The Swift Programming Language book: func fetchUserID(from server: String) async -> Int { if server == "primary" { return 97 } return 501 } let userIDs = await withTaskGroup(of: Int.self) { group in for server in ["primary", "secondary", "development"] { group.addTask { return await fetchUserID(from: server) } } var results: [Int] = [] for await result in group { results.append(result) } return results } print(userIDs) Xcode reports that the LLDB RPC server has crashed. The Swift Playground app reports “There was a problem running this playground.” However, in the case of the Swift Playground app, results are populated as expected. For example, the console shows “[97, 501, 501]”. Xcode does not print any results in the console. Tested with Xcode 26.4 (17E192) and Swift Playground Version 4.7 (2088). Wrapping the async code in a Task {} resolves the issue. Running this code in a standalone Swift file produces the expected result without an error. FB22416465 From the analytics report, attached in the feedback report, but in case it helps others identify the same issue in their crashes: Triggered by Thread: 26 RPC packet thread for client tid 013af238 (20640312) Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Subtype: KERN_INVALID_ADDRESS at 0x00000000000005a8 Exception Codes: 0x0000000000000001, 0x00000000000005a8 Termination Reason: Namespace SIGNAL, Code 11, Segmentation fault: 11 Terminating Process: exc handler [64943] VM Region Info: 0x5a8 is not in any region. Bytes before following region: 4296211032 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL UNUSED SPACE AT START ---> __TEXT 100130000-1003b8000 [ 2592K] r-x/r-x SM=COW /Applications/Xcode-26.4.0-Release.Candidate.app/Contents/SharedFrameworks/LLDBRPC.framework/Versions/A/Resources/lldb-rpc-server

Hello Apple Developer Support Team and Community, I am writing to request urgent assistance regarding my Apple Developer Program enrollment, which has been stuck on "Pending" for 11 days with no update or response. 📋 My Details: • Order Number: D009571392 • Invoice Number: MC62612013 • Invoice Date: April 4, 2026 • Amount Charged: $99.00 (Credit Card confirmed) 📌 Current Situation: • Payment was successfully processed and charged to my card on April 4, 2026 • I received the Order Acknowledgement email from Apple Developer Relations • I received the official Apple Invoice (#MC62612013) • My developer.apple.com/account still shows "Pending" status with the message "Subscribe your membership" • I have contacted Apple Developer Support multiple times via the contact form but have received no response whatsoever ✅ What I have already verified: • Two-Factor Authentication is enabled on my Apple ID • I have checked my spam/junk folder daily – no additional emails from Apple • I am NOT clicking "Complete your purchase" again to avoid being charged twice This delay is blocking my development work entirely. I cannot access App Store Connect, create certificates, or use any Developer Program features. Could someone from the Apple Developer team please investigate and manually activate my membership? I am happy to provide any additional documentation required. Thank you very much for your help. Adel Aidoudi

Hi everyone, I’m currently researching Apple Watch pairing behavior and diagnostic logging across different setup modes. I can reliably trigger a co-sysdiagnose on an Apple Watch when it is paired in a normal standalone / standard configuration. In that case, the expected co-sysdiagnose archive appears on the paired iPhone. However, in a Family Setup / managed account scenario, behavior is different: The watch provides the expected haptic feedback after the sysdiagnose button combination But no co-sysdiagnose archive appears on the paired iPhone afterward The same hardware behaves differently depending on pairing/account configuration My question is: Is co-sysdiagnose collection, transport, or availability intentionally different for Family Setup / managed Apple Watch devices? For example: Are logs stored elsewhere? Is transfer to the organizer iPhone restricted? Is co-sysdiagnose unsupported in Family Setup mode? Are additional conditions required, such as Wi-Fi, charging state, unlocked devices, or a longer delay? I may be missing something obvious, but I have not found documentation describing this difference. If this is expected behavior, I’d really appreciate a pointer to the relevant documentation. Thanks a lot!

Hi — I submitted ClaudeScope (a utility app, Bundle ID io.sandwichlab.claudescope, Apple ID 6761888911) for review on April 12, 19:40 PDT. It's been in "Waiting for Review" for over three calendar days and I just want to confirm there isn't a metadata issue quietly blocking the queue. Details: App name: ClaudeScope Bundle ID: io.sandwichlab.claudescope Apple ID: 6761888911 Version 1.0.0 (build 2) Current status: Waiting for Review No rejection or reviewer message in Resolution Center Happy to provide additional information if needed. Thanks in advance for any pointers.

I am having constant issues with the IAP on my app. I have now, after several review rejections, created a brand new non-consumable in-app purchase product and updated the submitted build to use the new product identifier. We also updated the paywall so it no longer loops and instead shows fallback messaging plus manual retry/restore options when pricing is unavailable. However, in TestFlight and sandbox testing, StoreKit is still not returning the product details, so no localized price is available to display. This suggests the in-app purchase is not being returned by Apple’s review/sandbox environment rather than a client-side UI issue. Has anyone else had this issue and of so how did they resolve this?

I have created a simple AppleScript that makes a folder named with today’s date. For many years, it has worked fine except: If I run the script (from a script app in the menu bar), then dump files into the folder, then change the colored “Tag” on the folder, I get a Finder error - An unexpected error occurred (error code -8076) - and I have to force-quit the Finder to complete the color tagging. If it change the tag before dumping the files, no error occurs. (Please hold the “Doctor, it hurts when I do this …” jokes.) This error has persisted through many macOS major iterations, including Tahoe 26.4.1. Prolly a Finder bug, but not sure. Here’s the source, for anyone interested. set dateStr to getDate() --display dialog dateStr tell application "Finder" activate try --set thisFolder to (the target of the front window) as alias set thisFolder to (the target of the front window) as string make new folder at thisFolder with properties {name:dateStr as string} on error errMsg display dialog "ERROR: " & errMsg end try end tell on getDate() set theDate to current date set theYear to year of theDate as string set theNewYear to third character of theYear & fourth character of theYear set theMonth to month of theDate as number as string if length of theMonth = 1 then set theMonth to "0" & theMonth as string end if set theDay to day of theDate as string if length of theDay = 1 then set theDay to "0" & theDay as string end if return theNewYear & " " & theMonth & " " & theDay as string end getDate

I'm posting here after 8 months of back-and-forth with Developer Support (case 102685152651) because I've exhausted that channel and need to know if others have experienced this or if any Apple engineers can advise. The issue: When a user types "Dabah" — the exact name of my app — the App Store autocorrects/redirects to "Sabah." My app does not appear in those results. It only appears when the user searches "Dabah recipes." This means users who know the app by name cannot find it unless they add a secondary keyword. What makes this clearly a system-level bug, not a ranking issue: The same behavior occurs inside Apple's own Developer Marketing Tools portal. Searching "Dabah" returns only Sabah-related apps. Searching "Dabah recipes" finds my app immediately. This is not a user-facing algorithm issue — it's happening in an internal Apple tool. "Dabah" is a unique, uncommon word with no major competing apps. There is no legitimate reason an exact-name search should be overridden. The app has been live on the App Store since mid-2024, is properly indexed (it surfaces on keyword searches), and has "Dabah" listed as a keyword. The problem is specifically in the autocorrect/normalization layer treating "Dabah" as a misspelling of "Sabah." I've submitted screen recordings demonstrating both behaviors. Developer Support has confirmed my ticket is with the engineering team, but I've received no resolution or timeline in 8 months. Has anyone else encountered autocorrect overriding an exact app name match? Is there a known path to escalate search indexing bugs beyond the standard Developer Support channel? App: Dabah (id6745241806) Category: Food & Drink

Hi, my individual Apple Developer Program enrollment is pending since April 10, 2026. Payment of $99 was charged and confirmed on my credit card. Account still shows 'Pending' with 'complete your purchase now' message. I have submitted support request with no response. Order number: W1322582048. Please advise; many thanks.

Hi folks, in my application I write some logs over debugPrint or directly over print. The application is already distributed and some part of functionality failed with application traceback. I would like to ask user for providing logs from the App. Is it possible to get those logs? Thanks Petr

I am trying to use SpeechDetector Module in Speech framework along with SpeechTranscriber. and it is giving me an error Cannot convert value of type 'SpeechDetector' to expected element type 'Array.ArrayLiteralElement' (aka 'any SpeechModule') Below is how I am using it let speechDetector = Speech.SpeechDetector() let transcriber = SpeechTranscriber(locale: Locale.current, transcriptionOptions: [], reportingOptions: [.volatileResults], attributeOptions: [.audioTimeRange]) speechAnalyzer = try SpeechAnalyzer(modules: [transcriber,speechDetector])

Hello, I am currently experiencing an issue during the App Review process related to a third-party payment integration using Toss Payments. Our app loads a payment widget from an external script hosted at: https://js.tosspayments.com/v2/standard In our local and production environments, the payment module works without any issues. However, in the App Review environment, the script appears to fail to load or initialize properly, resulting in an "Unknown Error" during payment widget initialization. We suspect that the App Review environment may have network restrictions or firewall rules that block or limit access to this external CDN (AWS-based), preventing the script from being fetched. We have already: Verified that the script loads correctly in all non-review environments Submitted a video demonstrating the normal payment flow Contacted the payment provider, and they confirmed that there are no IP blocks or restrictions on their side My questions are: Does the App Review environment impose restrictions on external CDN domains or third-party scripts? If so, what is the recommended approach for handling payment SDKs that rely on external script loading? As a temporary workaround for review purposes, would it be acceptable to: Bypass the actual payment SDK Replace it with a mock or simplified flow (e.g., tapping the payment button immediately proceeds to a success screen) Restore the real payment integration after approval? We want to ensure compliance with App Store guidelines while also resolving this review-specific issue efficiently. Any guidance or similar experiences would be greatly appreciated. Thank you!

We’re planning to distribute our app outside of TestFlight because our testing period is expected to exceed the 90-day limit. Since we have an Apple Developer account, we’re considering using either Ad Hoc distribution or direct installation (debug/development builds) for longer-term testing. I have a few questions regarding this approach: Ad Hoc Distribution Validity What is the effective validity period of an Ad Hoc build? We’re aiming for long-term testing (4-5 months) and would like to avoid unexpected expiration—are there any constraints we should be aware of? Development/Debug Build Expiry & Limitations If we distribute the app using a development (debug) build via provisioning profiles, what is the expiration timeline? Are there practical limitations (e.g., device limits, performance differences, or provisioning renewal requirements) that could impact extended testing? Potential Complications & Best Practices Are there any issues we should anticipate when using these distribution methods for long-term testing? For example: Provisioning profile or certificate expiration Device registration limits Any policy or compliance considerations with Apple We’d appreciate any guidance or best practices for managing long-term testing outside of TestFlight while staying within Apple’s guidelines.

I’m running an experiment around generating and importing .vcf files on iOS and wanted to sanity check expected behavior with others who may have explored this deeper. Goal Programmatically generate a vCard (v3.0) that, when imported into iOS Contacts, includes: Standard fields (name, phone, email, organization, etc.) Contact photo (PHOTO) Social profile (e.g., LinkedIn via X-SOCIALPROFILE) What I tested I tried to eliminate formatting issues by using iOS itself as the source of truth. Steps: Created a new contact directly in iOS Contacts Added name, phone, email Added a contact photo Added a social profile (LinkedIn) Exported that contact as a .vcf Deleted the contact from the device Re-imported the exported .vcf Result Core fields (name, phone, email, etc.) are restored correctly Contact photo is NOT restored Social profile is NOT restored as a native social entry This happens even though: The exported .vcf clearly contains a PHOTO field The exported .vcf includes X-SOCIALPROFILE;type=linkedin:... Additional testing I also generated my own .vcf files that closely mirror the structure produced by iOS (field order, encoding, etc.), and observed the same behavior: Photo does not reliably import Social profiles do not appear as native social entries in Contacts Question Is this expected behavior on iOS? More specifically: Are PHOTO fields intentionally ignored (or restricted) during .vcf import? Is X-SOCIALPROFILE supported for import, or only used internally/exported by Contacts? Is there any supported way to programmatically create a contact with: a photo social profile entries via .vcf import? Current understanding Based on testing, it appears that: iOS may export more data than it will accept on import Some fields (like social profiles and possibly photos) may only be fully supported when created via native APIs (e.g., Contacts framework) rather than .vcf Would appreciate confirmation or any documentation pointers if this is known behavior or if there are recommended alternatives. Closing thought If this is by design, it would be helpful to know which vCard fields are officially supported for import vs. export on iOS, since the current behavior is not entirely symmetric.

Hi, I'm using a TabView and for a given case I wish to have the icon of the Tab animated by symbolEffect to signify a state. The symbolEffect however doesn't seem to have an effect when used on a tab's label image. Is it really not possible? Tab(value: .hello) { EmptyView() } label: { Image(systemName: "hand.wave.fill") .symbolEffect(.wiggle, options: .repeating) } I still wish to use the TabView because it's amazing.

Hi everyone, I am facing an issue while configuring an App Clip in App Store Connect, and I am unable to proceed due to a UI crash. Issue When I navigate to the App Clip section under my app version and click on the Subtitle field, the page immediately shows: “We can't process your request.” I am unable to enter any metadata for the App Clip experience. Console Error Previously, I observed the following error in the browser console: TypeError: Cannot read properties of undefined (reading 'appClipDefaultExperience.id')

I am currently migrating an app from the classic UITableViewDataSource to UITableViewDiffableDataSource. In certain complex cases, I find myself needing to toggle between the UITableViewDataSource and UITableViewDiffableDataSource on a single UITableView instance. Apple's official documentation for UITableViewDiffableDataSource contains a strict warning: "Do not change the dataSource on the table view after you configure it with a diffable data source. If the table view needs a new data source after you configure it initially, create and configure a new table view and diffable data source." I’m seeking clarification on: Internal State: What specific UIKit caching or internal state is corrupted if we nil out the diffable source and re-assign a classic one? Background Processes: Does the background diffing engine pose a risk (race conditions/crashes) if the source is swapped while a diff is calculating? The "Safe" Reset: If swapping is truly necessary, is there a verified cleanup sequence (e.g., clearing snapshots first) that avoids the need to recreate the UITableView entirely?

Dear Developer, We are writing to notify you that the Ministry of Industry and Information Technology (MIIT) has identified your app as in violation of the Regulation on Personal Information in Mobile Apps. If your app is not compliant by April 20, 2026, MIIT will find your app to be illegal in China, and demand that Apple remove it from the China App Store. The App Review Guidelines require apps to comply with all legal requirements in any location where they are offered. Legal Apps must comply with all legal requirements in any location where you make them available (if you’re not sure, check with a lawyer). We know this stuff is complicated, but it is your responsibility to understand and make sure your app conforms with all local laws, not just the guidelines below. And of course, apps that solicit, promote, or encourage criminal or clearly reckless behavior will be rejected. We ask that you refer to the directions included in the document attached to this message. If you have any questions, we advise you to get in touch with MIIT within 24 hours of this notice by submitting your feedback via https://app.caict.ac.cn/. Thank you for your prompt attention to this matter. Best regards, App Review Message Attachments: Directions.docx

Hello, Our application has been stuck in the "In Review" status for 17 days now, and we are looking for guidance on whether this is a known technical stall or an extended policy audit. The Issue: The app moved from "Waiting for Review" to "In Review" on March 25th. Since then, there has been no change in status and no messages in the Resolution Center. App ID: 6753868146 Thanks

Hello, I have a question regarding Apple's policy on third-party SDK signatures. I have reviewed the official documentation here: https://developer.apple.com/support/third-party-SDK-requirements/ Our app is developed in the following environment: Minimum Target: iOS 15 Xcode: 26.2 Engine: Unreal Engine 4.27.2 We are integrating the Firebase SDK into our project. However, we are experiencing app crashes caused by an issue within the GoogleAdsOnDeviceConversion.xcframework included in the Firebase SDK (related to a memory optimization issue in UE4). According to an official response from the Firebase team, this crash can be resolved by wrapping the Firebase SDK in a dynamic XCFramework. We have confirmed that this solution does indeed fix the crash. The problem is that wrapping the Firebase SDK in a custom dynamic XCFramework removes all of the original Firebase SDK signatures. The documentation on third-party SDK signatures, which I referenced earlier, states that a signature is required for the Firebase SDK, and this requirement also applies when repackaging it. This leads me to the following questions: Question 1: When we wrap and repackage the Firebase SDK, is it mandatory for the resulting XCFramework to still include the original Google LLC signature? Question 2: To resolve the crash, we intend to use the Firebase SDK by wrapping it in our own dynamic XCFramework (e.g., FirebaseWrapper.xcframework). When we do this, the resulting XCFramework loses the Google LLC signature, and consequently, the final built IPA's signature list does not contain any Firebase-related signatures. Will this be a reason for rejection during App Store review? Question 3: If we wrap the Firebase SDK in a dynamic XCFramework and then sign it with our own developer certificate, would this be a reason for rejection during App Store review?