Yes, that is what I meant.
Thanks,
Brian
On Dec 3, 2018, 12:59 PM -0600, kee nethery via use-livecode
, wrote:
>
>
> > On Nov 28, 2018, at 1:51 PM, Rick Harrison via use-livecode
> > wrote:
> >
> > Brian,
> >
> > Do you mean:
> >
> > sudo codesign --verbose --deep --force --sign "3rd Party Mac
> On Nov 28, 2018, at 1:51 PM, Rick Harrison via use-livecode
> wrote:
>
> Brian,
>
> Do you mean:
>
> sudo codesign --verbose --deep --force --sign "3rd Party Mac Developer
> Application: MYCOMPANY NAME (KDSK9SJUNK)” --entitlements
>
assuming you meant --entitlements
Kee
>
> If so,
Brian,
Do you mean:
sudo codesign --verbose --deep --force --sign "3rd Party Mac Developer
Application: MYCOMPANY NAME (KDSK9SJUNK)” --entitlements
If so, yes I did that.
Rick
> On Nov 28, 2018, at 3:13 PM, Brian Milby via use-livecode
> wrote:
>
> When you did the codesign, did you use
When you did the codesign, did you use the "--entitlements" option? (I saw
this in a semi-related post on rejections)
On Wed, Nov 28, 2018 at 12:26 PM Rick Harrison via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Hi Guys,
>
> I managed to strip out the old 32 bit stuff leaving
> just
That is really nice to know!
thanks,
JB
> On Nov 28, 2018, at 1:39 AM, Matthias Rebbe via use-livecode
> wrote:
>
> Another and more comfortable way would be to use App Wrapper 3, in case you
> own it.
>
> App Wrapper has a feature called Architecture Cleanup to make Intel 64-Bit or
> Inte
Hi Guys,
I managed to strip out the old 32 bit stuff leaving
just the 64 bit code thanks to your instructions.
I re-codesigned the app and made sure that
the entitlements.plist had:
com.apple.security.app-sandbox
com.apple.security.files.user-selected.read-write
com.apple.security.network
Another and more comfortable way would be to use App Wrapper 3, in case you own
it.
App Wrapper has a feature called Architecture Cleanup to make Intel 64-Bit or
Intel 32-Bit only.
http://www.ohanaware.com/appwrapper/
Regards,
Matthias
Matthias Rebbe
free tools for Livecoders:
http
Just filed this report:
https://quality.livecode.com/show_bug.cgi?id=21720
Best,
Panos
On Wed, Nov 28, 2018 at 10:20 AM panagiotis merakos
wrote:
> Hello all,
>
> Yes, it seems we have to make sure that the code applied to externals for
> removing unneeded arch is also applied to revsecurity.
Hello all,
Yes, it seems we have to make sure that the code applied to externals for
removing unneeded arch is also applied to revsecurity. Here are detailed
instructions on how to do this manually from the terminal (the instructions
are for tsNet - just change the path to the one of revsecurity):
Yes, that is the section of code that I was referring to. So you should be
able to:
lipo revsecurity.dylib -remove i386 -output revsecurity.dylib
After changing to the directory containing the file in the terminal.
>
>
___
use-livecode mailing list
us
Hi Brian,
I am assuming you are referring to the following:
-- Remove unneeded slices from the MacOS externals
if the platform is "macos" and pSettings is not empty then
local tRemove
if pSettings["MacOSX x86-64"] is true and pSettings["MacOSX x86-32"] is not
true then
put "i386" into tRemov
Hi Brian,
I have not tried manually running lipo on the file.
I figure I will have to resign the app anyway so
not a huge deal if it works.
I’m not a big unix user so if you have some
additional suggested lipo code for me to look
at I’d appreciate it.
All I found on the web was the following
r
LC already has code to run lipo when building the app. It currently just
operates on externals. The code is in __revSBCopyFile which is a part of
revsblibrary.livecodescript. From my initial look, I'm guessing that it
also needs to work on revsecurity.dylib as well.
Have you tried manually runn
That sounds like the solution.
JB
> On Nov 27, 2018, at 4:44 PM, Rick Harrison via use-livecode
> wrote:
>
> Hi JB,
>
> I had the build for Mac OS X 64-bit box checked in the
> Standalone Application Settings for my stack.
>
> I am running High Sierra and so far LiveCode does
> not yet that
Hi JB,
I had the build for Mac OS X 64-bit box checked in the
Standalone Application Settings for my stack.
I am running High Sierra and so far LiveCode does
not yet that I know of support Mojave. I do however
think that yes this is Apple forcing things forward as
per usual.
I believe the team
I have never submitted an app on the apple store but
I googled i386 and here is what I get.
x86_64 is for 64 bit processors. i386 is for 32 bit processors.
So the question I wonder is does this have something to do with
Mojave OS? From what I have read they will be eliminating the
32 bit program
LC version 9.0.1
Rick
> On Nov 27, 2018, at 12:38 PM, Brian Milby via use-livecode
> wrote:
>
> What version of LC?
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscript
What version of LC?
Thanks,
Brian
On Nov 27, 2018, 11:28 AM -0600, Rick Harrison via use-livecode
, wrote:
> Here is the problem:
>
> lipo -info /Users/…(PathToMyAppContents)…/Contents/MacOS/revsecurity.dylib
> are: i386 x86_64
>
> Notice that at the end it says i386
>
> That is what apple is co
Here is the problem:
lipo -info /Users/…(PathToMyAppContents)…/Contents/MacOS/revsecurity.dylib are:
i386 x86_64
Notice that at the end it says i386
That is what apple is complaining about.
This is clearly a serious LiveCode revsecurity.dylib problem, and without it
fixed
no one can submit a
Hi Kee,
I tried a couple of quick experiments.
I turned off the password encrypt protection
and the destroy-stack option to see if that
would remove the revsecurity.dylib.
Unfortunately I had no luck in removing it.
I will try some other things in the morning.
Thanks for getting back to me abo
Sounds like bug report. Sorry I’m no expert on revsecurity.dylib. Once you
figure it out, happy to add it to the instructions.
Kee
> On Nov 26, 2018, at 8:42 PM, Rick Harrison via use-livecode
> wrote:
>
> Hi Kee,
>
> I did a get info on revsecurity.dylib inside the contents of the standalon
Hi Kee,
I did a get info on revsecurity.dylib inside the contents of the standalone
and unfortunately it doesn’t tell me if it is 32 or 64 bit. :-(
Rick
> On Nov 26, 2018, at 11:36 PM, kee nethery via use-livecode
> wrote:
>
> Sounds like a bug report is in order?
>
> Also, I wonder if you
Sounds like a bug report is in order?
Also, I wonder if you pull it out of the app and then do Get Info on it,
whether it will tell you is is 32 or 64 bit?
Kee
> On Nov 26, 2018, at 4:46 PM, Rick Harrison via use-livecode
> wrote:
>
> Hi Kee,
>
> I was wondering if perhaps revsecurity.dylib
Hi Kee,
I was wondering if perhaps revsecurity.dylib is being used
for the password protection of the stack. That could be it.
If that is the problem though how are people supposed to
protect their code?
Rick
> On Nov 26, 2018, at 5:59 PM, Kee Nethery via use-livecode
> wrote:
>
> What is re
Hi Kee,
I don’t know why revsecuity.dylib is causing the problem if it is.
Is there a way to see if revsecuity.dylib is 32 bit instead of 64 bit?
Rick
> On Nov 26, 2018, at 6:09 PM, Kee Nethery via use-livecode
> wrote:
>
> Oooops.
>
> My list of entitlements already included
>
>
Hi Kee,
It already has this so that can’t be it.
Rick
> On Nov 26, 2018, at 5:57 PM, kee nethery via use-livecode
> wrote:
>
> com.apple.security.app-sandbox
>
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit th
Oooops.
My list of entitlements already included
com.apple.security.app-sandbox
Ignore my previous emails. No clue why revsecurity.dylib is triggering an
entitlements issue. Perhaps it is standalone code that needs it’s own
entitlements plist?
Kee
> On Nov 26, 2018, at 2:59
What is revsecurity.dylib used for? That probably tells us what you are using
that my app was not.
Kee
> On Nov 26, 2018, at 2:57 PM, kee nethery via use-livecode
> wrote:
>
> Try this URL
>
> https://developer.apple.com/documentation/security/com_apple_security_app-sandbox?language=objc
>
Try this URL
https://developer.apple.com/documentation/security/com_apple_security_app-sandbox?language=objc
It’s not very useful. But it does say that entitlement needs a boolean.
Try adding to the entitlements.plist the following:
com.apple.security.app-sandbox
Wonder what y
29 matches
Mail list logo
