Search results for

build disappears

50,292 results found

Post

Replies

Boosts

Views

Activity

Please allow the "Back to App" breadcrumb to coexist with Live Activities in Compact Mode
Subject: Request to maintain the Status Bar Breadcrumb visibility while Dynamic Island is active Hi, I am developing an app using ActivityKit and Dynamic Island. I've noticed a significant UX regression regarding the system status bar behavior. Current Behavior: When a Live Activity is active in the Dynamic Island (specifically in the compactLeading and compactTrailing presentation), the system automatically hides the Back to [Previous App] breadcrumb button (the small arrow and app name) in the top-left corner of the status bar. This breadcrumb only reappears when the Live Activity switches to the minimal presentation or is dismissed. The Issue: This behavior makes multitasking cumbersome for users. For example, if a user navigates from Safari to my app and then locks the screen or goes to Home, they expect the Back to Safari button to remain accessible. However, because my app's Live Activity is running in the Dynamic Island, the OS removes this navigation shortcut, forcing users to use the app switcher ins
1
0
78
1w
I'm currently using macOS 26 and Xcode 26, but I'm unable to download iOS 26 simulators.
Download failed. Domain: DVTDownloadableErrorDomain Code: 41 User Info: { DVTErrorCreationDateKey = 2025-10-26 06:59:38 +0000; } Download failed. Domain: DVTDownloadableErrorDomain Code: 41 Failed fetching catalog for assetType (com.apple.MobileAsset.iOSSimulatorRuntime), serverParameters ({ RequestedBuild = 23A8464; }) Domain: DVTDownloadsUtilitiesErrorDomain Code: -1 Download failed due to a bad URL. (Catalog download for com.apple.MobileAsset.iOSSimulatorRuntime) Domain: com.apple.MobileAssetError.Download Code: 49 User Info: { checkConfiguration = 1; } System Information macOS Version 26.0.1 (Build 25A362) Xcode 26.0.1 (24229) (Build 17A400) Timestamp: 2025-10-26T17:59:38+11:00
19
0
972
1w
Reply to CallKit automatically shows a system top toast after iOS 26, how to dismiss it?
Is this top banner an intended system behavior change in newer iOS versions? Yes. Is there any public API to dismiss, hide, or customize this UI? No. The general design of CallKit is that the system handles all UI outside of the app, providing a call experience common to all CallKit apps. Related to that point: On iOS versions prior to iOS 26, this UI did not appear under the same CallKit configuration. ...keep in mind that the details of the CallKit UI experience have changed multiple times across iOS releases. This is simply the latest iteration. If not, is this UI considered non-dismissible by design? Sort of. The UI is tied to the call you're managing, so it will disappear when you end the call. However, if your goal is to be in an active call with minimal system UI, then no, that isn't really possible, as one of CallKit’s underlying design goals is to ensure that the user is aware that they are on a call. __ Kevin Elliott DTS Engineer, CoreOS/Hardware
Topic: UI Frameworks SubTopic: UIKit Tags:
1w
Reply to Review Reset
Welcome to the forum. Your question is too general to get a precise answer. However: cancelling a build and resubmitting does put you back in the pipe. but as we don't know how the pipe is managed, hard to say if to go to the back of the queue or not. But most likely, you will fall back in the line. I‘ve done this multiple times, and I have users asking me when the updates are coming. In general, it is not a very good idea to cancel a submission. I have noted that it may create problems, even blocking submission. you'd better test your app seriously before submitting. Guidelines remind that review board is not to detect bugs.
1w
[DriverKit SCSI] SCSI probe stalls for Target ID > 0 with IOUserSCSIParallelInterfaceController
Hello everyone, We are migrating a KEXT storage driver to DriverKit. In our KEXT, we use a one LUN = one Target model and successfully create multiple targets in a loop during initialization. We are now trying to replicate this architecture in our DEXT. The issue is that only Target 0 is fully probed and mounted. For Target 1, the lifecycle silently stops after the first TEST UNIT READY command is successfully acknowledged. The macOS SCSI layer never sends any subsequent probe commands (like INQUIRY) to this target. The failure sequence for Target 1, observed from our logs (regardless of whether Target 0 is created), is as follows: AsyncCreateTargetForID(1) -> UserInitializeTargetForID(1) (Succeeds) UserProcessParallelTask(Target: 1, Opcode: TUR) (Succeeds) The DEXT correctly acknowledges the TUR command for Target 1 by returning kSCSITaskStatus_CHECK_CONDITION with UNIT ATTENTION in the Sense Data (Succeeds) <-- Breakpoint --> UserProcessParallelTask(Target: 1, Opcode: INQUIRY) (Never happens) Throu
3
0
177
1w
CoreNFC ISO7816: provisioning profile doesn’t match entitlements for readersession.formats / iso7816.select-identifiers + NFCError 104 “Tag is not connected”
Hi all, I’m building an iOS app that uses CoreNFC to communicate with a YubiKey 5C NFC over ISO14443 / ISO7816 and send APDUs (e.g. select an applet by AID). Environment • Device: iPhone 13 Pro Max • iOS: 18.6.2 • Xcode: 26.1.1 (17B100) • API: NFCTagReaderSession(pollingOption: .iso14443) using NFCTag.iso7816 What I’m trying to do 1. Start NFCTagReaderSession(.iso14443) 2. Detect tag → connect 3. Send ISO7816 APDUs (SELECT AID, etc.) Issue A — Entitlements / signing If I add ISO7816-related NFC entitlements, Xcode fails signing with an error like: • “Provisioning profile … doesn’t match entitlements file value for com.apple.developer.nfc.readersession.formats” When I inspect the generated .mobileprovision, I only see something like: • com.apple.developer.nfc.readersession.formats = [NDEF, TAG, PACE] …and I do not see an ISO7816 / select-identifiers entitlement (and the Developer portal UI doesn’t appear to let me enable it). Questions: 1. Is ISO7816 access under com.apple.developer.nfc.readersession.
1
0
83
1w
Xcode Cloud: Command line name "app-store" is deprecated
Since Dec 18th, my Xcode Cloud builds (for multiple apps) have been failing with this error: Command line name app-store is deprecated. Use app-store-connect instead. I haven't made any changes to my system, signing, etc, and two separate apps started failing at the same time. No matter what I change on my Workflows (environment, new workflow from scratch, etc), nothing seems to fix it, which leads me to believe this is a bug with Xcode Cloud itself. I've logged FB21456291 already, but just wanted to post here to see if I'm missing something.
1
0
63
1w
Reply to Xcode Cloud: Command line name "app-store" is deprecated
Thank you for sharing your experience. Given that you are encountering failures in Xcode Cloud builds with a deprecation warning related to the command line name, it is likely that there has been an internal change or update in Xcode Cloud, and you are still using an outdated version of Xcode to upload your application. Please review any recent release notes or updates for Xcode Cloud that may mention changes to command line tools or deprecations. While these notes may sometimes lag behind actual changes, they can provide valuable insights. Do you have the latest version of Xcode? Version of your macOS? If so, please provide the version and build number. Additionally, have you attempted to submit the error using the other app app-store-connect? If available, consider participating in beta programs for Xcode or Xcode Cloud to gain early access to patches or updates that may address this issue. Please continue to track feedback and updates and provide us with more information about the version
1w
Apple rejected my app ( again )
Hello everyone, few days back I posted about how apple rejected my build and now after 3 days, they replied back in a very unclear, and I am not being able to understand what they really mean by that. Context :- In my app, when the user clicked on export button, it should show the export options, however, if the user is not on a lifetime plan, it should open the premium popup / modal to allow them to purchase. Now, this modal loades project based on storekit IN app purchases I added, and locally I tested using the `.storekit` file and everything worked fine. However, before archieveing the build for app store connect, I remove the local file form edit scema, and I thought it should load automatically based on the IAP, because I added the IAP to the app build in the console as well. But now, apple responded with this after 3 days :- Issue Description The app exhibited one or more bugs that would negatively impact App Store users. Bug description: Export button brings up an empty shee
1
0
195
1w
Pre-inference AI Safety Governor for FoundationModels (Swift, On-Device)
Hi everyone, I've been building an on-device AI safety layer called Newton Engine, designed to validate prompts before they reach FoundationModels (or any LLM). Wanted to share v1.3 and get feedback from the community. The Problem Current AI safety is post-training — baked into the model, probabilistic, not auditable. When Apple Intelligence ships with FoundationModels, developers will need a way to catch unsafe prompts before inference, with deterministic results they can log and explain. What Newton Does Newton validates every prompt pre-inference and returns: Phase (0/1/7/8/9) Shape classification Confidence score Full audit trace If validation fails, generation is blocked. If it passes (Phase 9), the prompt proceeds to the model. v1.3 Detection Categories (14 total) Jailbreak / prompt injection Corrosive self-negation (I hate myself) Hedged corrosive (Not saying I'm worthless, but...) Emotional dependency (You're the only one who understands) Third-person manipulation (If you refuse, you're provi
1
0
504
1w
Pending Termination Notice 3 months after App Transfer
Hi everyone, I am seeking urgent advice or attention from the App Review team regarding a Pending Termination Notice I received for Section 3.2(f). The Situation: I recently acquired a portfolio of apps from another developer to start my business on the App Store. Three months after the transfer, my account was flagged for removal because one of these acquired apps repeatedly violated guidelines to evade the review process. The Problem: I am being punished for the previous owner's actions. I have never submitted a new build, metadata update, or review request for this specific app since acquiring it. The Timeline (Proof of Innocence): August 4, 2025: Last update submitted by the Previous Owner. September 6, 2025: I signed the Purchase Agreement to start my business. September 9, 2025: App Transferred to my account. December 11, 2025: Termination Notice received. As the timeline proves, the alleged evasion attempts via submissions occurred before I even owned the app. Regarding Unresolved Issues: I am
2
0
89
1w
Reply to Pending Termination Notice 3 months after App Transfer
It has now been over 3 weeks since I submitted my appeal regarding this wrongful termination flag, and I have received no response from the App Review Board. The uncertainty is incredibly distressing for a new business owner. I am living in fear that my account will be terminated simply because my appeal is sitting in a queue, unread. To reiterate the core misunderstanding: Apple flagged my account for evading review with new submissions. Fact: The last submission for this app was August 4, 2025 (by the Seller). Fact: I acquired the app on September 9, 2025. Fact: I have never submitted a build for this app. I am being penalized for the previous owner's actions that occurred a month before I even had access. If an Apple Staff member sees this: Please, could you look into my case? I am holding the Purchase Agreement and Bank Transfer records verifying the date of my acquisition. I am a bona fide purchaser, not a bad actor. I am ready to delete the app immediately to resolve this, but I need someone to
1w
SwiftUI, iOS 26.2, ToolbarItem .largeTitle and .title, overlap issue
I built this very simple example to demonstrate the issue im facing on iOS 26 when trying to use custom ToolbarItem element for .largeTitle. Code: struct ContentView: View { var body: some View { NavigationStack { Screen() .navigationTitle(First) .toolbar { ToolbarItem(placement: .largeTitle) { Text(First) .font(.largeTitle) .border(Color.black) } } .navigationDestination(for: Int.self) { integer in DestinationScreen(integer: integer) } } } } struct Screen: View { var body: some View { List { ForEach(1..<50) { index in NavigationLink(value: index) { Text(index.description) .font(.largeTitle) } } } } } struct DestinationScreen: View { let integer: Int var body: some View { HStack { Text(integer.description) .font(.largeTitle) Spacer() } .padding() .navigationTitle(integer.description) .toolbar { ToolbarItem(placement: .largeTitle) { Text(integer.description) .font(.largeTitle) .border(Color.black) } } } } As shown on the gif, when navigating between pages, titles are going to overlap for a short while. Othe
Topic: UI Frameworks SubTopic: SwiftUI
1
0
91
1w
xCode26.x Metal4 classes do not compile
Hi, I am using xCode26.x. But my Metal4 classes are not compiling. I downloaded the sample code from Apple's website - https://developer.apple.com/documentation/Metal/processing-a-texture-in-a-compute-function. For example, I am getting errors like Cannot find protocol declaration for 'MTL4CommandQueue'; I have hit a deadline. Any recommendations are very welcome. I have downloaded the Metal Tool chain. When I run the following commands on the terminal - xcodebuild -showComponent metalToolchain ; xcrun -f metal ; xcrun metal --version I get the following response - Asset Path: /System/Library/AssetsV2/com_apple_MobileAsset_MetalToolchain/86fbaf7b114a899754307896c0bfd52ffbf4fded.asset/AssetData Build Version: 17A321 Status: installed Toolchain Identifier: com.apple.dt.toolchain.Metal.32023 Toolchain Search Path: /Users/private/Library/Developer/DVTDownloads/MetalToolchain/mounts/86fbaf7b114a899754307896c0bfd52ffbf4fded /Users/private/Library/Developer/DVTDownloads/MetalToolchain/mounts/86fbaf7b114a899
2
0
1k
1w