3 Replies
      Latest reply on Oct 13, 2019 5:34 AM by eskimo
      dannyow Level 1 Level 1 (0 points)

        Hello!

         

        I'm trying to notarize a single framework. The whole process went perfectly well with 'accepted' status at the end.
        However when I try to staple my framework stapler ends with "The staple and validate action failed! Error 73."

        Verbose flag shows that it's trying to remove nonexisting CoreResources folder:

         

        Could not remove existing ticket from file:XXX.framework/Contents/CodeResources because an error occurred. Error Domain=NSCocoaErrorDomain Code=4 "“CodeResources” couldn’t be removed." UserInfo={NSUserStringVariant=(
            Remove
        ), NSFilePath=XXX.framework/Contents/CodeResources, NSUnderlyingError=0x7fb096934260 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}}
        
        

         

        Any idea how to tackle this problem?

         

        PS: 10.15, xcode 11

        Thank you!

        • Re: Framework notarization: stapler error 73
          eskimo Apple Staff Apple Staff (12,085 points)

          Stapling to bundles other than a .app can be challenging (r. 54951597).  You should definitely file a bug about the problem you’re having here.  Please post your bug number, just for the record.

          Having said that, why are you trying to staple to a framework?  Most folks distribute frameworks are part of a larger package, and thus you’d staple to that outer package.  Are you distributing your framework independent?  Using a .zip?

          Share and Enjoy

          Quinn “The Eskimo!”
          Apple Developer Relations, Developer Technical Support, Core OS/Hardware
          let myEmail = "eskimo" + "1" + "@apple.com"

            • Re: Framework notarization: stapler error 73
              dannyow Level 1 Level 1 (0 points)

              @eskimo thanks for such prompt response.

              Why framework alone? I'm working on plugins loaded by 3rd party apps - to use native code I need a framework, second of all I would like to have an open option in case of distribution framework alone (so yeah it's a stab in the notarized dark here ).

              PS: Can you pls suggest what area of feedback will be the most suitible here? (I mean the very first step in feedback assistant) macOS/Installation-Setup-Migration or Developer Tools/XcodeKit or something else?

              -- daniel

                • Re: Framework notarization: stapler error 73
                  eskimo Apple Staff Apple Staff (12,085 points)

                  Can you pls suggest what area of feedback will be the most suitible here?

                  For this sort of things its best to start with Developer Tools.

                  I'm working on plugins loaded by 3rd party apps - to use native code I need a framework

                  Right, but in that case you should notarise and staple the outermost container (the .dmg or the .pkg or whatever custom installer you’re using) rather than the framework itself.  The ticket you generate by notarising that outermost container will cover any code within the container, and that includes your framework.

                  Share and Enjoy

                  Quinn “The Eskimo!”
                  Apple Developer Relations, Developer Technical Support, Core OS/Hardware
                  let myEmail = "eskimo" + "1" + "@apple.com"