[MonoDevelop] Code signing error in MonoDevelop.MonoMac
jeff at xamarin.com
Thu Jul 26 14:24:31 UTC 2012
Thanks for the update, can you submit a bug report about
libMonoPosixHelper.dylib not getting signed at
http://bugzilla.xamarin.comfor tracking? I'll try to make time to look
into this issue as soon as I
On Thu, Jul 26, 2012 at 7:39 AM, zezba9000 <zezba9000 at gmail.com> wrote:
> Although the signing process worked I should point out I get this error in
> email from Apple and an Invalid Binary in Itunes Connet.
> Dear developer,
> We have discovered one or more issues with your recent delivery for "Paper
> Tanks". To process your delivery, the following issues must be corrected:
> Invalid Signature - the main app bundle PaperTanks at path PaperTanks.app
> signed but the signature is invalid. Refer to the Code Signing and
> Application Sandboxing Guide for more information.
> Though you are not required to fix the following issues, we wanted to make
> you aware of them:
> Invalid Signature - the executable at path
> PaperTanks.app/Contents/Resources/libMonoPosixHelper.dylib is not signed.
> Refer to the Code Signing and Application Sandboxing Guide for more
> Once the required corrections have been made, go to the Version Details
> and click "Ready to Upload Binary." Continue through the submission process
> until the app status is "Waiting for Upload." You can then deliver the
> corrected binary.
> The App Store team
> Now I can manually sign "libMonoPosixHelper.dylib" so thats not a problem,
> although I think this should be automated. But why am I getting an invalid
> signature is frustrating as Im positive they are correct... I mean its not
> that complicated to get valid keys from app for an OSX App.
> View this message in context:
> Sent from the Mono - MonoDevelop IDE mailing list archive at Nabble.com.
> Monodevelop-list mailing list
> Monodevelop-list at lists.ximian.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Monodevelop-list