Not sure there's an easy way to keep it from happening. If it is created
with the permission.. (doubtful since windows works differently but I've
been wrong often before) you could always run a linux vm in virtualbox, set
the permission, gzip it up and send it that way.
On Fri, Jul 1, 2016 at 9:5
Hi hh,
> Am 01.07.2016 um 15:57 schrieb [-hh] :
>
> If it's a newer MacOS (system integrity protection)
> he/she could try to rightClick the icon and then
> select "open" and choose again "open" in the
> "unknown-dev-dialog".
nope, it was no Gatekeeper security issue, see my response to Mike hin
Hi Mike,
> Am 01.07.2016 um 15:54 schrieb Mike Bonner :
>
> Yeah, sounds like it lost the correct permissions during the transfer to
> the mac.
obviously, any way to prevent this?
> you can either chmod 755
thanks, that was it, it is running fine now :-)
> I think you have to go into the a
If it's a newer MacOS (system integrity protection)
he/she could try to rightClick the icon and then
select "open" and choose again "open" in the
"unknown-dev-dialog".
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/Mac-app-c
Yeah, sounds like it lost the correct permissions during the transfer to
the mac. you can either chmod 755
I think you have to go into the app package and hit the actual executable,
don't think it will work on the app package itself. (You can probably also
set the permissions using finder.. go
Hi friends,
a client of mine has compiled a Mac standalone on Windows and now the app will
not run:
"The application XXX cannot be run" or what the exact english message reads!?
I remember faintly there is some problem with erm. "executable bit"?
But forgot the details...
Or does the app have t
