Overview

I have an iOS (iPhone/iPad) and a Mac version of my app. When I create a new product page optimization test, on the next page, where it shows Treatment A, I only see the iPhone media there. If I click on "View All Sizes in Media Manager", I can then see the iPad media in the Media Manager. But there are two issues: (1) There's no Mac media in the Media Manager. So would I need to submit a new build just to update media for Mac? (2) There's no save button in the Media Manager, and when I return to the product page optimization dashboard, it still only shows iPhone media. Should I presume that any changes to iPad media in the Media Manager are counted in the test and any subsequent application to original product pages?

TLS + connectReceiver connect successfully, but the sender fails to negotiate the immersive video stream: VCVideoRuleCollectionsImmersiveVideoMac initSupportedPayloads: Empty supported payload: supportsMVHEVCEncode=0 Failed to create immersive video rules! AVCMediaStreamNegotiator … Failed to init … for mode=15 hardwareSettingsModeFromFeatureListStringType: Unexpected featureListStringType=0 connectReceiver failed … GKVoiceChatServiceErrorDomain 32032 Host: MacBook Pro M3 (Mac15,3), macOS 26/27. VTIsStereoMVHEVCEncodeSupported() returns true, and I set preferredVideoWidth/Height/FrameRate. Is immersive MV-HEVC encode in this API gated by an entitlement, a specific M-series tier (Pro/Max), or a known beta issue? What populates the "immersive video rules" feature list?

I'm creating an APP for the first time in Xcode, I have a part of a place search on a map, it has a card very similar to the iPhone map card, I want it to move to the left when it's horizontal and position itself there to see the information that slides up and down. What should I write in the code?

Updating an App for the first time since 2011. Build, Analyze, Archive all successful. Automatically Manage Signing checked. Validation fails with 90286 - Invalid code signing entitlements, and 91130 - Invalid Provisioning Profile dozens of times after tweaks, clean builds, trying manual signing (thought I was done with that), etc. For 90286 it seems my Developer ID , e.g. 346JXXXXX (not Team ID, QZ99XXXXX) is the prefix for the bundle ID, com.company.app-name and that generates the error? For 91130 it's invalid "com.apple.application-identifier" which I assume is the same issue with a Developer ID instead of a Team ID. The original version of the app was QZ99XXXXX.com.company.app-name. I even changed the bundle identifier in Xcode to that, and got this: App Record Creation failed due to request containing an attribute already in use. The app name you entered is already being used for another app in your account. If you would like to use the name for this app you will need to submit an update to your other app to change the name, or remove it from App Store Connect. Yes, the original app name is being used for an app in my account. I was trying to update the app, checked all the boxes, added update text, but of course there was no build to upload. Would appreciate any help.

With the 27 OSes using UserDefaults.standard.integer(forKey: ) can cause a crash with EXC_BAD_ACCESS (code=1, address=0x0) It has been seen on a Multiplatform app, up to now tested on iOS/iPadOS and visionOS 27 Beta 1. In our code we use UserDefaults.standard.integer(forKey: ) from a singleton called during the SwiftUI app init(), and we don't know yet if this is the only moment there is a crash as we can't go farther. The API should return 0 if it can't get a value. There is no reason the app should crash if the API conforms to its contract. Running the same code from Xcode on iOS 26 runs it without issue. FeedBack FB23310748

Following the documented ImmersiveMediaSupport flow (NWBrowser → connectReceiver, NWListener → receiver.start(connection:)) with ImmersiveMediaPreviewMessagingProtocol.definition as the framer. Bonjour discovery works, but connectReceiver throws ImmersiveMediaRemotePreviewSession received invalid parameters (sometimes GKVoiceChatServiceErrorDomain 32032). The doc example leaves TLS as /* setup TLS security options */. What exact TLS configuration does the session require — a self-signed SecIdentity, TLS-PSK, a specific cipher/version? And should ImmersiveMediaRemotePreviewSender(networkParameters:) be nil (framework default) while only the NWBrowser/NWListener carry the TLS+framer params? A minimal working setupNWParameters() would unblock me. Thanks!

I've been trying to sign up for the Apple Developer Program for a week now. It keeps giving me errors, my messages aren't being answered, and I can't reach a live person when they call me. It's awful.

