I'm developing a macOS File Provider Extension and encountering a `-2014` (Extension not registered) error when using Testing Mode only.

Question

mohani OP

Created 1d

Replies 1

Boosts 0

Participants 2

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 corrected Extension Info.plist
✅ Verified Extension code signing
✅ Added App Group (group.kr.it.flux.FluxDrive2)
✅ Clean Build and rebuild
✅ Verified installation in /Applications
❌ Attempted to enable Extension in System Settings (Testing Mode doesn't appear)

Observations

Extension is not actually loaded (FileProviderExtension.init() is never called)
NSFileProviderManager.add(domain) immediately returns -2014 error
Extension file is built correctly and included in the app bundle

Questions

Shouldn't Testing Mode allow testing of File Provider Extension? Why is the -2014 error occurring?
The general com.apple.developer.fileprovider capability is not visible in Developer Portal. How can I enable it?
Is it normal for Extension not to be registered in the system when using Testing Mode, or are additional settings required?
Is the general File Provider capability mandatory for App Store submission?

Additional Information

Extension code correctly implements NSFileProviderReplicatedExtension protocol
All required methods (item, enumerator, fetchContents, etc.) are implemented
Network permission (com.apple.security.network.client) is configured

Any help would be greatly appreciated!

Boost

Answer 1

DTS Engineer OP

Apple

13h

I don't have the answer yet, but the explanation of the error code -2001 and -2014, as shown in the following, basically says your app bundle doesn't have a launchable file provider extension, which is pretty strange if your file provier works when the testing mode isn't used.

/**
 Returned by NSFileProviderManager if no provider could be found in the application
 */
NSFileProviderErrorProviderNotFound FILEPROVIDER_API_AVAILABILITY_V3_IOS = -2001,

/*
 Returned by the system to indicate that the system does not have any launchable
 `com.apple.fileprovider-nonui` application extension for this domain's app bundle.
 */
NSFileProviderErrorApplicationExtensionNotFound FILEPROVIDER_API_AVAILABILITY_V6_0_IOS = -2014,

You mentioned "the general com.apple.developer.fileprovider capability is not visible in Developer Portal" and asked how to enable it, which confuses me a bit, because com.apple.developer.fileprovider is never a capability. Would you mind to share where you found the capability and why you believe it should appear in the portal?

For us to investigate the issue, would you mind to check if the issue reproduces when using the following Apple sample, and if yes, share the detailed steps?

Synchronizing files using file provider extensions

Best,
——
Ziqiao Chen
 Worldwide Developer Relations.

0