Since the crash occurs before the code signing takes place, I do not think
it is caused by the second workaround. I would suggest you upload another
archive that includes the audio files. The crash log would be helpful, as
well. If I remember correctly, on OSX the crash logs should be stored in
/Us
The crash is consistent, yes, even after applying the second workaround. Like I
said, it appears to be happening during the file copy process, before the code
signing even takes place.
If it would be helpful, I can upload another archive to my dropbox that
includes those audio files. I didn’t i
Hi Chris,
Is the crash consistent when you include the second workaround? I am not on
a MacOS Sierra to test now.
Best,
Panos
--
On Tue, Sep 20, 2016 at 10:32 PM, Chris Sheffield
wrote:
> That did the trick on the error, however, now LC is crashing when I try to
> create a build and include al
That did the trick on the error, however, now LC is crashing when I try to
create a build and include all the files in the app. In addition to my images
folder, which contains quite a few png images, I also have a folder that
contains *a lot* of mp3 files (to be exact, 8624 of them). Somewhere d
Hi Chris,
You can apply the workaround described here until 8.1.1 rc1 is released:
https://github.com/livecode/livecode/pull/4530/files
(Make sure you include the line [get shell("xattr -cr" && quote &
pAppBundle & quote)] as well)
Best,
Panos
--
On Tue, Sep 20, 2016 at 9:55 AM, panagiotis mer
Hi Chris,
I just tested with your stack in LC 8.1.1 RC-1 (not public) and I confirm I
still get the "resource fork, Finder information, or similar detritus not
allowed” error when building an iOS standalone. After further
investigation, it seems this is caused *only* if you add the "Internet" or
"
You are welcome. Just the stack should be enough to replicate this, but I
would suggest you send everything, just in case.
Best,
Panos
--
On 19 Sep 2016 22:46, "Chris Sheffield" wrote:
> It appears to be just this stack. After creating a new stack, and even
> setting it to copy the same files, t
It appears to be just this stack. After creating a new stack, and even setting
it to copy the same files, the build works just fine.
Yes, I do have png files, quite a lot of them, inside an images folder that is
included in the Copy Files section. Like I said though, I included that folder
even
Hi Chris,
Hmm, that's weird, it should work. The first part of the error
(—resource-rules blah blah) is just a warning. The codesign fails because
of the "resource fork, Finder information, or similar detritus not allowed”
part.
The command [get shell("xattr -cr" && quote & pAppBundle & quote)] s
Panos,
I greatly appreciate the quick reply. Unfortunately that fix didn’t work for
me. I even dug in a little deeper and applied Monte’s other changes as well,
and my build still fails. The —resource-rules error is gone, but I am still
left with the second part of the error about the "resource
Hi Chris,
Try the workaround described here:
http://quality.livecode.com/show_bug.cgi?id=18135
It worked for me.
Best,
Panos
On 19 Sep 2016 19:01, "Chris Sheffield" wrote:
> I’m hoping someone can help with this.
>
> I just fired up LiveCode 8.1 this morning to create a new app build for a
> l
I’m hoping someone can help with this.
I just fired up LiveCode 8.1 this morning to create a new app build for a
landscape app that has the “cropped” issue in iOS 10. I am getting an error at
the point that the app gets signed:
codesigning failed with Warning: —resource-rules has been deprecate
12 matches
Mail list logo