Hi — multiple notarytool submissions from my account have been stuck "In Progress" for 60+ hours and never reach Accepted/Invalid. Apple's Developer System Status shows "Developer ID Notary Service" as operational, so this appears to be a backend/account processing stall rather than a public outage. This is blocking a product launch. Team ID: Q7FF775479 ("Developer ID Application: JUNSEN LIU", individual account). Submissions (all still In Progress): e9d00de6-074c-4818-a452-f765fa178a4e — 2026-06-19 06:07 UTC (current build) f02a0398-b6db-4ba0-8429-86a797bdc153 — 2026-06-18 23:21 UTC 8aa72d28-642a-466a-be85-181db125596b — 2026-06-18 04:40 UTC App: "Dollar Desktop Pet" 1.0.0 — a signed .dmg of a hardened-runtime, Developer ID-signed Universal (arm64 + x86_64) Electron app. Tooling: notarytool 1.1.2, Xcode 26.5, macOS 26.5. notarytool submit/history/info all work and list the submissions; status simply never completes, and notarytool log returns nothing. Could you please investigate why these aren't processing? I can provide the .dmg or any additional logs. Thank you.

Hello everyone, I'm looking for advice because my first iOS app has been stuck in "Waiting for Review" since May 29. The app has never entered the "In Review" stage and the status has not changed for weeks. I have already contacted Apple Developer Support multiple times, and they keep telling me that everything looks normal and that I just need to wait. However, it has now been almost a month, which seems highly unusual compared to the review times other developers are reporting. Some details: First app submission Status: Waiting for Review Submitted on May 29 No messages in Resolution Center No rejection or request for additional information Apple Support says there are no issues with the submission Has anyone experienced a similar delay for a first app release? Did the review eventually start on its own, or was there something specific that had to be done? Any advice would be greatly appreciated. Thank you.

Hello everyone, I'm looking for advice because my first iOS app has been stuck in "Waiting for Review" since May 29. The app has never entered the "In Review" stage and the status has not changed for weeks. I have already contacted Apple Developer Support multiple times, and they keep telling me that everything looks normal and that I just need to wait. However, it has now been almost a month, which seems highly unusual compared to the review times other developers are reporting. Some details: First app submission Status: Waiting for Review Submitted on May 29 No messages in Resolution Center No rejection or request for additional information Apple Support says there are no issues with the submission Has anyone experienced a similar delay for a first app release? Did the review eventually start on its own, or was there something specific that had to be done? Any advice would be greatly appreciated. Thank you.

Our app submission has been in "Waiting for Review" status for 8 days after another 8 days before that with no review. Typical review time is 24–48 hours, so this appears to be stuck. We have not received any communication from App Review during this period and there are no outstanding items in App Store Connect. Could a member of the App Review team please check the status of this submission? App Name: Blingz App ID: 6759068218 Bundle ID: com.apperfun.hub Version: 1.39.1 Submission ID: 381c3dce-68f5-426b-b6de-807f513d370f Submission Date: Jun 13, 2026 Support Case ID: 102915835489 Thank you.

