Invalid Signature - Mac App Store

[Nicholas Rahn]

Hi.

I sign all jars and dylibs under the MyApp.app/Contents directory. Then I
sign the JVM bundle (in my case, MyApp.app/Contents/Plugins/1.8.0.jdk).
 Then I sign the executable, MyApp.app/Contents/MacOS/MyApp. Then I sign
the app, MyApp.app.

I submit the pkg using Application Loader and haven't had a problem with
invalid signatures.

-Nick



On Tue, Sep 24, 2013 at 6:50 PM, Jessica Finley
<jfinley at tech4learning.com>wrote:

> Hiya folks,
>
> We're submitting our app to the Mac App Store and getting the following
> warning:
> > Invalid Signature - the nested app bundle Java SE 8 at path My
> App.app/Contents/PlugIns/1.8.0.jre is not signed
> >
>
>
> I'm stumped as to why I'm getting this warning because I sign all of the
> individual components of the jre bundle (jnilibs, jars, dylibs) and then
> after that, I sign the jre bundle itself.  Is there some magical order to
> doing things that I'm missing?  Has anyone else successfully submitted a
> java app to the Mac App Store without iTunes Connect warning about the jre
> not being signed?  If so, could you please drop me a hint?
>
> Thank you!
> Jess
>
>