File Provider Extension Testing Mode -2014 Error Issue I'm developing a macOS File Provider Extension and encountering a -2014 (Extension not registered) error when using Testing Mode only. Environment macOS: 13.0+ Xcode: Latest version Developer Account: Paid Developer Account Extension Type: NSFileProviderReplicatedExtension Current Status App ID Configuration App ID: kr.it.flux.FluxDrive2.FileProvider Capabilities: ✅ com.apple.developer.fileprovider.testing-mode (enabled) ❌ General com.apple.developer.fileprovider (not visible) Extension Configuration NSExtensionPointIdentifier: com.apple.fileprovider NSExtensionPrincipalClass: FluxDrive2FileProvider.FileProviderExtension Code Signing: Valid (Team Identifier verified) Info.plist: Valid Error Message Error Domain=NSFileProviderErrorDomain Code=-2014 The operation couldn't be completed. (NSFileProviderErrorDomain error -2014.) Underlying error: Error Domain=NSFileProviderErrorDomain Code=-2001 Extension cannot be used Attempted Solutions ✅ Verified and corre
Search results for
build disappears
50,287 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Hello, we have reported this concerning bug with the first beta of iOS 26 in June 2025. Apple has not yet addressed this bug, neither do they have acknowledged that anyone has taken a look at it. I believe this is yet another confirmation that Apple is not interested in maintaining the Screen Time framework – it’s now in a state where it’s barely usable to build stable apps. here are my feedback number for reference: FB18927456 FB18061981 feel free to cross reference those in your feedback reports!
Topic:
App & System Services
SubTopic:
General
Tags:
Hello, we have reported this concerning bug with the first beta of iOS 26 in June 2025. Apple has not yet addressed this bug, neither do they have acknowledged that anyone has taken a look at it. I believe this is yet another confirmation that Apple is not interested in maintaining the Screen Time framework – it’s now in a state where it’s barely usable to build stable apps. here are my feedback number for reference: FB18927456 FB18061981 feel free to cross reference those in your feedback reports!
Topic:
App & System Services
SubTopic:
General
Tags:
Hello, we have reported this concerning bug with the first beta of iOS 26 in June 2025. Apple has not yet addressed this bug, neither do they have acknowledged that anyone has taken a look at it. I believe this is yet another confirmation that Apple is not interested in maintaining the Screen Time framework – it’s now in a state where it’s barely usable to build stable apps. here are my feedback number for reference: FB18927456 FB18061981 feel free to cross reference those in your feedback reports!
Topic:
App & System Services
SubTopic:
General
Tags:
File Provider Extension Testing Mode -2014 Error Issue I'm developing a macOS File Provider Extension and encountering a -2014 (Extension not registered) error when using Testing Mode only. Environment macOS: 13.0+ Xcode: Latest version Developer Account: Paid Developer Account Extension Type: NSFileProviderReplicatedExtension Current Status App ID Configuration App ID: kr.it.flux.FluxDrive2.FileProvider Capabilities: ✅ com.apple.developer.fileprovider.testing-mode (enabled) ❌ General com.apple.developer.fileprovider (not visible) Extension Configuration NSExtensionPointIdentifier: com.apple.fileprovider NSExtensionPrincipalClass: FluxDrive2FileProvider.FileProviderExtension Code Signing: Valid (Team Identifier verified) Info.plist: Valid Error Message Error Domain=NSFileProviderErrorDomain Code=-2014 The operation couldn't be completed. (NSFileProviderErrorDomain error -2014.) Underlying error: Error Domain=NSFileProviderErrorDomain Code=-2001 Extension cannot be used Attempted Solutions ✅ Verified and corre
I am developing a macOS virtual audio device using an Audio Server Plug-In (HAL). I want the virtual device to be visible to all applications only when my main app is running, and completely hidden from all apps when the app is closed. The goal is to dynamically control device visibility based on app state without reinstalling the driver. What is the recommended way for the app to notify the HAL plug-in about its running or closed state? Any guidance on best-practice architecture for this scenario would be appreciated. So, full disclaimer, I don't have a lot of direct experience with AudioServer plugins, so the advice I'm giving is coming from a general device management/architecture perspective, NOT from detailed experience with this particular plugin type. In any case, the place I would probably start with here is the sample project Building an Audio Server Plug-in and Driver Extension. You don't need any kind of DEXT for this, but that sample does how to deal with device appearance/disappearance
Topic:
App & System Services
SubTopic:
Drivers
Tags:
Thanks for the detailed information and diagnostic steps. This makes me believe you have debugged your end adequately, and we are not running into an invalid image, or something simple as that. It might be more suitable to file a Feedback Report than a DTS ticket, so the Notifications team can take a look as to why the store might be becoming inaccessible. The question that comes to my mind is whether this happens when the device is locked and the system Notifications setting is set to not show previews (Settings -> Notifications -> Show Previews) when the device is locked. If that is not set to Always could you try with setting it to Always. I don't really believe this could be the case as you mention the app being active, but it's an easy test to see if that setting has any effect on the issue. Regardless, this would best be handled as a bug report with diagnostic logs. Here are the steps to obtain logs. First , please go to https://developer.apple.com/bug-reporting/profiles-and-logs/ and follow the i
Topic:
App & System Services
SubTopic:
Notifications
Hey @sadaotokuyama, It is technically possible to implement the described experience, however, AVPlaybackCoordinator synchronizes the timing of a single AVPlayer object across devices. In your use case you will need to perform the synchronization across multiple AVPlayer objects yourself. Review Synchronizing data during a SharePlay activity to understand how to accomplish this. Consider sending synchronization timing messages frequently as unreliable so that each user sees the same content, however, when a video starts or stops playing due to user interaction use the reliable delivery mode. The supportsGroupImmersiveSpace flag ensures entities with identical transforms appear in the same relative location for all participants, including both nearby and remote participants. For more information please review Configure your visionOS app for sharing with people nearby. Nearby participants appear naturally via passthrough. Nearby participants do not need to register a spatial Persona. You can share with someone
Topic:
Spatial Computing
SubTopic:
General
Tags:
Below is compilable code: struct ContentView: View { var body: some View { Text(Text) .onAppear() { print(test) } } } test is printed in the console after a new build, and when I go to the Home Screen and return to the app, but if I swipe up from the bottom, and then swipe up from the menu of apps to close the app, it does not print upon opening the app again. What would be an example of code that does run under the circumstance of fully quitting the app and opening it again?
Topic:
UI Frameworks
SubTopic:
SwiftUI
Tags:
When uploading an iOS IPA via App Store Connect API or altool, App Store Connect validates the IPA against the wrong existing app record, even though the IPA is correctly signed and provisioned. The exact same IPA uploads successfully via Apple Transporter, which correctly routes it to the intended app. This appears to be an App Store Connect upload-resolution issue specific to API-based delivery. Environment Account: App Store Connect (Admin access) Authentication: App Store Connect API Key (Issuer ID + Key ID) Apps in Account: com.dailyaudiobible.dabapp Apple ID: 121xxxx266 com.dailyaudiobible.dabapp2 Apple ID: 645xxxx428 iOS / SDK Details Platform: iOS Build Artifact: Single signed IPA used for all tests Target SDK: iOS 18.5 Xcode: 16.4 .NET iOS SDK: 18.5.9227 Minimum iOS Version: 18.5 Architecture: ios-arm64 Build Type: App Store distribution (Release) This SDK/Xcode combination previously worked for TestFlight uploads of this app. Expected Behavior When uploading an IPA with: CFBundleId
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect API
I have been fighting this problem for two months and would love any help, advice or tips. Should I file a DTS ticket? Summary We attach a JPEG image to a local notification using UNNotificationAttachment. iOS reports the delivered notification as having attachments=1, but intermittently no image preview appears in Notification Center. In correlated cases, the attachment’s UNNotificationAttachment.url (which points into iOS’s attachment store) becomes unreadable (Data(contentsOf:) fails) even though the delivered notification still reports attachments=1. This document describes the investigation, evidence, and mitigations attempted. Product / Component UserNotifications framework UNNotificationAttachment rendering in Notification UI (Notification Center / banner / expanded preview) Environment App: OnThisDay (SwiftUI, Swift 6) Notifications: local notifications scheduled with UNCalendarNotificationTrigger(repeats: false) Attachment: JPEG generated from PhotoKit (PHImageManager.requestImage) and written to app
Topic:
App & System Services
SubTopic:
Notifications
Hello Apple Developer Support Team, I am writing to request assistance with an issue preventing me from distributing my iOS app to the App Store. I am able to successfully build and archive my app in Xcode without errors. However, after archiving, Xcode only shows the option “Distribute Content” instead of “Distribute App”. Because of this, I am unable to upload the app to App Store Connect. App & Account Details • App Bundle Identifier: com.yesbuy.yesbuyapp • Team Name: Fathima Sayed Mohamed • Team ID: Z327MG963D • Xcode Version: 26.2 • macOS Version: macOS 15.6.1 Signing & Certificates • Signing Method: Automatically manage signing (enabled) • Signing Certificate (Release): Apple Distribution: Fathima Sayed Mohamed • Provisioning Profile: Xcode Managed / App Store Distribution • Archive Status: Build succeeded What I’ve Already Verified • The archive is created using Release configuration • Skip Install is set to No for the main app target (Runner) • The app target is selected corr
Topic:
App Store Distribution & Marketing
SubTopic:
General
Tags:
App Store
Xcode Cloud
Developer Program
Hello Apple Developer Support Team, I am writing to request assistance with an issue preventing me from distributing my iOS app to the App Store. I am able to successfully build and archive my app in Xcode without errors. However, after archiving, Xcode only shows the option “Distribute Content” instead of “Distribute App”. Because of this, I am unable to upload the app to App Store Connect. App & Account Details • App Bundle Identifier: com.yesbuy.yesbuyapp • Team Name: Fathima Sayed Mohamed • Team ID: Z327MG963D • Xcode Version: 26.2 • macOS Version: macOS 15.6.1 Signing & Certificates • Signing Method: Automatically manage signing (enabled) • Signing Certificate (Release): Apple Distribution: Fathima Sayed Mohamed • Provisioning Profile: Xcode Managed / App Store Distribution • Archive Status: Build succeeded What I’ve Already Verified • The archive is created using Release configuration • Skip Install is set to No for the main app target (Runner) • The app target is selected corr
Hi everyone, I’m building a React Native iOS app where I’m integrating Wazo (native WebRTC) and Jitsi (WebView / WebRTC). Use case: Wazo is used to maintain a background call session (mainly signaling + audio keep-alive). Jitsi is used in the foreground for video calls. Problem: When Jitsi starts, it takes control of the microphone and camera. The Wazo call disconnects after ~5 minutes (likely due to media / audio session conflict). Even if Wazo audio/video is muted or tracks are disabled, the session still drops. My questions: Is it officially supported or recommended to run two WebRTC stacks (Wazo + Jitsi) simultaneously on iOS? Can Wazo stay connected without active audio/video tracks while Jitsi uses mic/camera? Is there a way to release Wazo media streams temporarily (but keep signaling alive) while Jitsi is loading or active? Are there any AVAudioSession / background mode limitations on iOS that make this impossible by design? If this is not supported, what is the recommended architecture (sing
Hello, I am implementing video calling on iOS and need to support Picture in Picture (PiP) behavior similar to FaceTime or WhatsApp. What works Audio continues correctly in background CallKit UI works as expected Video works correctly while the app is in the foreground What I’m trying to achieve When the user presses the Home button or switches apps, I want to show a system Picture in Picture window (floating video outside the app). Current setup Video is rendered via WebRTC The video is displayed inside a WKWebView (HTML / JavaScript) PiP works only while the app is foregrounded When the app backgrounds, the video disappears (only audio remains) Questions Does iOS support system Picture in Picture for: WebRTC video WKWebView / HTML video 2 Is AVPictureInPictureController limited only to: AVPlayerLayer AVSampleBufferDisplayLayer 3 If PiP requires native rendering: Is it mandatory to render WebRTC frames natively using AVSampleBufferDisplayLayer? Is PiP explicitly unsupported for WebView / HTML video?