Title: Xcode 27 beta 27A5194q: aimodelc reports “Core AI requires the Metal Toolchain” although Metal Toolchain is installed Description: I am trying to compile a Core AI asset using Xcode 27 beta on macOS 27. CoreAI.framework is available and the Metal Toolchain component is installed, but aimodelc refuses to compile with: error: Core AI requires the Metal Toolchain. note: Download it from Xcode > Settings > Components > Other Components. Environment: macOS 27 beta Xcode 27.0 beta Xcode build: 27A5194q Metal Toolchain installed build: 27A5194o Apple Silicon Mac Diagnostics: xcodebuild -version reports: Xcode 27.0 Build version 27A5194q xcodebuild -showComponent MetalToolchain -json reports: { "buildVersion": "27A5194o", "status": "installed", "toolchainIdentifier": "com.apple.dt.toolchain.Metal.32023.917", "toolchainSearchPath": "/private/var/run/com.apple.security.cryptexd/mnt/com.apple.MobileAsset.MetalToolchain-v27.1.5194.15.4aqDVJ" } The actual tools resolve: xcrun --find aimodelc /Applications/Xcode-beta.app/Contents/Developer/usr/bin/aimodelc xcrun --find coreai-build /var/run/com.apple.security.cryptexd/mnt/com.apple.MobileAsset.MetalToolchain-v27.1.5194.15.4aqDVJ/Metal.xctoolchain/usr/bin/coreai-build xcrun --find metallib /var/run/com.apple.security.cryptexd/mnt/com.apple.MobileAsset.MetalToolchain-v27.1.5194.15.4aqDVJ/Metal.xctoolchain/usr/bin/metallib Reproduction: Install Xcode 27 beta build 27A5194q. Install Metal Toolchain from Xcode > Settings > Components > Other Components. Confirm xcodebuild -showComponent MetalToolchain -json reports Metal Toolchain installed. Attempt to compile a Core ML package to Core AI: xcrun aimodelc compile --output /private/tmp/vesta-coreai-smoke/ManualPatchCheck.coreai /private/tmp/vesta-coreai-smoke/AFM27CoreAISmoke.mlpackage Actual result: aimodelc fails immediately: error: Core AI requires the Metal Toolchain. note: Download it from Xcode > Settings > Components > Other Components. Expected result: aimodelc should recognize the installed Metal Toolchain and compile the Core AI asset, or Xcode should provide a Metal Toolchain component compatible with Xcode build 27A5194q. Additional details: Running: xcodebuild -downloadComponent MetalToolchain downloads and installs Metal Toolchain 27A5194o. Running: xcodebuild -downloadComponent MetalToolchain -buildVersion 27A5194q fails with: xcodebuild: error: Failed fetching catalog for assetType (com.apple.MobileAsset.MetalToolchain), serverParameters ({ RequestedBuild = 27A5194q; }) This suggests Apple’s component catalog currently provides Metal Toolchain 27A5194o while Xcode is build 27A5194q, and aimodelc does not accept this installed component as compatible. Please confirm whether Metal Toolchain 27A5194o is intended to work with Xcode 27A5194q. If not, please publish the matching Metal Toolchain component or adjust aimodelc/component compatibility detection.

I bought an iMac 2018 years ago, but it seems that I am having trouble securing it now, which source I have not been able to pin down. I went to turn on FileVault, but saw an unusual procedure flow. I got a message: "Recovery Key A recovery key has been set by your company, school, or institution." I did NOT get this unusual procedure flow with the other macs (MacMini, macbookAir), to which I applied FileVault enable (OK). This iMac has never been under the governance of any company, school, or institution, because I bought it straight out of the Apple Store, right out of the box. But lately, I think that the security of the system has been breached by a hacker. Vitals: Model Name: iMac Model Identifier: iMac18,1 Processor Name: Dual-Core Intel Core i5 Processor Speed: 2.3 GHz Number of Processors: 1 Total Number of Cores: 2 L2 Cache (per Core): 256 KB L3 Cache: 4 MB Hyper-Threading Technology: Enabled Memory: 16 GB System Firmware Version: 529.140.2.0.0 OS Loader Version: 577.140.2~30 SMC Version (system): 2.39f40 Serial Number (system): D25XJ01NH7VF I went ahead & enabled FileVault with this warning statement, listed below, thinking that I could find a workaround. I have tried "sudo fdesetup removerecovery -institutional", and this works for staff, but not for administrators, either terminal in macOS 13.7.8 (22H730), or in Recovery Mode. Can someone enlighten me about what needs to be done to right my iMac's security issue, and help remove what seems to be a breach in my security with the MDM governance installation, which looks out of place because this iMac has always been at my house & never used with any instutition?

