You would make use of the codesign utility to sign the framework with your certificate. Ultimately the only reason Apple issues certificates is so that they are sure that the person uploading is the developer they've had their handshake with. The second Apple accepts your upload for consideration for release they resign all bundles in the binary with their intermediate certificate, it then goes through the review process after which it is signed with the actual Apple store certificate. The code signature has nothing to do with code ownership.
-rudy On Feb 6, 3:55 pm, Laurent Daudelin <[email protected]> wrote: > Thanks, Rudy, but how would I do that? I don't own the Growl's source code > for 1.3, do I? > > -Laurent. > -- > Laurent Daudelin > [email protected] > AIM/iChat/Skype:LaurentDaudelin > http://www.nemesys-soft.com/ > Photo Gallery > Store:http://laurentdaudelin.shutterbugstorefront.com/g/galleries > > On Feb 6, 2012, at 11:59, Rudy Richter wrote: > > > > > > > > > you would actually sign the framework with your certificate in this > > case. > > > -rudy > > > On Feb 6, 3:52 am, Laurent Daudelin <[email protected]> > > wrote: > >> I have an app on the App Store. I wanted to release an update which > >> would bring support for Growl. However, I cannot include the Growl > >> framework form my app since Apple rejects it because it's not signed. > > >> So, how can I release my app on the App Store and add Growl support > >> without including the Growl framework? -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.
