Open GoogleCodeExporter opened 8 years ago
Just did a little bit of light research (ie: Googling) and this sounds like it
could be a problem with the Certificate you used to package the app/installer.
Original comment by Motionbl...@gmail.com
on 16 Apr 2014 at 8:39
Yeah, the issue is that Jarzilla isn't an App Store app.
I suppose I could jump through whatever hoops Apple has put up to certify
Jarzilla, but part of me doesn't feel like I should have to ask Apple
permission (and pay $99 per year) to have an application on their platform.
The downside of this is that GateKeeper treats Jarzilla as untrusted and the
only way to install it is to disable GateKeeper entirely (at least temporarily
during the install).
Original comment by voidstar@gmail.com
on 16 Apr 2014 at 8:56
I don't think you have to pay Apple to make it work (and I agree with your
sentiment there). I always leave GateKeeper running (though I am questioning
that), but I can usually run non-Apple approved apps by using the right-click
Open work around. See this page:
http://www.bu.edu/infosec/howtos/bypass-gatekeeper-safely/
It just seems that this workaround doesn't work and triggers this "damaged and
can't be opened" instead.
Is there some part of the packaging process where you have to provide a
certificate? The other page I found that said something about having this
problem with their app suggested that it was with the certificate that they
used in their installer.
Either way, I support you if you decide not to pursue this. At least it's
listed here now and there's an easy work around. :)
Original comment by Motionbl...@gmail.com
on 16 Apr 2014 at 9:16
Cool. I'll keep this as an open bug.
At some point I'll look into whether there's a way to certify Jarzilla without
too much pain/cost, and avoid GateKeeper's generally bad user experience.
Original comment by voidstar@gmail.com
on 16 Apr 2014 at 9:54
Original issue reported on code.google.com by
Motionbl...@gmail.com
on 16 Apr 2014 at 8:30