I can't figure how to install it Here's google post: You can use the following free options directly inside Xcode 27:1. Built-in On-Device Predictive Code CompletionApple provides a free on-device, on-chip model that runs entirely locally on your Mac.Cost: 100% Free (no internet connection or subscription required).How it works: It uses Apple Silicon to predict and autocomplete your Swift code instantly as you type.Setup: Go to Xcode > Settings > Intelligence and ensure local code completion is toggled on.2. Free-Tier Cloud Models (ChatGPT, Claude, & Gemini)Xcode 27 explicitly features a native two-tier intelligence system. For simple completions, it uses your local chip. For complex planning, multi-turn conversations, and writing autonomous unit tests, it integrates directly with cloud providers. You can utilize the free tiers of these services:Anthropic Claude: You can generate a free API key from the Anthropic Developer Console to power Xcode 27’s coding agents.OpenAI ChatGPT: You can hook Xcode directly into OpenAI's free-tier API allowance.Google Gemini: Xcode 27 natively supports Google's ecosystem, allowing you to use a free Gemini API key.Setup: Navigate to Xcode > Settings > Intelligence, select your cloud provider, and paste your free API key.3. Fully Local Open-Weight Models via OllamaIf you want to handle complex agent tasks without data leaving your Mac, you can connect Xcode 27 to local open-source models. This requires an Apple Silicon Mac.Recommended Models: qwen2.5-coder (highly recommended for Swift and SwiftUI) or llama3-coder.Setup:Download and run Ollama.Pull the model via your Mac terminal (ollama run qwen2.5-coder).Use an Xcode 27 compatible local-host bridge tool or local API endpoint under the "Custom Provider" option in Xcode's Intelligence settings to link Ollama's local port (localhost:11434) straight into your workspace.Xcode 27 Agent SkillsWhen using these models in Xcode 27, they will automatically ingest Apple's native Agent Skills (like the SwiftUI Specialist Skill). This means even a generic free model will receive Apple's optimized context rules to write better, modern Swift 6 code.Are you looking to use the model mostly for inline code autocompletion or for the new conversational agent features (like having the AI autonomously write tests and fix bugs in your workspace)? I can walk you through the exact setup steps for either.19 sitesXcode 27 Beta Release Notes | Apple Developer DocumentationOverview. Xcode 27 beta includes Swift 6.4 and SDKs for iOS 27, iPadOS 27, tvOS 27, macOS 27, and visionOS 27. Xcode 27 beta suppo...Apple DeveloperInside Apple Intelligence and Xcode: Special Presentation | WWDC26so today we're going to build something fun live on stage together but first can we'll give you a quick tour of Xcode. 27. all rig...49sYouTube·Apple DeveloperSwiftUI Best Practices, straight from Apple's Xcode 27 Agent SkillSwiftUI Best Practices, straight from Apple's Xcode 27 Agent Skill. Xcode 27 launched during WWDC 2026 and includes Apple's SwiftU...SwiftLeeShow all

This is not a minor visual glitch or a negligible beta bug; this is a catastrophic telecom and safety failure. In iOS 27 Developer Beta, attempting to activate Wi-Fi Calling for US carriers (like RedPocket, Mint, T-Mobile, etc.) that require an E911 address registration completely hard-crashes the Settings app. You cannot activate Wi-Fi Calling, you cannot register your emergency address, and your cellular service is effectively crippled. As an SRE, I pulled the Console logs and traced the crash. It is absolutely unacceptable that Apple is still relying on the ancient, long-deprecated ⁠UIWebBrowserView⁠ inside ⁠TPSCloudCallingWebViewController⁠ for a critical emergency service configuration page. The Settings app is dying from a dual-concurrency crash caused by aggressive iOS 27 refactoring colliding with this legacy web container: The Apple Intelligence / TextInputUI Collision: On page load, the new text prediction engine blindly scans the legacy web input fields and throws a fatal exception: ⁠-[UIThreadSafeNode _smartReplyUpdateInProgress]: unrecognized selector sent to instance⁠. The old web node simply doesn't support the new Smart Reply APIs. The WebKit Thread Violation: This input system failure (⁠RTIInputSystemClient⁠ invalidation) cascades into a complete WebKit thread deadlock. The engine attempts to parse the carrier's CSS and throws a fatal UIKit assertion: ⁠Modifying properties of a view's layer off the main thread is not allowed⁠. The OS instantly sends a ⁠SIGABRT⁠ to ⁠com.apple.Preferences⁠. I have tried every possible workaround: Disabling JavaScript, removing 3rd-party/foreign keyboards, turning off predictive text, and even using MITM proxies to strip the CSS from the carrier's gateway. Nothing works. The crash happens instantly on load because the TextInputUI injection and the background-thread layer mutation are hardcoded into the OS framework. It is utterly absurd that a broken Smart Reply UI prediction path can block a user from registering an emergency 911 address and activating their phone service. Apple, you need to fix this immediately. Either rewrite ⁠TPSCloudCallingWebViewController⁠ to use a modern ⁠WKWebView⁠, or patch ⁠TextInputUI⁠ to gracefully handle legacy ⁠UIThreadSafeNode⁠ instances. Do not ship another beta with a broken carrier service page.

