FileProvider Extension not working when code signed

Question

Kathiresan-A OP

Created Apr ’23

Replies 2

Boosts 0

Views 1.4k

Participants 3

My project has a base app which is manually signed, inside I have a FileProvider parent app and extension.

When things works elegantly in Xcode debug build when I run FP App. But, when I package it, the FileProvider can't mount, fails with a generic error on parent app

(Error Domain=NSFileProviderErrorDomain Code=-2001 "The application cannot be used right now." UserInfo={NSLocalizedDescription=The application cannot be used right now.}

Another generic error in FileProvider demon

fileproviderd(488) deny(1) file-read-data &#x2F;Applications&#x2F;XYZ.app&#x2F;Contents&#x2F;Resources&#x2F;FileFP.app

How to solve this?

Boost

Answer 1

mital OP

Sep ’23

I am also running into similar issue, @Kathiresan-A did you managed to find a solution to this ?

0

Answer 2

T-dawg OP

Nov ’23

I also had this problem for a long time. Please do a deep dive on proper signing and notarization. Personally for me what fixed it was that I was providing the wrong provisioning profile so the notarization was failing. Turns out I needed a Distribution provisioning profile as opposed to a Developer provisioning profile. Also beware that if you sign an extension, package it within an app, then sign the app, then the extension signature will be overridden and possibly invalidated.

0