Re: MAS codesign requirements break Java app signing

2014-11-11 Thread Jessica Finley
Zach, Having mentioned this on the side, I’ll say it again for posterity: I bundle my app also using the appbundler and also have just recently been receiving that same email from Apple upon app submission. Today, I finally got my app bundle to be accepted (for the first part of the process

Re: MAS codesign requirements break Java app signing

2014-11-11 Thread Zach Oakes
Jessica, thank you so much. Your fix worked for me, and I wouldn't have discovered it on my own. I'll try javapackager again when the next JDK update comes, but this will certainly work for the time being. Thank you to Danno, Michael, and the others as well for all the responses. Zach On Tue,

Re: MAS codesign requirements break Java app signing

2014-11-10 Thread Zach Oakes
Darn. Is there no way to manually insert values into the Info.plist before it is signed? If not, I guess I'll keep trying to get my custom script to work. I just need some kind of short term solution to get this app update out... By the way, I noticed there is also no way to set the

Re: MAS codesign requirements break Java app signing

2014-11-10 Thread Zach Oakes
Thanks Steve, I'll try it out when I get home. I am using 10.9.5 (Mavericks), not Yosemite. I'm using different entitlements under Danno's suggestion, and it has worked so far until some time in the last month. On Mon, Nov 10, 2014 at 3:29 PM, Steve Hannah st...@weblite.ca wrote: I was just

Re: MAS codesign requirements break Java app signing

2014-11-10 Thread Zach Oakes
With the Ant task, I already can manually edit my Info.plist so that's not an issue. The problem with it is simply that Apple is rejecting it after I upload the app with the error message I included in the OP. There is something wrong with the sig but I can't figure out what it is. On Mon, Nov

Re: MAS codesign requirements break Java app signing

2014-11-10 Thread Zach Oakes
I successfully am replacing the Info.plist file with the technique you mentioned. Is it possible that the JVMAppClasspath key does not actually do anything? I added the extra jars to it, trying both a space and a colon as a separator, and the java.class.path is always just the main jar file. Sorry

MAS codesign requirements break Java app signing

2014-11-09 Thread Zach Oakes
It looks like Apple has changed its codesigning requirements for the Mac App Store. Thus far, I've been packaging my Java app using Oracle's appbundler tool and signing it with the following script: http://pastebin.com/BtLV9bur This worked fine even as recently as last month. This time, I get an

Re: MAS codesign requirements break Java app signing

2014-11-09 Thread Zach Oakes
In the bash script I linked, everything but jspawnhelper gets the full (user-supplied) entitlements. Do you think that is the problem? On Sun, Nov 9, 2014 at 7:13 PM, Danno Ferrin danno.fer...@oracle.com wrote: What are your entitlements? For javapackager we sign only the master package with

Re: MAS codesign requirements break Java app signing

2014-11-09 Thread Danno Ferrin
Not sure, but that is what is different from what I have that works. Everything else seemed to match up, including the forced overriding of the signatures. On Nov 9, 2014, at 5:23 PM, Zach Oakes zsoa...@gmail.com wrote: In the bash script I linked, everything but jspawnhelper gets the full

Re: MAS codesign requirements break Java app signing

2014-11-09 Thread Michael Hall
On Nov 9, 2014, at 6:10 PM, Zach Oakes zsoa...@gmail.com wrote: Can you elaborate on what you are trying to say? As I mentioned, I already ran codesign -dv MyApp.app, and it does indeed show version=2. Yet, I still get the error from Apple after uploading. Sorry, I had read your poset a