I've successfully shipped Java apps on the MAS using an embedded JRE, but
with the stricter signing requirements now in place, I'm having a problem.
My script now signs all the binaries, including the JRE's jspawnhelper
executable, which my app relies on to spawn new processes via Runtime.exec.
Th
What entitlements did you sign spawnhelper with? The same as the main app or
the inherit permission?
On Jun 24, 2014, at 9:40 AM, Zach Oakes wrote:
> I've successfully shipped Java apps on the MAS using an embedded JRE, but
> with the stricter signing requirements now in place, I'm having a pr
I signed with the same entitlements as the main app. Apple auto-rejects my
submission if jspawnhelper doesn't at least have the app-sandbox
entitlement. I haven't tried signing it with nothing but the inherit
permission, though, so I'll try that right now.
On Tue, Jun 24, 2014 at 11:44 AM, Danno
It looks like that worked, thanks! I ended up creating a separate
entitlements file for jspawnhelper which looks like this:
http://www.apple.com/DTDs/PropertyList-1.0.dtd";>
com.apple.security.app-sandbox
com.apple.security.inherit
On Tue, Jun 24, 2014 at 11:44 AM, Danno F
Lucky guess. This validates my choice to use the inherit permission for all
but the main .app in the java packager Mac App Store Ready bundler. What you
describe is already being automatically be done in 8u20. Now I know it makes a
difference. Thanks for the update.
—Danno
On Jun 24, 2014,