I want to implement a function to generate a report in the form of pages using the model data of the iOS application. I didn't find the relevant API. Please help me find a relevant SDK and some examples. Thanks.

Hello, I appreciate any advice on how to get enrolled in the development programme as I have been trying for weeks. I have tried with my consumer account, existing for a decade. My ID verification failed. Tried again with a new account created on purpose, again my ID verification failed after sending: - passport picture, bank statement and utility statement. No reason provided and no path to resolution provided. I have tried to contact multiple times that support team, no reply over 2-3 weeks. I have tried escalating officially as a complaint (no reply or acknowledgment) I have asked a manual review to the support team. No reply again. Not sure what is left to me to do. Thanks for any advice.

Stuck in "In Review" for 2+ weeks - tens of clients waiting, not sure what to do Hi everyone, Our app has been sitting "In Review" for more than two weeks now, with no update and no rejection — just silence. We've already shipped to TestFlight and everything works, so this is purely the App Store review stage holding us up. The hard part: we have tens of clients waiting on this launch, and every extra day is putting real pressure on us. We don't know whether we did something wrong, whether we're flagged for extra review, or whether this is just a long queue we have to wait out. we've actually been accepted to the expedited review but it didnt push anything forward. A few questions for anyone who's been through this: Is 2+ weeks in review without any response normal, or a sign something is stuck? Did Apple grant it? Is there a better channel — Developer Support phone/chat, escalation, anything — that got a human to actually look at the submission? We'd really appreciate hearing how others got unstuck. Trying to figure out the right next move instead of just waiting blindly. Thanks in advance.

Hi everyone, I've been working on a problem that I think many of us building AI in Swift are facing: how do you debug why an AI agent behaves differently between runs? Traditional logging tells you what happened. But when a model skips a step, changes its reasoning order, or produces a different output with identical input — you're left staring at walls of logs with no clear answer to why. I've released DProvenanceKit — a reasoning observability framework for Swift that lets you: Record every reasoning step an agent takes (non-blocking, async-safe) Query for reasoning patterns ("find runs where X happened but Y didn't") Diff two executions to see structural differences Detect regressions automatically with rule-based validation Think of it as Git for AI logic. Example: Swift // Record an execution try await DProvenanceKit.run(contextID: "case-123", store: store) { DProvenanceKit.record(.documentEvaluated(documentID: "DocA", score: 0.95)) DProvenanceKit.record(.conflictDetected(reason: "timeline_inconsistency")) DProvenanceKit.record(.finalDecisionMade(approved: false)) } // Query for suspicious patterns let suspiciousRuns = try await store.queryRuns( TraceQueryDSL() .requiring(step: "conflictDetected") .missing(step: "documentEvaluated") // Find runs where conflict was reported but no docs evaluated ) // Diff two runs let diff = engine.diff(base: runA, comparison: runB) print(diff.changes) // See exactly which steps appeared, disappeared, or moved The design: Built specifically for on-device AI (macOS/iOS) with Apple Foundation Models, MLX, or Core ML Non-blocking recording (touches only in-memory buffer) Durable, crash-safe persistence with SQLite WAL Works with async/await context propagation Status: Experimental (core engine complete, actively evolving). Free for development/testing under BSL 1.1. GitHub: https://github.com/Therealdk8890/DProvenanceKit I'm curious if this resonates with anyone here building AI in Swift. What debugging/observability challenges are you facing with AI systems?

I'm using Product.products(for:) to get my auto-renewable subscription on watchOS: let products = try await Product.products(for: [<##Identifier##>]) However, it doesn't return any value, and doesn't throw errors. The console shows an error: Could not parse product: missingValue(for: [StoreKit.ProductResponse.Key.billingPlanType], expected: StoreKit.BackingValue) Is this a bug or I did't configure something well? This product has been approved by App Review.