FileProvider fails to instantiate from /Applications folder

Question

T-dawg OP

Created May ’23

Replies 3

Boosts 2

Views 1.5k

Participants 1

Hi,

So I am bundling a FileProvider Extension with my electron application and have noticed a very strange behavior. When I package my application and install/launch it from any directory everything runs perfect. However the exception is when I install it to/launch it from the /Applications folder.

Specifically I receive Cannot create domain: Error Domain=NSFileProviderErrorDomain Code=-2001 "The application cannot be used right now." which maps to providerNotFound. Seems that the provider is failing to instantiate altogether, and therefore I lack any extension functionality.

After I have run the app from the /Applications folder once if I try and run the app from any other directory it fails and I get the same error message.

Anybody have any clues as to what may be changing in my environment that driving this behavior?

Answered by T-dawg in 753305022

I discovered that the issue was that the provisioning profile being generated from XCode was using my personal ID instead of my organization ID so I had to turn off automatic signing and manually provide the correct provisioning profile.

You can see more in detail the steps I took in my response to this StackOverflow post.

Hope this helps someone :)

Boost

Answer 1

T-dawg OP

May ’23

Upon further inspection I found that I'm getting an error in the Console that seems to be the cause of the issue: "Sandbox: fileproviderd(684) deny(1) file-read-data /Applications/myApp.app/Contents/PlugIns/myHelperApp.app". Any clues as to how to resolve this issue?

Is this is a code signing issue? If so I am failing to see what I am doing wrong. I am signing my helper app through XCode with a MacOS provisioning profile, packaging it within my application, and then signing my application.

0

Answer 2

T-dawg OP

May ’23

Made a sister post on stackoverflow here.

0

Answer 3

T-dawg OP

May ’23

Accepted Answer

I discovered that the issue was that the provisioning profile being generated from XCode was using my personal ID instead of my organization ID so I had to turn off automatic signing and manually provide the correct provisioning profile.

You can see more in detail the steps I took in my response to this StackOverflow post.

Hope this helps someone :)

1